commit | 43fedabc032ba7c209b58111b6c35c7d95a9f14e | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Mon Feb 03 14:28:05 2025 -0500 |
committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Tue Feb 11 04:52:19 2025 +0000 |
tree | 9d1e798e2ceb0c49595b862fd54ecd4ed9b68d5e | |
parent | e606f0611e0dba5243fd07cc82db23c31bcb1905 [diff] |
clang-format: update latest spec and reformat Copy the latest format file from the docs repository and apply. Change-Id: Id8301a67d945f8a3d1ceb87ae59087100338119c Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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.