commit | 6555e7efc40c305e5c3c8863c3d1793f474ec7e2 | [log] [tgz] |
---|---|---|
author | jinuthomas <jinu.joy.thomas@in.ibm.com> | Tue Feb 14 21:48:00 2023 -0600 |
committer | jinuthomas <jinu.joy.thomas@in.ibm.com> | Tue Feb 21 08:24:35 2023 -0600 |
tree | 36aca124a0d08331711db6914bc7f9e23c0c303c | |
parent | f27cea757530b910aee31b891f2b10f01b7226b7 [diff] |
Adding ISDIMM support Added ISDIMM support for Bonnell machine Change-Id: Ifdb2fc9e2d38267c8eb6cd5848d30102ab48efd1 Signed-off-by: jinuthomas <jinu.joy.thomas@in.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.