commit | f05f354d10f4a3ee30abcc8048b36c9a41fbf77b | [log] [tgz] |
---|---|---|
author | RekhaAparna01 <vrekhaaparna@ibm.com> | Sun Mar 02 22:25:23 2025 -0600 |
committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Mon Mar 24 09:33:01 2025 +0000 |
tree | ca9d827c0f5b62e3c007840ae9dd2ffb5df15254 | |
parent | ecfaa2153d43a8a8b9f2d5111f94048adffc40a1 [diff] |
API to check is field mode enabled This commit implements an API to check if field mode is enabled. Change-Id: Icb2ae1df2588e5cb3fd81e30bf739745de5fbb42 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.