commit | d159bb4975c92f11e1100a534adaa70f31a3566b | [log] [tgz] |
---|---|---|
author | Sunny Srivastava <sunnsr25@in.ibm.com> | Thu Jan 09 11:13:50 2025 +0530 |
committer | Sunny Srivastava <sunnsr25@in.ibm.com> | Wed Jan 22 18:20:04 2025 +0530 |
tree | 9d109770959e11436092c45544cc8ff76c5aa1d2 | |
parent | 549d0905e7854e635c422a8bd7a60f8ac5693f4b [diff] |
API to set present property The commit add an API into worker class to set present property over DBus for a given FRU. It also implements change to set present property as false in case any failure is detected in the process of collecting VPD for the FRU. Change-Id: I3faa988a0fb0886a6a28673439a46d6c22c16a32 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.