commit | 9d4f11290013e8204365d6d2a60706326a882756 | [log] [tgz] |
---|---|---|
author | SunnySrivastava1984 <sunnsr25@in.ibm.com> | Wed Aug 26 02:41:46 2020 -0500 |
committer | SunnySrivastava1984 <sunnsr25@in.ibm.com> | Mon Nov 23 08:55:15 2020 -0600 |
tree | 71b4e4010c3b88e0c30eae3fd045a3ef8467cd90 | |
parent | 9d149345b92074c07e7dfc2432cbbd020ccd79d9 [diff] |
Custom Exception type for openpower-vpd-parser. This commit implements custom exception type for openpower-vpd-parser repo. With this runtime exceptions can be classified into categories and appropriate actions can be taken based on their type. Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com> Change-Id: Ia514141e9166a76ba43c536a2e0f1229bd544bae
#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.