| commit | 99a87b6f141bb1d13af4053f5518e4193cc055b6 | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@inspur.com> | Wed Aug 16 10:04:53 2023 +0800 |
| committer | George Liu <liuxiwei@inspur.com> | Wed Aug 16 10:04:53 2023 +0800 |
| tree | fa3b0f1c00f4800042267495520ea26e09d98edb | |
| parent | 5c75dd56c86b46fce6763bed11e16cadd4c461b0 [diff] |
meson_options.txt: Support for reading options from meson.options Support has been added for reading options from meson.options instead of meson_options.txt[1]. These are equivalent, but not using the .txt extension for a build file has a few advantages, chief among them many tools and text editors expect a file with the .txt extension to be plain text files, not build scripts. [1] https://mesonbuild.com/Release-notes-for-1-1-0.html#support-for-reading-options-from-mesonoptions Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I6e7b4133bc4254ebb5eb1e02390080ab704a8a34
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