commit | a27519e987a8341585e50913930862825c48cd26 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Aug 04 11:40:12 2022 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Aug 10 14:57:27 2022 +0000 |
tree | 48fa93950b3fbde2ee151cef56d24f3b2655a462 | |
parent | e9feb95759ed17b5f9014d1a0af7ea4c3bc4e9fc [diff] |
MAINTAINERS: remove file The MAINTAINERS file is deprecated in favor of OWNERS. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I0da7cb31f85fc8f1fd4d1a1fccfe92c683e69286
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