commit | 64b9f5f12083b15e47d1df63a3be3500d8c842c4 | [log] [tgz] |
---|---|---|
author | Alpana Kumari <alpankum@in.ibm.com> | Sat Feb 19 13:25:58 2022 -0600 |
committer | Santosh Puranik <santosh.puranik@in.ibm.com> | Mon Mar 07 04:07:28 2022 +0000 |
tree | 8fca57cb0417866b406594aaa5714b3c2fffdd72 | |
parent | 01e6c6352adcc3a1e2746ef951e4a681c80ca596 [diff] |
Fix code bug Before fetching any of the JSON's key, need to check it's presence. If we try to fetch the keyword and it is not present in the json then code crashes in runtime. Also, added a check before executing driver binding command, as with blank i2c address this execution will do nothing. Signed-off-by: Alpana Kumari <alpankum@in.ibm.com> Change-Id: I9dc991bd795cf3fad31cbd5da92cf8cd56b8aa6b
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.