commit | 522493d42c069bdfe22a8a9c58bb404d0d216fd0 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Mon Sep 11 10:23:28 2023 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Mon Sep 11 10:24:53 2023 -0500 |
tree | 813fc3529c00d7f76aa83942ae50b498057336c5 | |
parent | 122599913d88ff410bcb4e73ba4cbc1b372b5f44 [diff] |
vpd-manager: remove error.cpp This content appears to have been manually generated from a very old version of phosphor-dbus-interfaces YAML a long time ago and the content is now clashing with the corresponding `error.hpp` file. Remove this file from the repository and rely on the generated version instead (in the PDI library). Change-Id: Icaebb5ac67fd829e4a06bca15eb02d0255caedc5 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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.