Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / e2f09be83c032805c1aa924b5d2187ee994f4ebb
commite2f09be83c032805c1aa924b5d2187ee994f4ebb[log] [tgz]
authorAnupama B R <anupama.b.r1@ibm.com>Tue Apr 08 04:41:28 2025 -0500
committerJinu Joy Thomas <jinu.joy.thomas@in.ibm.com>Wed Apr 09 08:44:01 2025 +0000
treedb690668e4e0c976f0306d3719cb8ebe4fd58876
parent0f370434621997eea8ac37d69834e9ada810068d [diff]
Fix: Read IM value from planar for single FAB

Reading IM value from system planar by its hardcoded offset value is
failing, as IM offset found different for different systems.

This commit adds the code to address the issue, instead of reading IM
value directly from offset, existing Parser class implementation is
used for reading IM value.
where Parser class iterates through the given record and extracts the
keyword value from the EEPROM file.

This commit also updates isFieldModeEnabled API to return ‘true’ only
when ‘fieldmode’ is set ‘true’ on the system explicitly, in all other
case it should be considered as ‘false’.

Change-Id: I0bf9cfee4dab046da0b485504bde63bc4561f710
Signed-off-by: Anupama B R <anupama.b.r1@ibm.com>
1 file changed
tree: db690668e4e0c976f0306d3719cb8ebe4fd58876
  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
  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.