summaryrefslogtreecommitdiff
path: root/meta-phosphor/conf
AgeCommit message (Collapse)AuthorFilesLines
2023-05-18meta-phosphor: btrfs-tools: disable python PACKAGECONFIGPatrick Williams2-0/+8
Some systems, like Bletchley, might be using btrfs file systems and using the btrfs-tools to format them. They probably don't need the Python modules by default, so disable them in meta-phosphor. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I87316001f48432db4297656838b750e10651d043
2023-05-18meta-phosphor: unset 'largefile' featurePatrick Williams1-1/+1
According to poky/documentation/migration-guides/migration-4.1.rst, the DISTRO_FEATURE `largefile` no longer exists. Remove it from our default feature list. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Id6d052c439ea2442dea5cb98468d7e2d68cb7c42
2023-05-17meta-phosphor: adjust default DISTRO_CODENAMEPatrick Williams1-1/+1
When upstream adjusted this to mickledore, we missed it and it was still listed as langdale. Adjust to match. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I5ad4a373f4d4c823ecf9314218c73faf7f23213f
2023-05-05meta-phosphor: Enable Software Bill of Materials (SBOM)Andrew Jeffery1-0/+3
SBOM support gives a conscise, structured summary of the content of the image and the licenses used. More information is provided here: https://docs.yoctoproject.org/next/dev-manual/sbom.html Change-Id: Ia0f906b6e2994c030b30cc73c19b5f74b326cda5 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2023-04-13introduce new extra-dev-debug-tools distro featureAndrew Geissler1-0/+1
For systems with extra flash space, including some additional developer debug tools can be useful. Instead of having everyone hand code them into their obmc-apps bbappend files, provide a common include that will bring them in. Change-Id: I91a1b29ab4a4ff2efaaf5ea5dfbafd83781168df Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2023-03-27meta-phosphor: static-norootfs: use xz for small flash imagesPatrick Williams1-0/+1
The 32MB flash machines typically do not have enough space to hold a zstd compressed rootfs, so default them to use xz. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I6f24d771e41853c13ec55c9a35bc5dff3f523cb2
2023-03-17libgpiod: disable the 2.0 version temporarilyPatrick Williams1-0/+2
The 2.0 version of libgpiod broke backward compatibility and requires changes in multiple repos within OpenBMC. Set PREFERRED_VERSION back to 1.6.4, which is still shipping with meta-openembedded, until we have time to resolve this. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I2aca89e9bc9eaba84f95e006bfa0647553c37f54 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
2023-01-14meta-phosphor: introduce static non-rootfs image typePatrick Williams3-0/+13
Define a new image type 'static-norootfs' that takes the entire rootfs and places it as the initramfs for the kernel's FIT image, so that the BMC is entirely running from a ramdisk. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I0163f5be0a1b176e0db5f89b85f34e4feae8a588
2023-01-14meta-phosphor: split image type configs to includesPatrick Williams4-18/+10
We have reached branch-capacity in the bb.utils.contains checks at 3 image types. In order to be able to more easily add additional image types, split the differences out into additional inc-snippets for each image type. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ibcdb5c885c67cb6d8728dfd315eb07f99b1a2173
2023-01-13yocto:mickledore: add support for new yocto layerAndrew Geissler1-1/+1
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
2023-01-12meta-phosphor: enable org.freedesktop dbus interfacesPatrick Williams1-4/+4
The org.freedesktop interfaces have the same "use everywhere" status as xyz.openbmc_project, since they are not specific to any company or architecture. Enable them in meta-phosphor. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I3261a6777b2c9003f5476061e4df30811321f73d
2022-12-21meta-phosphor: set DISTRO_CODENAMEPatrick Williams1-0/+3
Back in 2018 we stopped including poky.conf by default and treated phosphor as a separate distro. One minor side-effect of this is that the DISTRO_CODENAME is no longer defined, which is used in some misc. locations such as os-release. Mirror the current Poky codename with the intention that we will keep this in sync as upstream moves along. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iabbdd3f6046f2c7b8ffc81536ab4b47f8471ee20
2022-10-13meta-phosphor: remove unused variablesBrad Bishop1-5/+0
These variables are unused; remove the dead metadata. Change-Id: I17d0282277a0231a264773d8bac9afeef69ec8b4 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2022-10-13treewide: remove pointless abstractionsBrad Bishop1-66/+0
All of these abstractions have exactly one implementation. Remove the indirection to improve at a glance comprehension. Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Change-Id: I5d701aff6d0876fa3b2d16c841cbdcb0433b221f
2022-10-06cleanup: Do as the TODO commandsEd Tanous1-7/+0
Both of the patchsets mentioned in the SECURITY_FLAGS holdouts have been merged, we can enable the security flags on these projects now. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I62ab78568dac5970f7ab6a05bfe9cd8b99ecc731
2022-09-30add langdale to compatible layerAndrew Geissler1-1/+1
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
2022-09-27meta-nuvoton: add support to generate full flash image for npcm8xxTim Lee1-0/+1
Nuvoton's npcm8xx full flash image includes TIP FW, Bootblock, ATF, OPTEE and UBOOT with headers. Generating headers and merging images are being done by Nuvoton's binary generator tool (Bingo) which uses external parameters from XML files for that. Thus, we need to add related fitimage and image type for npcm8xx. However, before merge this commit, we must wait for below commits were merged. meta-nuvoton: arm-trusted-firmware: add arm trusted firmware recipe https://gerrit.openbmc.org/c/openbmc/openbmc/+/55234 meta-nuvoton: add npcm8xx-bootblock recipe https://gerrit.openbmc.org/c/openbmc/openbmc/+/55117 meta-nuvoton: add npcm8xx-igps recipe https://gerrit.openbmc.org/c/openbmc/openbmc/+/55099 meta-nuvoton: npcm7xx-bingo: upgrade latest version 0.0.5 support Arbel https://gerrit.openbmc.org/c/openbmc/openbmc/+/55128 Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I4599e39d3873f07cde6904d0f10161964fc45c7a
2022-09-12treewide: handle more upstream TEMPLATECONF movePatrick Williams1-0/+0
We also need to move the conf-notes.txt files. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ic44e015c0216b526de4fec277ad42f162bca1f33
2022-09-09treewide: handle upstream TEMPLATECONF movePatrick Williams2-0/+0
The latest poky commit is requiring us to have all of our template configs in a subdirectory instead of directly in the `conf` directory. Without this we end up with errors during setup like: ``` Error: TEMPLATECONF value (which is .../openbmc/meta-facebook/meta-bletchley/conf) must point to meta-some-layer/conf/templates/template-name ``` Fix this by moving all of our template files into the 'default' template subdirectory (following the pattern of poky) and modifying `setup` as necessary to follow. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iecefde73d55acbb6bc63ae3d68c4311adaf327ae
2022-05-02meta-phosphor: Allow overriding of DISTRO_NAMEJoel Stanley1-1/+1
Some systems wish to override the distro name. Allow this by not forcefully setting the variable in phosphor-base. Change-Id: Ie6fc72e92d7bd215dfa6a2835a8022ae8daf51b2 Signed-off-by: Joel Stanley <joel@jms.id.au>
2022-04-30treewide: remove meta-perlPatrick Williams1-1/+0
The only recipes which use content from meta-perl are openpower machines: ``` meta-openpower/recipes-bsp/pdata/pdata_git.bb: libxml-libxml-perl-native \ meta-yadro/meta-nicole/recipes-phosphor/logging/openpower-esel-parser_git.bb: libxml-libxml-perl-native \ ``` Remove meta-perl from the bblayers of every layer except openpower machines. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I51f1a8fbfbe879295c64d2339fc115dbd8823681
2022-04-22treewide: drop unused meta-security layerBrad Bishop1-1/+0
This was added with cde0f094f for libseccomp, but shortly after that upstream moved libseccomp from meta-security to core (241c7d2e6). As such, meta-security is no longer used or required. Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Change-Id: I371e54b11f6336720dfc6edf0ef733d22b7fb4f2
2022-04-22meta-phosphor: add layer dependenciesBrad Bishop1-0/+4
These layers are all required, so add them to the layer dependencies. This generates an error earlier in the build process when layers are missing from the configuration (bblayers.conf). The dependency list below is informative, but likely not comprehensive: -meta-python: python3-inflection-native -meta-networking: net-snmp -meta-oe: rsyslog, libvncserver, ipmitool, boost-url, libgpiod, lmsensors-config, openldap Change-Id: I1b480224e6ec4b8bd61c8f21d6e569d17363a9a6 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2022-04-12treewide: Update BB_DISKMON_DIRS useGeorge Liu1-4/+4
Per [1][2], Yocto is starting to deprecate ABORT and has replaced the "ABORT" action in BB_DISKMON_DIRS entries with "HALT". 1. https://wiki.yoctoproject.org/wiki/Inclusive_language 2. https://git.yoctoproject.org/poky/commit/?id=4f77505d94a8f6260933f457e9848d1d2fa98ce5 Tested: Built obmc-phosphor-image successfully and eliminate the following warnings: ``` WARNING: The BB_DISKMON_DIRS "ABORT" action has been renamed to "HALT", update configuration ``` Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: If57d0ded9fac41e23b31b01e2a0e309ac7388148
2022-03-28meta-phosphor: Add vmlinux to image typesJoel Stanley1-1/+1
Ensure the vmlinux is archived as part of the build artifacts for debugging. Signed-off-by: Joel Stanley <joel@jms.id.au> Change-Id: If84c284cfc60f6b8ae5c641ef7ee06255f29d8c1
2022-02-26treewide: support yocto kirkstone releasePatrick Williams1-1/+1
* Deprecate N-1 release (hardknott). * Enable N+1 release (kirkstone). Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
2022-02-23meta-phosphor: packagegroup-security: remove tpm2-pkcs11Patrick Williams1-0/+2
We don't need pkcs11 support on the BMC by default and it ends up causing a dependency chain that brings in Rust. This packagegroup can only be pulled in when meta-security/meta-tpm is used, so hook into BBFILES_DYNAMIC to use it when appropriate. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iff12f641e57ace313ad64a402091444edba74ea4
2022-02-22meta-phosphor: remove custom BBFILE_COLLECTION parsingPatrick Williams1-8/+0
Switch from custom BBFILE_COLLECTION parsing to relying on BBFILES_DYNAMIC for any new layers. The existing layers (aspeed, nuvoton) have already been moved to the BBFILES_DYNAMIC mechanism. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ie67b95684349b6419e4608afba660607d0566803
2022-02-22meta-phosphor: migrate nuvoton-layer to dynamic-layersPatrick Williams1-0/+2
The proper way to add extensions to another layer is with BBFILES_DYNAMIC rather than adding to BBFILES based on BBFILE_COLLECTIONS. Move nuvoton-layer to a dynamic-layers subdirectory and hook into layer.conf using BBFILES_DYNAMIC. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ic1b1f0ce837a899c5060531735c75c73cf51f1f5
2022-02-22meta-phosphor: migrate aspeed-layer to dynamic-layersPatrick Williams1-0/+5
The proper way to add extensions to another layer is with BBFILES_DYNAMIC rather than adding to BBFILES based on BBFILE_COLLECTIONS. Move aspeed-layer to a dynamic-layers subdirectory and hook into layer.conf using BBFILES_DYNAMIC. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I26e5093d469ce0a57c0b93bcc6b3383dd7bcf264
2022-02-12meta-phosphor: change connectivity url to yoctoprojectAndrew Geissler1-1/+1
www.example.com is having intermittent connection issues, causing a lot of intermittent openbmc builds fails in CI. Upstream is moving to https://www.yoctoproject.org/ so we should as well. Upstream: https://lists.openembedded.org/g/openembedded-core/message/161662 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Iae7c2debcfe294e3facca25ad47a6b8434449769
2022-01-14phosphor-base: Remove unused recommended e2fsckWilliam A. Kennington III1-0/+3
Our builds with MMC will explicitly depend on this as needed. No other BMC builds should need this utility normally and it gets included with all builds. Change-Id: I4ce0303dfd4646579d70f79be3e6af9b191ca45a Signed-off-by: William A. Kennington III <wak@google.com>
2021-12-17meta-phosphor: prefer https protocolPatrick Williams1-1/+1
A few recipes are specifying 'protocol=git' to the git-fetcher, which is already the default[1]. For github URLs, upstream Yocto / OE suggest that 'protocol=https' is used[2]. Switch any URL that has a protocol specified to be 'https' instead of 'git'. 1. https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-fetching.html#git-fetcher-git 2. https://lists.openembedded.org/g/openembedded-devel/message/94255 Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ibf1ab0fa2cb83c8cb9f4e535a0781f41e3b0dafe
2021-12-02Remove BBLAYERS_NON_REMOVABLE variableAlexander Filippov1-10/+0
`BBLAYERS_NON_REMOVABLE` is obsolete and no longer required. As it said by Yocto documentation it can be used by `Hob` https://www.yoctoproject.org/docs/1.5.2/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE that already removed since Yocto-2.1 https://www.yoctoproject.org/tools-resources/projects/hob Change-Id: Ibc2d8268a9d837a81e9cf6b0131dba8d0a030a3f Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
2021-11-10meta-phosphor: remove obmc-system-mgmt from qemuPatrick Williams1-2/+4
It was reported that after 5a5f33c729e6b5869362172b63595422eb84a418 the qemu images are not buildable. Treat qemu systems like an 'evb' so that the obmc-system-mgmt package is not included. Make a minor change to how evb is specified so that it is treated as a MACHINEOVERRIDE that can be leveraged in multiple recipes. Tested by ensuring that `evb-ast2600` still successfully resolves all package dependencies (with `bitbake -p`). Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iff4573aa3d4aac30a6681ed75741a6e351bda982
2021-11-04Partially revert "treewide: remove obmc-system-mgmt feature"Patrick Williams2-0/+3
The obmc-system-mgmt feature is currently used in the image to trigger inclusion of a virtual-provider which provides a number of packages many systems need. Partially revert the removal of this feature so that the outcome is: 1. The empty obmc-phosphor-sysd package is still removed. 2. By default the 'obmc-system-mgmt' feature is included, unless specifically exempted. 3. All EVB platforms remove the 'obmc-system-mgmt' feature since they have no system they are managing. This partially reverts commit 060ad3ff7fcc30aff78a9e504efee9d8fa0d4526. Tested: * Built `bletchley` and confirmed `packagegroup-fb-apps-system` and `entity-manager` are present. ``` entity-manager armv7ahf-vfpv4d16 0.1+git0+6bf41588ab-r0 packagegroup-fb-apps-system all 1.0-r1 ``` * Built `witherspoon` and confirmed `packagegroup-op-apps-system` and `pdbg` are present. ``` packagegroup-op-apps-system noarch 1.0 pdbg arm1176jzs 3.3 ``` * Ran `bitbake -p` on `evb-ast2600` to confirm the undefined `virtual-obmc-system-mgmt` is not being included in the image. Change-Id: I8b7804d5101cc84a2c57473b3f85672bf7767c67 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
2021-10-26treewide: remove obmc-system-mgmt featurePatrick Williams2-3/+0
Every machine layer treats 'system-management' as either part of a package-group or removes the feature. The sample implementation in meta-phosphor is a do-nothing shell script (and up until recently was a Python script). There appears to be no useful purpose to this feature as a stand-alone concept, so remove it. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I20ca1fa8ff3cb01cac2d07d4ded84e0769e4514b
2021-10-26meta-phosphor: remove OBMC_MACHINE_FEATURES indirectPatrick Williams1-4/+0
Clean up the final part of this indirect, which is the append of the variable to the MACHINE_FEATURES one. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I2077d7acff5602b7bf333677f5866d979bdaa07c
2021-10-15u-boot-aspeed: Add distro feature to enable SPI master modeChanh Nguyen1-0/+2
The ast2500 shares the RGMII1 pin and the hw strap pins for SPI interface mode selection ( pin[12:13] ). In some systems, the RGMII/NCSI interface will use the pin. It makes the SPI interface mode setting is not correct. This patch adds a distro feature to enable the SPI master mode by default. Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com> Change-Id: I93e5dd5e86870601169974aa1aab4b5480a45ef1
2021-09-16bitbake: Use IPK packaging for rootfs assemblyAndrew Jeffery1-1/+1
bitbake offers a choice of DEB, RPM or IPK packaging. To a degree the choice is functionally arbitrary for image generation but control over the package format becomes important if we want to: 1. Include runtime package management functionality in the firmware image 2. Mess about with the packages on the build system With respect to 1 the IPK format and opkg (an ipk package manager) are designed for embedded systems[1] - by contrast to RPMs have heavier dependencies and a greater impact on the size and complexity of the firmware image. Regarding 2, the embedded nature and the need for opkg to work without much fuss leads to a lower configuration barrier by comparison to RPMs. With ipk it becomes possible to reuse the packages built during image preparation for core analysis without needing to generate an SDK: ``` $ export LD_LIBRARY_PATH=./tmp/work/x86_64-linux/opkg-native/*/recipe-sysroot-native/usr/lib $ MY_DEBUG_ROOT=tmp/rootfs-debug $ ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \ -f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/*/opkg.conf \ -o $MY_DEBUG_ROOT \ update $ fakeroot ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \ -f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/opkg.conf \ -o $MY_DEBUG_ROOT \ install dbus-sensors dbus-sensors-dbg $ gdb-multiarch (gdb) set solib-absolute-prefix .../tmp/rootfs-debug (gdb) add-auto-load-safe-path .../tmp/rootfs-debug (gdb) file tmp/rootfs-debug/usr/bin/nvmesensor (gdb) core-file obmcdump_17_9597/core.nvmesensor.0.aae91b519d0e4e0e8bbe746e3f6cd25f.2779.9594000000 Core was generated by `/usr/bin/nvmesensor'. Program terminated with signal SIGABRT, Aborted. pthread_kill.c:45 45 pthread_kill.c: No such file or directory. (gdb) bt pthread_kill.c:45 ../sysdeps/posix/raise.c:26 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 "xyz.openbmc_project.NVMeSensor", this=0x488f04) at /usr/include/sdbusplus/bus.hpp:234 ../../../../../../workspace/sources/dbus-sensors/src/NVMeSensorMain.cpp:159 (gdb) ``` This approach documented in the Poky Reference Manual: https://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html#platdev-gdb-remotedebug-launch-gdb-inferiorbins Switch all machines to IPK to align the debugging experience with upstream's documentation and to facilitate efficient use of packaged software at runtime. [1] https://openwrt.org/docs/guide-user/additional-software/opkg Change-Id: I8ef526add2d7a6790de1b3eb3fb85cd39b864f23 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
2021-08-31add seccomp to DISTRO_FEATURESAndrew Geissler1-0/+1
Commit aff0243 added seccomp to the systemd PACKAGECONFIG. The libseccomp recipe requires seccomp be a DISTRO_FEATURE. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Iee1d5e9b2efe8284454c0b5125d9de7b43c1bdb0
2021-08-25meta-phosphor: enable DISTRO_FEATURE 'security'Patrick Williams1-0/+1
The meta-security layer requires the DISTRO_FEATURE 'security' set otherwise it gives a warning: WARNING: You have included the meta-security layer, but 'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files and preferred version setting may not take effect. See the meta-security README for details on enabling security support. This DISTRO_FEATURE doesn't really seem to do anything except enable an additional include file in the linux-yocto recipe (which itself then checks other features). It seems entirely safe for us to enable this feature everywhere to avoid the warning. $ git grep -A4 "DISTRO_FEATURES" | grep "'security'" meta-security/README:to have 'security' in DISTRO_FEATURES to have effect. meta-security/README: 'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files meta-security/classes/sanity-meta-security.bbclass: if 'security' not in e.data.getVar('DISTRO_FEATURES').split() and not skip_check: meta-security/classes/sanity-meta-security.bbclass:'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files \ meta-security/recipes-kernel/linux/linux-yocto_5.%.bbappend:require ${@bb.utils.contains('DISTRO_FEATURES', 'security', '${BPN}_security.inc', '', d)} Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ife1549783b356f87f429466f260f34b9a41d002c
2021-08-24treewide: remove gategarth from layer-supportPatrick Williams1-1/+1
We've typically kept these LAYERSERIES_COMPAT to 2 releases: the current and the upcoming. Remove 'gatesgarth' is it is now 2 releases back. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I5e812a94fed1738898af75c0fdee81996a5bbf20
2021-08-17Add ppc64le to QEMU_TARGETSAnton Blanchard1-1/+1
We want to build OpenBMC on ppc64le, so add it to QEMU_TARGETS. Signed-off-by: Anton Blanchard <anton@ozlabs.org> Change-Id: Ice8735a105f40c938dde42061d2e33ddf55a07dc
2021-08-11meta-{aspeed,phosphor}: layer.conf: Override syntax cleanupAdriana Kobylak1-1/+1
LAYERVERSION should keep underscore instead of colon. Change-Id: I53b0af2fd8c756d09a11ee2c970910cdf7331738 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-08-11meta-phosphor: increment CONF_VERSIONPatrick Williams1-1/+1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ib334e243bb2293148b6bf3587c79a77e46bd8ce3
2021-08-11meta-phosphor: prep for new override syntaxPatrick Williams6-29/+29
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
2021-08-10Change default password hashJoseph Reynolds1-1/+5
Background: OpenBMC provisions the BMC firmware image with the root account password in a form which is no longer acceptable to Linux-PAM version 1.5.1. Specifically, [phosphor-defaults.inc][] sets the password hash into /etc/shadow as "\$1\$UGMqyqdG\$FZiylVFmRRfl9Z0Ue8G7e/", where $1 indicates the deprecated [MD5 hash algorithm][].  Ref: [wikipedia passwd entry][].  Beginning around PAM version 1.5.1, when you log in, the [pam_unix.so module][] authenticates okay but requires the password to be changed.  (For example, you'll get a message like "You are required to change your password immediately (administrator enforced)."  This behavior is undesirable for OpenBMC project defaults, and is not tolerated by the project's current continuous integration tools.) This change is to replace the password hash to keep the same cleartext password but hashed with an acceptable algorithm. Specifically, the password hash supplied in phosphor-defaults.inc is updated to use the same password as before but encoded with the SHA-512 algorithm.  The hash was generated by the `openssl passwd -6 0penBmc` command.  This change ought to be transparent and forward and backward compatible. Note various meta-layers use this same hash string in conf/local.conf.sample files. They are changed to match. References: [phosphor-defaults.inc]: https://github.com/openbmc/openbmc/blob/1a977b269ed437bebb9ae7810e3157746ec9174d/meta-phosphor/conf/distro/include/phosphor-defa ults.inc#L245 [wikipedia passwd entry]: https://en.wikipedia.org/wiki/Passwd [pam_unix.so module]: https://github.com/linux-pam/linux-pam/tree/master/modules/pam_unix [MD5 hash algorithm]: https://en.wikipedia.org/wiki/MD5 Tested: Created image with new password hash and PAM 1.5.1 and checked that login works okay and does not require the passwod to be changed. Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net> Change-Id: I5b189374f08ba506dbed7f8b9b991f2808cc3bc5
2021-08-10Remove redundant code to set root passwordJoseph Reynolds1-0/+1
Background: The OpenBmc project default root account password is set in meta-phosphor/conf/distro/include/phosphor-defaults.inc and can be customized in each layer's local.conf file. Many of these local.conf.sample files had redundant code to set the password, which probably should not have been there. Removing them allows the defaults in phosphor-defaults.inc to take effect. Tested: No. Only meta-ibm was tested. Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net> Change-Id: I76dce00d269d7afa005d7bcfd63f846d3cf45596
2021-06-23meta-phosphor: os-release: Set weak default to DISTRO_VERSIONWilly Tu1-1/+0
Improved practice to use DISTRO_VERSION instead of the undocumented VERSION_ID. DISTRO_VERSION is documented in yocto https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html and specified in this section about creating your own distribution. https://docs.yoctoproject.org/dev-manual/common-tasks.html#creating-your-own-distribution VERSION_ID is undocumented and will more likely be changed compared to the documented DISTRO_VERSION. The VERSION_ID is set to DISTRO_VERSION in poky/.../os-release.bb Use weak default to DISTRO_VERSION instead of overriding VERSION_ID. This allows other layers to override in *.bbappend or *.conf. Tested: ``` root@romulus:~# cat /etc/os-release ID=openbmc-openpower NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="2.11.0-dev" VERSION_ID=2.11.0-dev-165-g20885c497 PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 2.11.0-dev" BUILD_ID="2.11.0-dev" OPENBMC_TARGET_MACHINE="romulus" ``` Signed-off-by: Willy Tu <wltu@google.com> Change-Id: I25b5a165b764e6562fa8008c9d2a75a82fb09139
generated by cgit v1.2.3 (git 2.39.0) at 2024-09-06 10:37:16 +0300