| commit | eddf960a4377a0573f85b69c4fdd886d450f7a25 | [log] [tgz] |
|---|---|---|
| author | Jonathan Doman <jonathan.doman@intel.com> | Wed Nov 23 09:29:41 2022 -0800 |
| committer | Jonathan Doman <jonathan.doman@intel.com> | Wed Nov 23 11:25:18 2022 -0800 |
| tree | 2b5b8b3e7de892810284f258eb88fab3bcb0663a | |
| parent | c1819379d12c286c8f17175f76e970d14c73d480 [diff] |
Update .clang-format and reformat Update the local .clang-format to the example configuration and reformat all the source code, as well as line wrap the README text. Signed-off-by: Jonathan Doman <jonathan.doman@intel.com> Change-Id: I996d96a14a271612e03113013e29f4613b782c35
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