Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 3aca293156c1a5ef6e32bfd9fd73edce1d5c1aee
commit3aca293156c1a5ef6e32bfd9fd73edce1d5c1aee[log] [tgz]
authorAnupama B R <anupama.b.r1@ibm.com>Wed Mar 05 22:37:15 2025 -0600
committerJinu Joy Thomas <jinu.joy.thomas@in.ibm.com>Fri Mar 07 10:26:27 2025 +0000
tree9cb812e587d8e7845c495108b351ea03366cc5a3
parent7fea9f503fbdc0dce1ecf3bf684ac49ccf80ae89 [diff]
Fix for AMM gets disabled after system reboot

Enable Active Memory Mirroring(AMM) mode in GUI memory tab under
‘Resource Management’. On reboot of the system and once system reaches
ready state, AMM mode in the GUI shows as disabled.

Bios handler in VPD manager caused this issue as it’s comparing AMM VPD
as character value with wrong int value.

This commit implements changes to fix the above issue.

Change-Id: I758ede97e17ecf76fbd4ee05287172ce1534201c
Signed-off-by: Anupama B R <anupama.b.r1@ibm.com>
2 files changed
tree: 9cb812e587d8e7845c495108b351ea03366cc5a3
  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.