BMC/OpenBmc/openbmc.git/meta-openpower/classes, branch Add_Fan_PID_Control

openpower-pnor-code-mgmt: srcrev bump 6fc7fcd6b1..514a094e90

2021-10-27T00:33:57+00:00

meta-openpower: mmc: add reference to new bios reset service Isaac Kurth (2): item_updater_mmc: Add service calls to bios reset openpower: mmc: physical reset triggers bios reset Change-Id: I98a64189e3ce2da59f858e8f37bdb1363e50f6de Signed-off-by: Andrew Geissler Signed-off-by: Isaac Kurth

openpower-software-manager: Add PLDM option to p10bmc

2021-10-21T22:17:25+00:00

openpower-pnor-code-mgmt: srcrev bump 9c2ef681e3..6fc7fcd6b1 Adriana Kobylak (2): Add a new pldm feature option Add support for the host PLDM transport that takes place of hiomap (mboxd). Add this new feature to p10bmc. Tested: Verified that tacoma (that doesn't support pldm) and p10bmc (supports pldm) reached runtime. Change-Id: I31e8beba5ff8a413b7b7fa7476f5f2403d3781dd Signed-off-by: Andrew Geissler Signed-off-by: Adriana Kobylak

meta-phosphor: change systemd.bbclass to match upstream override syntax

2021-09-02T13:19:25+00:00

Upstream bbclasses changed to typically use the `:${PN}` override syntax, including the SYSTEMD_ variables. Change our systemd.bbclass to do the same for consistency and perform a tree-wide variable replacement. Spot checked by building bletchley and witherspoon and checking some of the SYSTEMD_LINK directives on installed packages under qemu. Signed-off-by: Patrick Williams Change-Id: I20a9dd809bff8af8759488734f80486c7228c6eb

meta-openpower: prep for new override syntax

2021-08-11T17:28:12+00:00

Change-Id: I5ca16c6fa7bc616bfa9bc41c4f86d32fd92b0287 Signed-off-by: Adriana Kobylak

openpower-pnor-code-mgmt: srcrev bump fdc91fa011..56f538ca26

2021-07-20T21:57:51+00:00

Adriana Kobylak (6): meson: Enable unit tests from x86 meson: Remove autotools support and update READMEs functions: Catch sdbusplus exception mmc: Move process host firmware to own service mmc: Add update-bios-attr-table subcommand functions: Set bios attribute property Add two new service files for the mmc layout option that handle the hostfw image files for hostboot to consume. Change-Id: I908b649f5e56d119a8b590a843d8086fc89315e2 Signed-off-by: Andrew Geissler Signed-off-by: Adriana Kobylak

openpower-pnor-code-mgmt: add bash and srcrev bump be20e8722e..067876aa2a

2021-05-12T00:57:34+00:00

The changes converted the virtual pnor script from sh to bash, so need to add bash as an RDEPENDS. Adriana Kobylak (7): generate-tar: fix shellcheck warnings generate-ubi: fix shellcheck warnings mmc/obmc-flash-bios: fix shellcheck warnings ubi/obmc-flash-bios: fix shellcheck warnings vpnor/obmc-vpnor-util: fix shellcheck warnings Enable shellcheck meson.build: switch to C++20 and meson >=0.57.0 Change-Id: Ic4c376cca3a028abcbc4e9df5dbf561173e1a1bf Signed-off-by: Andrew Geissler Signed-off-by: Adriana Kobylak

openpower-software-manager: Add mmc support

2020-07-18T18:32:53+00:00

Add support for the mmc configuration option based on the phosphor-mmc distro feature. (From meta-openpower rev: dc65d339226402e55a1c04f2092268fff88f0686) Change-Id: I344a357516ce4233fc4a3098a98670e80c78d139 Signed-off-by: Adriana Kobylak Signed-off-by: Andrew Geissler

openpower-pnor-code-mgmt: srcrev bump 573552ae8e..bbb5e3bec1

2020-07-15T18:35:35+00:00

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 Signed-off-by: Andrew Geissler

clear host volatile section on chassis poweron

2020-06-26T19:45:39+00:00

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 Change-Id: I5ea6ef27cd29d488fa3b7b3bf93a73f1112d1120 Signed-off-by: Andrew Geissler

openpower-software-manager: New virtual pnor bbclass

2019-11-11T12:49:52+00:00

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 Signed-off-by: Brad Bishop