commit | e5faaa9beee4da9a2da7419839e0e2ffe48e67b3 | [log] [tgz] |
---|---|---|
author | Sunny Srivastava <sunnsr25@in.ibm.com> | Wed Oct 16 10:41:26 2024 +0530 |
committer | Sunny Srivastava <sunnsr25@in.ibm.com> | Wed Oct 16 10:48:27 2024 +0530 |
tree | ad0ee300b94ed71d6937e37cc054049d14612284 | |
parent | a12c6c8e27e6dfc2ae4766c7152cd39efe1dad8f [diff] |
Update present property for subtree When BMC is rebooted at chassis off state, all the FRUs are queued for recollection and their present property is set accordingly. Whereas in case there is any sub fFRU under that parent, which was not populated based on udev event then its present property remains what was there before boot, creating a wrong representatin of the system. Change-Id: I22168b6064c1b3674798dee26cac6e11ca413c74 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.