commit | 5c75dd56c86b46fce6763bed11e16cadd4c461b0 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 12 11:15:27 2023 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Jul 12 11:15:28 2023 -0500 |
tree | 4c3174c449f22cc2f48eafd9f22a1b95798e6708 | |
parent | e7e197b3afc0ce14c5fcbf5c1da00dd04b65e2aa [diff] |
build: upgrade to C++23 Meson 1.1.1 and GCC-13 both support C++23 and a sufficient portion of the standard has been implemented. Upgrade the build to leverage it. Change-Id: Ic6ef0ad86b97a49792b40317bcb39311c49e233e 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