commit | d3e693ebd01bf07a4f15fe2b5969c69178c6aa34 | [log] [tgz] |
---|---|---|
author | RekhaAparna01 <vrekhaaparna@ibm.com> | Tue Mar 04 05:08:30 2025 -0600 |
committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Fri Mar 21 09:07:35 2025 +0000 |
tree | a48779b8949ab9cee834b552cb4c218f86ce42bc | |
parent | 227938343973968ac77541111fa6c0ef384082cd [diff] |
API to update IM value on system planar This commit implements code to update IM value on system planar EEPROM path. Change-Id: Ib4e8570d1ad5c86dd4573aca9882031282342a88 Signed-off-by: Rekha Aparna <vrekhaaparna@ibm.com>
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:
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 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.
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:
#
and are > 255 bytes in length).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.