| commit | 549d0905e7854e635c422a8bd7a60f8ac5693f4b | [log] [tgz] |
|---|---|---|
| author | Souvik Roy <souvik.roy10@ibm.com> | Wed Jan 22 02:37:37 2025 -0600 |
| committer | Sunny Srivastava <sunnsr25@in.ibm.com> | Wed Jan 22 18:10:26 2025 +0530 |
| tree | a7432229f480d9bdf0bd36ef1155bc58638de6e7 | |
| parent | a8bb16637a7dcd594296291b72c118e6786dd8b7 [diff] |
vpd-tool dump inventory: trim out base inventory path prefix
This commit trims out the base inventory path
prefix("/xyz/openbmc_project/inventory") from the vpd-tool
--dumpInventory and --dumpObject JSON output. Other scripts assume the
object paths in the JSON to be without the prefix.
Change-Id: I566d40cda59a3c8835590fb7a8ce8501a1a98aa0
Signed-off-by: Souvik Roy <souvik.roy10@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 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.