commit | 19be6d3d483fddeea3e24f524cbbfc39dbca20b5 | [log] [tgz] |
---|---|---|
author | SunnySrivastava1984 <sunnsr25@in.ibm.com> | Tue Mar 03 07:21:45 2020 -0600 |
committer | SunnySrivastava1984 <sunnsr25@in.ibm.com> | Mon Jun 22 01:45:33 2020 -0500 |
tree | 35eb7bc1ea51ddb96fa7a5fe520e705c1ef8f95b | |
parent | de3c60de2dd55f8f5038b804723983dbb46bade6 [diff] |
Common file to hold all constant values This commit introduces a const.hpp file to hold all the constants related to the openpower vpd repository. All new and ongoing implementations can make use of this file to declare or reuse constants. Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com> Change-Id: Ib93c1c264dc8c69198140d63318e7e132d33fb13
#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.