| commit | d01d1f84191894ad605a9ba5b546280bcfc64f7d | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Fri Feb 26 15:00:27 2021 -0600 |
| committer | Andrew Geissler <geissonator@yahoo.com> | Tue Mar 02 16:35:27 2021 -0600 |
| tree | 3d0ff7d3346c15afb86dcbca63bb19ffe451c711 | |
| parent | 43341f5846e769b760a53ad6502b61e3782523b8 [diff] |
boot-progress: introduce new setup state Some OpenBMC systems have an option to boot into a setup state where the user can interact with the host via a KVM or virtual tty interface. Commonly this is the BIOS setup menu on a computer system. The PLDM "Boot Progress" sensor in DSP0249_1.0.0.pdf defines this state as "7 – User-Initiated System Setup " The DMTF also has a "SetupEntered" coming for their BootProgressTypes enumeration. This will be released as a part of the 2021.1 release. This new D-Bus enum value will be how we connect the host PLDM sensor with the Redfish BootProgress API. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ic3c68ddc16e4afeb782c6bfdabea62b03a3eee32
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