| commit | d4430278581a501ebaa80a7c6084867529224b0f | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Sat Feb 01 08:36:58 2025 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Sat Feb 01 08:36:58 2025 -0500 |
| tree | b93f6c4afa27aee76ab544bb28e1b3d04552a3ae | |
| parent | fb9733670e07409b5b9d475a60dbfbee8c470565 [diff] |
meson: reformat with meson formatter Apply the `meson format` results. Change-Id: I10e74170cec30d5aca487f1082c635441ad238a7 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