| commit | c1171736be9c51bee3307bab70c8fa288794de3d | [log] [tgz] |
|---|---|---|
| author | Souvik Roy <souvikroyofficial10@gmail.com> | Thu Oct 16 09:27:38 2025 +0000 |
| committer | SunnySrivastava <sunnsr25@in.ibm.com> | Mon Nov 03 15:23:21 2025 +0000 |
| tree | 71f27d43face6177c1c7ae607770d6093aade713 | |
| parent | bac8ba648270d66b793b013854936ca34f01d8f5 [diff] |
Check VPD collection mode in non field mode This commit adds changes to read VPD collection mode in case system is in not in field mode. In non field mode, VPD collection mode is determined by reading u-boot variable "vpdmode". Test: ``` - Put debug traces in worker constructor - Install image on rainiest simics - Check u-boot variable "fieldmode" is not defined - Check u-boot variable "vpdmode" is not defined - See worker is initialized with m_vpdCollectionMode = HARDWARE_MODE - Check u-boot variable "fieldmode" is defined as "fieldmode=true" - See worker is initialized with m_vpdCollectionMode = HARDWARE_MODE - Check u-boot variable "fieldmode" is defined as "fieldmode=false" - Check u-boot variable "vpdmode" is not defined - See worker is initialized with m_vpdCollectionMode = HARDWARE_MODE - Check u-boot variable "vpdmode" is defined as "vpdmode=hardware" - See worker is initialized with m_vpdCollectionMode = HARDWARE_MODE - Check u-boot variable "vpdmode" is defined as "vpdmode=file" - See worker is initialized with m_vpdCollectionMode = FILE_MODE - Check u-boot variable "vpdmode" is defined as "vpdmode=mixed" - See worker is initialized with m_vpdCollectionMode = MIXED_MODE ``` Change-Id: I89e514c7c46cc409c0746cddfe66ce0a860220ee 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 at a broken link.
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.