| commit | 4461e14097547ca2b85945e371c260c40a5d6d86 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Mon Jan 25 14:56:08 2021 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Feb 10 20:10:39 2021 +0000 |
| tree | 21c29d4fc3349a3c3300a1f2fdeee0acfe1c3b2b | |
| parent | 3a77dc425f5eb9237de4d78f7099b1f0a3062ab7 [diff] |
introduce standby state for host interface Certain host firmware implementations of this interface have the concept of a standby/safe state. The host firmware has done it's basic initialization but it has not executed to the point where it can start operating system instances. A common use case for this on IBM systems is when a system is being serviced and the technician wants to log into the host firmware to check hardware status before continuing to start the operating systems. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ie0d0007b6859c8a23df83287ac27f251e2cf9b79
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