| commit | e0764cf41d16b823a519e9d4f508b588e3e84aba | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Thu Oct 28 16:10:46 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Nov 15 17:16:43 2021 +0000 |
| tree | d538db44edbb182d339e1f3f9ab099b8ba3b3ab9 | |
| parent | ab2ce4eaccf518e3fe707e1d5b43db67a6d5e8df [diff] |
host-state: introduce new host crash restart reason In situations where the host firmware crashes, and BMC firmware detects it, the BMC will attempt to recover by initiating a reboot of the host firmware a certain amount of times. On IBM systems, the host needs to know when a crash is the reason for a boot. This property will be utilized by the host communication firmware to tell them. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ibf18c1ac084ec8fb0b0ab3985623ed41f01f65ad
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.
The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.
Only the xyz/openbmc_project interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir