commit | add68dc0e720a83e0e2c1d08599b13f916bdf822 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <geissonator@yahoo.com> | Fri Oct 08 16:07:52 2021 -0500 |
committer | Santosh Puranik <santosh.puranik@in.ibm.com> | Mon Oct 18 11:07:11 2021 +0000 |
tree | 7fcf1dc84f7e2ae3d796f67eaaf2a0e7d4dcd004 | |
parent | 8e532c10162529ac8a37a8e1aaacad88d6654b2f [diff] |
reduce journal output from vpd app The bigger systems have a lot of vpd which causes these logs to fill the journal Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ibca4224f7ed8a7b1d28f6585a6c83cf1fc2bb1bd
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.