| commit | 4e1910bb8c85693557904c18079b9f2d8f32101b | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Sat Feb 01 08:22:19 2025 -0500 |
| committer | Zhikui Ren <zhikui.ren@intel.com> | Thu Feb 20 20:02:45 2025 +0000 |
| tree | 2ba3cc62f78e766679689b2c75bd6a43fce60909 | |
| parent | d4430278581a501ebaa80a7c6084867529224b0f [diff] |
clang-format: update latest spec and reformat Copy the latest format file from the docs repository and apply. Change-Id: Iac0e4028f0f9b69046acdd35a4f531680793fe3d Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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 repository 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