commit | fe9fbc1362bd9e7a55b6d3a2edd60370a4649245 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Dec 08 06:12:55 2022 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Mon Dec 12 09:03:38 2022 -0600 |
tree | 044e0ea1cbaf66bb5ef6a20461e84d9bb48a550c | |
parent | eddf960a4377a0573f85b69c4fdd886d450f7a25 [diff] |
prettier: re-format Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML files to have consistent formatting for these file types. Re-run the formatter on the whole repository. Change-Id: I4c6395d774287f086af0b673ab3a900561b6344f 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