| commit | 3b4737761094a4ae00b5d7052e00baee0a5c1bc8 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Fri Nov 13 15:27:32 2020 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 18 16:07:05 2020 +0000 |
| tree | c8b3552efdfe3c3de1943adc5e1cce77e22ead69 | |
| parent | 5364764e2e76ff3533254cfa2ddc466ccb2f8b31 [diff] |
boot-progress: add new pldm/redfish progress enums The following design doc describes the new Redfish BootProgress schema and OpenBMC's support of it: https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/32988 This commit adds these new boot progress enumerations while also leaving MotherboardInit (which does not have a mapping to the new Redfish BootProgress object) so as to continue to support systems still utilizing it. If needed, MotherboardInit could be mapped to one of the Redfish BootProgress values. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I9cb6714ea4044ca3b19724029478172d2af732d2
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