commit | ad7e25e99a267677f087fe145b588eb10d68d67c | [log] [tgz] |
---|---|---|
author | Sunny Srivastava <sunnsr25@in.ibm.com> | Thu Sep 04 09:43:21 2025 -0500 |
committer | SunnySrivastava <sunnsr25@in.ibm.com> | Thu Sep 04 15:13:53 2025 +0000 |
tree | 50a9935dc45ec219e992b4d5357841b9c3c96a93 | |
parent | bb52af4416a4c99dc7deed7e50aa3234c16570b6 [diff] |
Defining error codes as enum The error codes has been moved under enum because of following benefit. As the number against error codes were not specifying anything. Overhead of maintaining unique number for each error code goes away. Change-Id: Id2133c85306c7b65bb3a0ac1d622dda813f2256b Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.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 at a broken link.
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.