commit | 53c6d0c7e2766df450f6605dd1815469fec648a1 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Fri Jul 22 15:53:34 2022 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri Jul 22 15:53:34 2022 -0500 |
tree | 1c7168f8a5fe60c760ff8e031fa8de55a801c473 | |
parent | e709874a634cfe19350d31b06bbfec3c8f61a826 [diff] |
OWNERS: switch 'matches' to 'matchers' The original OWNERS template had a mistake which used 'matches' instead of the field supported by the Gerrit plugin 'matchers'. Update the OWNERS file to have the correct field. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I4b5a63a99a895181ea0becd30581492d707107bf
This phosphor-post-code-manager repository provides an infrastructure to persist the POST codes in BMC filesystem & it also owns the systemd services that are responsible for exposing the BIOS Post Codes to rest of the world via redfish.
To build phosphor-post-code-manager package , do the following steps:
meson <build directory> ninja -C <build directory>
This repository ships xyz.openbmc_project.State.Boot.PostCode.service
systemd service along with its template version and a tiny binary that exposes the necessary dbus interfaces & methods to extract the POST codes per boot cycle.
This repository is tightly coupled with phosphor-host-postd OpenBMC respository which is responsible for emitting the dbus signals for every new POST Code.
phosphor-post-code-manager is architected to look for the property changed signals which are being emitted from the service that hosts Value property on xyz.openbmc_project.State.Boot.Raw
interface & archive them per boot on the filesystem, so that those can be exposed over redfish