| commit | 8eb4d58b7c3d4edf5b2b3485b14c560a041a0537 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 29 06:44:22 2023 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 29 06:44:22 2023 -0600 |
| tree | ba035b3b433a2da20910ae37695dcecae10fbb3b | |
| parent | 608a392189d48ff0f0b94d2f21d9dd7a99323872 [diff] |
build: use allowed over enabled Meson feature options are typically in a tri-state of enabled, disabled, or auto. The enabled and disabled functions on an option (from `get_option`) no longer return true for auto features. Instead, the expectation is to use `allowed()` which is true for both enabled and auto. Switch all uses of `enabled` to `allowed`. Change-Id: I8a8a5b86aaeb9ae6835ca26b22a8e21e4438bb52 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 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