BMC/tmp/openbmc.git/meta-phosphor/classes, branch 2.13.0-dev

Fix the bug that devtool modify u-boot is not picked up by image-bmc

2022-03-31T15:50:15+00:00

Previously when u-boot code was changed inside a devtool modify repo, the u-boot artifacts were updated but they could not be picked up by the final image-bmc. The reason was that the sstate version of u-boot was used because the dependency between u-boot and obmc-phosphor-image was not set up properly. Fix the issue by adding the proper inter-task dependency between the two. Tested: The image-bmc md5sum changes as expected when u-boot code is changed. Change-Id: Ic98d3097f66e351c774ced4ee435149b5441cf67 Signed-off-by: Yong Zhao

image_types_phosphor: Add compatible name to MANIFEST

2022-03-28T14:02:04+00:00

This adds CompatibleNames field to the manifest file which can contain compatibility strings as described in the Software interface. The field is set by the OBMC_COMPATIBLE_NAMES variable in the machine.conf file, e.g. OBMC_COMPATIBLE_NAMES = "\ foo.bar \ baz.bim \ " Also omit ExtendedVersion from the manifest file if it is not set. Signed-off-by: Justin Ledford Change-Id: Id27b4d6ec25ec7c3d3d5942368f40e618535eafe

treewide: fix up github SRC_URIs

2022-01-25T16:37:00+00:00

Per [1], Yocto is going to start requiring both branch names and `protocol=https` in GitHub SRC_URI variables. Ran the upstream tool to automatically fix our URIs. 1. https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n10 Signed-off-by: Patrick Williams Change-Id: I5f9619f7ff707050b469ae74c8aa16846568c5e4

Add bbclass to copy license info to /usr/share/www

2021-12-15T19:25:40+00:00

Some products have requirements for the source license info to be made available to users. This adds a bbclass that copies the license info stored in /usr/share/common-licenses to /usr/share/www/common-licenses. From there it is served to users by bmcweb in the existing webassets.hpp functionality. File paths will show users the file content, but directories will only display content in an index.* file. So, the bbclass also creates an index.json for each directory so that directory paths will show users the directory contents. Tested: Navigated to /common-licenses and common-licenses/ and confirmed that the directory listing was displayed. Navigated to /common-licenses/bmcweb and common-licenses/bmcweb/ and confirmed that the directory listing was displayed. Navigated to /common-licenses/bmcweb/LICENSE and confirmed that the license text was displayed. Navigated to /common-licenses/../../network/config.json and it returned "Not Found". Navigated to /common-licenses/../ipmi-providers/channel_access.json and it returned "Not Found". Change-Id: I286b0cf53a9520087b1a57b17ea66f408f08ed3b Signed-off-by: Jason M. Bills

meta-phosphor: remove obmc-system-mgmt from qemu

2021-11-10T18:11:44+00:00

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 Change-Id: Iff4573aa3d4aac30a6681ed75741a6e351bda982

image_types: Add BUILD_ID to MANIFEST

2021-11-09T21:54:55+00:00

Add the BUILD_ID value to the MANIFEST so that it can be used alongside the VERSION value to generate a version id during firmware updates. Add a function to read BUILD_ID from the os-release file instead of reading it from a variable because the BUILD_ID value could be set via a os_release.bbappend file instead of a .conf file. Tested: Verified the BUILD_ID value was added to the MANIFEST by default, and when BUILD_ID was specified in a .conf file, and on a os-release.bbappend. Ex: $ cat MANIFEST purpose=xyz.openbmc_project.Software.Version.VersionPurpose.BMC version=2.11.0-dev-566-g263df7f852 BuildId=20211025151654 ExtendedVersion= KeyType=OpenBMC HashType=RSA-SHA256 MachineName=p10bmc Change-Id: I3b7beaccbbd47d8820d499180ccdf021b004cf85 Signed-off-by: Adriana Kobylak

Partially revert "treewide: remove obmc-system-mgmt feature"

2021-11-04T09:36:33+00:00

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

skeleton: srcrev bump 81100ae9ee..77b241c472

2021-10-27T23:10:03+00:00

Manojkiran Eda (1): Add OWNERS file Change-Id: I7baeec6ca85478efeee3ee8ef80536527abc6890 Signed-off-by: Andrew Geissler

treewide: remove obmc-system-mgmt feature

2021-10-26T16:15:19+00:00

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 Change-Id: I20ca1fa8ff3cb01cac2d07d4ded84e0769e4514b

Fix phosphor-deploy-ssh-keys.bbclass

2021-10-22T21:57:30+00:00

The logic was broken due to lack of quotes around the semicolon delimiters inside subshell commands. It did not work for single keys nor multiple keys provided in SSH_KEYS. This commit adds proper quotes, and also refactors the loop a bit to reduce repeated commands, reduce indentation, and clarify variables. Tested: - Added INHERIT/SSH_KEYS to local.conf as described in script comments. - Tested with 1 key: "root:/path/to/key.pub" and 2 keys "root:/path/to/key.pub;root:/path/to/key2.pub". - Verified that in all cases keys were added to authorized_keys files exactly once by checking rootfs output: (build/tmp/work////rootfs/home/root/.ssh/authorized_keys) Signed-off-by: Jonathan Doman Change-Id: I58af4e8107daa6447b8276a66fc7c91e346c7dd5