commit | 5c773bdfb9c579ec82bdd08a837abe122ffbb824 | [log] [tgz] |
---|---|---|
author | Deepak Kodihalli <deepak.kodihalli.83@gmail.com> | Thu Nov 26 10:30:44 2020 +0530 |
committer | Deepak Kodihalli <deepak.kodihalli.83@gmail.com> | Mon Dec 07 17:27:57 2020 +0000 |
tree | 4eb53848ab345393d29a86ddc540b7e5bb688558 | |
parent | a20be8ec061ad4053c523adfc44d83f91b38b29c [diff] |
MAINTAINERS: Remove Deepak from the list Signed-off-by: Deepak Kodihalli <deepak.kodihalli.83@gmail.com> Change-Id: I0b169ccfc58aa54ffb4031af032ea1a3683cc5cd
#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.