-
The [frus.sch](https://github.com/HistoryAtState/frus/blob/master/schema/frus.sch) Schematron file enumerates the allowed values for `div/@subtype` values. The list there is drawn from the values that…
-
APIs for I/O Enclosure: Config, Firmware Policy Update, Firmware Update
This includes FRUs on the MEX IO expansion drawer
GUI story is #617
Redfish?
-
This epic tracks all the VPD function needed for Rainier HW poweron:
* Data needed by PHYP over PLDM (Location Codes, and system blueprint).
* Collection of Module VPD (SPI)
-
As @KerryHite reported: In `frus1941v06/d125`, the non-numeric "a" in footnote "60a" appears as the inline footnote callout but not as the footnote reference in the note itself (currently, "60"). We…
-
Rainier fans won't have vpd eeproms, so need to create and store in dbus. Get pertinent info from config file of some sort.
Need to ensure vpd from hot-plugged fan is re-stored. This done with ht…
-
This story is used to track the inventory item interfaces for all guardable FRUs/FRU subunits.
Add the below inventory item interfaces for all guardable FRUs/FRU subunits because, those **interfac…
-
On the GUI roadmap as
FRU’s Concurrently Maintainable (TOD Battery & Op/Control Panel).
I don't see anything in Assembly but Drive has
"ReadyToRemove": {
"de…
-
Manufacturing Replaceable Units are are more specific than FRUs.
Need to figure out how an application will get the MRUs to phosphor-logging for a callout.
-
Not everything in the inventory is a FRU, so not all paths will have the LocationCode or FN/SN/CC VPD interfaces. For example, a core. It would be nice to be able to support CALLOUT_INVENTORY_PATH …
-
## Use Case
- As a PE/SSR, I need to be able to perform detailed analysis related to a hardware fault, so that I can point out which hardware components need to be serviced/replaced.
- As an SSR, …