commit | ad91cf9ac0166d8f468c0aaa414ec094c63168ee | [log] [tgz] |
---|---|---|
author | RekhaAparna01 <vrekhaaparna@ibm.com> | Wed Jan 31 03:40:19 2024 -0600 |
committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Wed Feb 14 15:48:23 2024 +0000 |
tree | 9fa146cd406143334caad3e752f07b3293b53dc0 | |
parent | 9da817192c7e0830c073e06f80360745c58efef6 [diff] |
Update pretty name of inventory items in Json Updates inventory JSON of Rainier and Everest to populate pretty name similar to name mentioned in the IBM Knowledge center document. Change-Id: I0518b2d6e5f0a751394c3ff29f3989e9c458c7b0 Signed-off-by: RekhaAparna01 <vrekhaaparna@ibm.com>
This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both OpenPower VPD and IPZ VPD formats are structured binaries that consist of records and keywords. A record is a collection of multiple keywords. More information about the format can be found here.
The repository consists of two distinct applications, which are:
This is a build-time YAML driven application that parses the OpenPower VPD format and uses the YAML configuration (see extra-properties-example.yaml and writefru.yaml) to determine:
The application instance must be passed in the file path to the VPD (this can, for example, be a sysfs path exposed by the EEPROM device driver) and also the D-Bus object path(s) that EEPROM data needs to be published under.
This parser is can be built by passing in the --enable-ibm-parser
configure option. This parser differs from the OpenPower VPD parser in the following ways:
#
and are > 255 bytes in length).Making the application runtime JSON driven allows us to support multiple systems (with different FRU configurations) to be supported in a single code image as well as making the application more flexible for future improvements.