commit | ecfaa2153d43a8a8b9f2d5111f94048adffc40a1 | [log] [tgz] |
---|---|---|
author | Sunny Srivastava <sunnsr25@in.ibm.com> | Mon Mar 24 13:02:13 2025 +0530 |
committer | Sunny Srivastava <sunnsr25@in.ibm.com> | Mon Mar 24 13:05:35 2025 +0530 |
tree | 29378800c93246cccc8a3523a4bf630ab375e72e | |
parent | 58057c1867e0cf62d1ecea39d64a3b238f3ac033 [diff] |
API to detect powerVS image PowerVS systems mandate running of image with specific prefix. The commit adds API to check for those prefix and confirm if it is a powerVS image or not. Change-Id: Ie1cb012d57068d77fbfeeb2cbd6e4e54a542d32f Signed-off-by: Sunny Srivastava <sunnsr25@in.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.