commit | 987f91a6536e0330799cc5f4e54740c4023b5ef0 | [log] [tgz] |
---|---|---|
author | Manojkiran Eda <manojkiran.eda@gmail.com> | Tue Dec 21 04:48:41 2021 +0530 |
committer | ManojKiran Eda <manojkiran.eda@gmail.com> | Wed Dec 29 11:13:48 2021 +0000 |
tree | 3122540a235b795eed812589661f2ed943a42b55 | |
parent | f5e52db77cb580b2a6e9b95d06e26bfd185627d9 [diff] |
post-code-manager: Add documentation This commit would attempt to add few basic details on how to build post-code-manager & the dbus service that it exposes. Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I6b9b350e6009f008fb5c186320884f527b97624a
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