commit | 5700b3c8ba20253806dec16338d7dd689bb565e5 | [log] [tgz] |
---|---|---|
author | jinuthomas <jinu.joy.thomas@in.ibm.com> | Tue Mar 07 22:51:00 2023 -0600 |
committer | jinuthomas <jinu.joy.thomas@in.ibm.com> | Tue Mar 07 23:26:31 2023 -0600 |
tree | 7836d361717e308229a3eeb28091787d79bdbda2 | |
parent | 834c078612909710beef2f65802237e7c659983f [diff] |
ISDIMM - compile fix Add the isdimm cpp file to vpd-manager meson Fix namespace for isdimm Change-Id: I2620dc51f5674b9261aa95720def235b24b97ed2 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.