Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / refs/heads/master
commit115652ecb25e755e53296b869d49e223a79fe952[log] [tgz]
authorSouvik Roy <souvikroyofficial10@gmail.com>Fri Jul 25 04:35:33 2025 -0500
committerSouvik Roy <souvikroyofficial10@gmail.com>Mon Jul 28 06:25:35 2025 +0000
treea90f7fce704f3218ec1a2f209031e3c54499f9e7
parent37c6bef9e3ad2ab80a5fb7ac9f76eedd1cd37ec8 [diff]
CI fix:specify libgpiod version

This commit updates the repo's meson.build file to specify the version
of libgpiod which is being used. This is required to explicitly specify
version of libgpiod as the codebase is using libgpiod v1.6.x APIs which
are not compatible with v2.0 APIs.

Test:
```
- run local CI and see that it passes
- run bitbake and see that openbmc image is successfully generated
```

Change-Id: I1e7610eaacefb7eaab0a8ecbd1007b106babd9b0
Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
1 file changed
tree: a90f7fce704f3218ec1a2f209031e3c54499f9e7
  1. configuration/
  2. docs/
  3. scripts/
  4. service_files/
  5. test/
  6. vpd-manager/
  7. vpd-tool/
  8. vpdecc/
  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.