summaryrefslogtreecommitdiff
path: root/meta-phosphor/classes/phosphor-software-manager-mmc.bbclass
AgeCommit message (Collapse)AuthorFilesLines
2021-04-06software-manager-mmc: Use zstd instead of zstd-binAdriana Kobylak1-1/+1
The commit meta-openembedded: subtree update:98175fd0cc..da393545a2 removed the zstd recipe (zstd_1.4.5.bb) from meta-openembedded and just left the one in oe-core (zstd_1.4.9.bb): Randy MacLeod (6): zstd: remove the recipe since it moved to oe-core The 1.4.5 recipe had a change to split the binaries by adding "inherit lib_package" to the recipe, but this change is not present in 1.4.9. We'll need to check for any zstd changes in future poky updates since the person that made the change to split the binaries in meta-openembedded might make a submission to port that change into the oe-core recipe. Even though this change will compile, it would break firmware updates on Rainier because only the zstd libraries would be installed and not the binaries. Therefore this commit must be submitted at the same time as the meta-openembedded subtree update. Change-Id: Ie7246195f5db42a1a0c402643439d312ad058a80 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-03-19software-manager-mmc: Use zstd-bin instead of zstdAdriana Kobylak1-1/+1
With openbmc commit 97771a3: "meta-openembedded: subtree update:7206f7f5bc..98175fd0cc", the zstd package was split into libraries and binary: Sean Nyekjaer (3): zstd: split bin into separate package This change added an "inherit lib_package" to the zstd recipe which creates a separate ${PN}-bin package. Therefore, need to use zstd-bin to include the binary. No need to keep zstd since the libraries are not needed for code update to extract the image files. Tested: Verified the zstd binary existed in the rootfs and code update was successful in Rainier. Change-Id: I379ec2b0d85090df5183e3581bc88384eaf4dbc6 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2020-09-01phosphor-software-manager-mmc: Set optional-images configAdriana Kobylak1-0/+1
Set the optional-images config option to image-hostfw, which is an image file added to the mmc code update tarball at build time. This config option enables signature validation on the files specified if signature validation is enabled and the optional file exists in the tarball. Tested: Verified signature validation was run over the image-hostfw file. (From meta-phosphor rev: 7625008312e8ce8db5e3c46b2c890dbe36718c25) Change-Id: Ifdd5c27b639453cca77d36f1209b50c7efea20ef Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-15phosphor-software-manager: mmc: Add update servicesAdriana Kobylak1-0/+13
The mmc config option in the phosphor-bmc-code-mgmt repo supports now mmc code update, add the depends and services. (From meta-phosphor rev: 98d1f319a22a88887c96ae80b58b8fe8d4b7ca97) Change-Id: Id32177e5d63b18ad9e1060770a031bcce91ae551 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-15phosphor-software-manager: Create a new mmc bbclassAdriana Kobylak1-0/+7
Add a bbclass for the mmc configuration option. (From meta-phosphor rev: 7df4aa01e4d35e6ec7294f08e4bd3f1d18e61f01) Change-Id: I6602362e511bcffae1e185a72861ae1edec050f9 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>