commit | 8554f105a7c007f82989f0c86ecdf0f227d49194 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Tue Jun 02 14:37:40 2020 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jun 02 14:37:55 2020 -0500 |
tree | 1a89b042441ccf07db71df41c0aac37420f39747 | |
parent | 095ffd09699fcf59d048975eb26e939d5e7dfb1c [diff] |
MAINTAINERS: update Jinu's email address Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ic8f520d363c4a8e2ac79cf1fc8b308e9c7d704f6
#Overview 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.