| commit | e9feb95759ed17b5f9014d1a0af7ea4c3bc4e9fc | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Fri Jul 22 19:26:54 2022 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Aug 10 14:56:38 2022 +0000 |
| tree | 039a4d4017789b75f1878dde0422417a4c62a24c | |
| parent | 53c6d0c7e2766df450f6605dd1815469fec648a1 [diff] |
sdbusplus: use shorter type aliases The sdbusplus headers provide shortened aliases for many types. Switch to using them to provide better code clarity and shorter lines. Possible replacements are for: * bus_t * exception_t * manager_t * match_t * message_t * object_t * slot_t Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Id93b8dfb6c81f62647dd56f1ce04c1a4fda4f7f4
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