commit | d5d52bb49b7232aca198885168b16f01e7d471e9 | [log] [tgz] |
---|---|---|
author | Santosh Puranik <santosh.puranik@in.ibm.com> | Tue Jul 28 15:08:10 2020 +0530 |
committer | Santosh Puranik <santosh.puranik@in.ibm.com> | Tue Jul 28 15:08:10 2020 +0530 |
tree | c55cf67800a4f69fe1383a280860b62f1bb75546 | |
parent | 16c634f7c7a3b7a20f9652582ada1959c7517fa6 [diff] |
vpd-tool: Do not enumerate Power supplies There are outstanding issues with enumerating power supply objects in the vpd tool. Skip those for now. Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com> Change-Id: I450fe93627ec061e7e408b9f6e432a589ba9c4cf
#Overview 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.