commit | 50731e434cf1ca691d336aa2202311ba76f2a03b | [log] [tgz] |
---|---|---|
author | Souvik Roy <souvikroyofficial10@gmail.com> | Fri Apr 25 01:36:04 2025 -0500 |
committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Wed Apr 30 04:25:21 2025 +0000 |
tree | 1f98e31b47caa4a74576f4186ac1de67b3341023 | |
parent | 9f255f5c5caac205a3ae47a7e11c31e32971b2e8 [diff] |
vpd-tool:Log invalid BIOS attribute value type This commit adds log message in vpd-tool if any invalid BIOS attribute value type is received from BIOS Config Manager. Change-Id: I87499ef30d8e8f2a92b46ae1d366933bed4abd98 Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.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.