| commit | 42d56641672707cd8ca89d87e1fc1be8a1b4ce42 | [log] [tgz] |
|---|---|---|
| author | kuiying <wangkuiying.wky@alibaba-inc.com> | Fri Dec 09 19:43:41 2022 +0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Dec 12 12:26:43 2022 -0600 |
| tree | 66193d427fa01e47853cede6da3ad974b86e84e2 | |
| parent | fe9fbc1362bd9e7a55b6d3a2edd60370a4649245 [diff] |
Updagte Kuiying's email address Kuiying's email address is changed to wangkuiying.wky@alibaba-inc.com Signed-off-by: kuiying <wangkuiying.wky@alibaba-inc.com> Change-Id: I1d9ebe26aa3872c85e93b2a962380097597b2d76
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