Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / dfdd4b101da8bde2903b1ec94fe23237607d0811
commitdfdd4b101da8bde2903b1ec94fe23237607d0811[log] [tgz]
authorSunny Srivastava <sunnsr25@in.ibm.com>Tue Feb 25 12:41:46 2025 +0530
committerSunny Srivastava <sunnsr25@in.ibm.com>Tue Feb 25 01:45:45 2025 -0600
tree442f317b21782c86a515b95bdf33c34c7f8169e2
parent46f2981aa48ebc139a235d02807c858abfe6f58b [diff]
Update meson for upstream support

Move IBM specific requirements under condition as it is not
required for generic upstream CI.

Change-Id: I23f670ced6d87c71ca3a4786b53b2d05c6b16f8b
Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
1 file changed
tree: 442f317b21782c86a515b95bdf33c34c7f8169e2
  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.