| commit | e709874a634cfe19350d31b06bbfec3c8f61a826 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Mon Mar 21 10:01:23 2022 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Mar 21 10:01:26 2022 -0500 |
| tree | 9aee30a5083a1c97effbe50ce3d0d5fc0f91f29e | |
| parent | bd706d79b15a974b2c346df85a78271e21c3fc62 [diff] |
meson: simplify dependencies Leverage wrapfile `[provide]` directives to simplify the dependency searching in the meson.build. Change-Id: I7b37d6b9a0aa7b4a5df6f5a2bf28156b4043fc9a
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