docs/designs/boot-progress.md

51 As of [ComputerSystem.v1_13_0][7], the `BootProgress` object is officially in
54 To summarize, the `LastState` property under this new `BootProgress` object
68 There is also a `LastStateTime` associated with this new BootProgress object
75 it also does not preclude them. The `BootProgress` D-Bus property is associated
81 - Enhance the existing [BootProgress][3] D-Bus property to cover all supported
84   and time of the last update to `BootProgress`
85 - Ensure the `BootProgress` and `BootProgressLastUpdate` properties are updated
88     `BootProgress` property on D-Bus
90     `BootProgressLastUpdate` property on D-Bus when it sees `BootProgress`
93   appropriate mappings to the `BootProgress` and `BootProgressLastUpdate D-Bus
99 `BootProgress` D-Bus property and the ones which have a mapping to the Redfish
100 BootProgress object will be shown via the Redfish interface.
104 [BootProgress][3] will be enhanced to support a superset of what is provided by
107 IPMI code already sets the `BootProgress` D-Bus property based on a config file.
113 bmcweb will then use this `BootProgress` D-Bus interface to respond
122 mapped to the appropriate BootProgress value if desired (or for cases where the
123 host does not support an IPMI or PLDM stack that has BootProgress in it).
127 Each system will need to document which `BootProgress` codes they support and
132 Ensure an IPMI and PLDM based system boot and update the `BootProgress` D-Bus