commit | b421bfdd7e97f37f6e4842340f3e651249fbd79d | [log] [tgz] |
---|---|---|
author | SunnySrivastava1984 <sunnsr25@in.ibm.com> | Mon Mar 02 08:59:32 2020 -0600 |
committer | SunnySrivastava1984 <sunnsr25@in.ibm.com> | Mon Jun 22 01:45:33 2020 -0500 |
tree | 65941a229f129102918d0089118039f84e1282e9 | |
parent | 6d8314d69f0b1da7c5e6f8df3a4ca229035b210d [diff] |
Process json for Extra and Common Interfaces This commit contains code to process json to check if the record and keyword combination updated using write keyword is a part of extra interfaces and common interfaces of VPD inventory json. Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com> Change-Id: I95333abec6e7a7ad6981621f89e6d6e7edc7ecc9
#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.