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
1 file changed
tree: c8b3552efdfe3c3de1943adc5e1cce77e22ead69
  1. com/
  2. gen/
  3. org/
  4. subprojects/
  5. xyz/
  6. .gitignore
  7. LICENSE
  8. MAINTAINERS
  9. meson.build
  10. meson_options.txt
  11. README.md
README.md

phosphor-dbus-interfaces

YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.

Building

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.

Configuration

Only the xyz/openbmc_project interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References