Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 227938343973968ac77541111fa6c0ef384082cd
commit227938343973968ac77541111fa6c0ef384082cd[log] [tgz]
authorSunny Srivastava <sunnsr25@in.ibm.com>Thu Mar 20 12:09:09 2025 +0530
committerJinu Joy Thomas <jinu.joy.thomas@in.ibm.com>Fri Mar 21 08:47:43 2025 +0000
tree23afff801d4f0c2ad8e11fae9bbdd2aeec3f3667
parentb5bfcbc6e53d3aa9a92776cd9ea1c8acde495a87 [diff]
Update FRU part number for PowerVS systems

Error log makes use of FRU part number instead of part number in the
call outs.
Hence the code is updated to change FRU part number instead of part
number in case of PowerVS systems.
Similarly, spare part number of Decorator.Asset interface is updated
instead of part number.

Change-Id: I31b57e23863b250f7fb036b23c7a192fc1bbec5c
Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
4 files changed
tree: 23afff801d4f0c2ad8e11fae9bbdd2aeec3f3667
  1. configuration/
  2. scripts/
  3. service_files/
  4. test/
  5. vpd-manager/
  6. vpd-tool/
  7. vpdecc/
  8. .clang-format
  9. .gitignore
  10. LICENSE
  11. meson.build
  12. meson_options.txt
  13. OWNERS
  14. README.md
README.md

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:

OpenPower VPD Parser

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 supported records and keywords.
  • How VPD data is translated into D-Bus interfaces and properties.

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.

IBM VPD Parser

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:

  • It parses all the records and keywords from the VPD, including large keywords (Keywords that begin with a # and are > 255 bytes in length).
  • It relies on a runtime JSON configuration (see examples/inventory.json) to determine the D-Bus object path(s) that hold interfaces and properties representing the VPD for a given VPD file path.

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.

TODOs and Future Improvements

  1. The long-term goal is to completely do away with the build time YAML driven configurations and instead reconcile the OpenPower VPD parser and the IBM VPD parser applications into a single runtime JSON driven application.
  2. Add details to the README on how to configure and build the application.
  3. More JSON documentation.
  4. Support for more IBM VPD formats.
  5. VPD Write and tool documentation.