Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / refs/heads/master
commit5ab347642f7f97614345abba81c7d347fe511289[log] [tgz]
authorRekha Aparna <vrekhaaparna@ibm.com>Thu Feb 12 10:16:20 2026 -0600
committerRekha Aparna <vrekhaaparna@ibm.com>Fri Feb 20 07:21:09 2026 -0600
treeef9697fdedee40f2e128a88adcccca959d402d71
parent76549c8081a066ecbb334cb8ede9ad5852c7ce72 [diff]
Method to delete all FRU VPD

Persisted VPD may become stale due to hardware reconfiguration or when
FRUs are no longer accessible. In such cases, clearing these entries
ensures the inventory can be repopulated with valid data.

This commit implements a D-Bus method to delete all FRU VPD from PIM
persisted path under VPD Manager interface.

Change-Id: I41b2653b6f6c8861567f68489e9400f5019369c0
Signed-off-by: Rekha Aparna <vrekhaaparna@ibm.com>
2 files changed
tree: ef9697fdedee40f2e128a88adcccca959d402d71
  1. configuration/
  2. docs/
  3. service_files/
  4. test/
  5. vpd-manager/
  6. vpd-tool/
  7. vpdecc/
  8. wait-vpd-parser/
  9. .clang-format
  10. .gitignore
  11. LICENSE
  12. meson.build
  13. meson.options
  14. OWNERS
  15. 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 at a broken link.

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.