summaryrefslogtreecommitdiff
path: root/meta-openpower/classes/openpower-software-manager-ubi.bbclass
AgeCommit message (Collapse)AuthorFilesLines
2021-08-11meta-openpower: prep for new override syntaxAdriana Kobylak1-2/+2
Change-Id: I5ca16c6fa7bc616bfa9bc41c4f86d32fd92b0287 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2020-07-15openpower-pnor-code-mgmt: srcrev bump 573552ae8e..bbb5e3bec1Andrew Geissler1-31/+0
Adriana Kobylak (1): vpnor: Move clearvolatile services to vpnor Andrew Geissler (2): ensure volatile clear waits on dependency ensure volatile clear occurs after reset check Also added to this commit is the movement of the service files from ubi to vpnor (required with the above commits) (From meta-openpower rev: 8b70bb894a3c16d10bf5d11fd26bbc9ea6c3bae1) Change-Id: Ie464de2d4f7abad6e0a3ae2edc1df1b7c740e559 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-06-26clear host volatile section on chassis poweronAndrew Geissler1-0/+16
When using istep to boot a openpower based system, the flow is to issue a "obmcutil chassison" and then boot the system using the istep tool. istep does not use the host-start targets so therefore the host volatile data is not cleared. To ensure the data is always cleared, add the services to the chassis-poweron target. The services need to remain within the host start targets to handle warm reboot scenarios. A normal "obmcutil poweron" will run both the host and chassis targets but due to them being started at the same time (and letting systemd figure out the ordering), the volatiles services will each only be run once so there is no extra execution due to this commit. If a user were to just issue a "obmcutil chassison" and then follow that with a "obmcutil poweron" then the services would be run a second time. This scenario is a debug only type situation and the extra second to re-run the services would have very minimal impact. There is a desire to move services from requires to wants relationships. That was not done here because of the undefined behavior seen by the host when this data is not cleared. The required behaviors is to fail the power on or host start if these services fail. Tested: - Verified services were in obmc-chassis-poweron@0.target.requires - Verified services were run as expected issuing a chassison - Verified boot of system worked as expected and services were only executed once during "obmcutil poweron" (From meta-openpower rev: 9a967ec383a6f0d0a7e3d7a61d48b35c8aaf8f1c) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I5ea6ef27cd29d488fa3b7b3bf93a73f1112d1120 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-11-11openpower-software-manager: New virtual pnor bbclassAdriana Kobylak1-1/+0
Create a new virtual pnor bbclass to hold the updatesymlinks systemd service file. This service file was moved because it doesn't depend on the filesystem layout. Enable it if the virtual-pnor distro feature is selected. Tested: Verified the service file was still present on witherspoon since the virtual pnor distro feature is part of ubi. (From meta-openpower rev: 86c282465aa3d601fcc949233049558ee6851d30) Change-Id: Id2d91e5bbcce93ed6d8c6750a0fa54fcf5a9615b Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-14openpower-software-manager: Use in-repo script and systemd unitsAdriana Kobylak1-8/+0
Use the script and systemd service files provided by openpower-software-manager. Remove the op-pnor-msl.service from the ubi bbclass since it's already being included from the main recipe. Tested: Verified the service files were present on the image and PNOR updates were successful. (From meta-openpower rev: b3d3c717140ed02d116174d6496a7cb291369b78) Change-Id: I4f77c9bb5869a2380247b7b6a1c772ab98cddf10 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-03openpower-software-manager-ubi: install obmc-flash-bios into binAdriana Kobylak1-2/+2
OpenBMC executables should be installed in bin, reference: https://github.com/openbmc/docs/blob/master/anti-patterns.md#placement-of-applications-in-sbin-or-usrsbin The systemd service files for the openpower updater still run: "ExecStart=/usr/bin/env obmc-flash-bios" so this change does not affect them. A subsequent commit will change them to point to bin. Tested: Verified obmc-flash-bios was in /usr/bin/ in the BMC and that a PNOR code update was successful. (From meta-openpower rev: 200786912b557fdb9c254474d6732deea00979ab) Change-Id: I00dd1f210aad03be1010b7c27b4a9cc898352e00 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-02openpower-software-manager: Support ubi and static layoutLei YU1-0/+35
Move ubi and static specific configures into bbclass, and inherit the bbclass in openpower-software-manager recipe. Tested: Verify Romulus build uses the static bbclass, and Witherspoon uses the ubi bbclass. (From meta-openpower rev: 2c2604d36e9415396baf1936b07a6a974b376cd9) Change-Id: I23f68486ab95802785f7c5c22232a9f2b76d0341 Signed-off-by: Lei YU <mine260309@gmail.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>