commit | 3e9f63c065bf8766ffb5a4109b897873758cbdf5 | [log] [tgz] |
---|---|---|
author | Souvik Roy <souvikroyofficial10@gmail.com> | Wed Apr 23 06:28:17 2025 -0500 |
committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Fri Apr 25 09:53:50 2025 +0000 |
tree | 5f17a16b1070c9f463ebfda17e188feeaabdc32e | |
parent | 612bce854fc0d212bc79e35aba1058450c04fdc3 [diff] |
Enhance getParsedJson API log This commit adds the path to JSON to a error log in getParsedJson API. The path to JSON in the log will help in debugging any failures while parsing a JSON. Change-Id: Iafde4d6ff50e191573ec4349d44d8bf70350c5ad Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.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.