commit | 31970ded12a125ec04ac11f506bad8251d2a9f22 | [log] [tgz] |
---|---|---|
author | Alpana Kumari <alpankum@in.ibm.com> | Mon Feb 17 06:49:57 2020 -0600 |
committer | Priyanga Ramasamy <priyanga24@in.ibm.com> | Fri Jun 19 19:25:04 2020 +0530 |
tree | 47b2bb045e364478c59582d4940b9916057ea6c9 | |
parent | 7ef5442238b89851683002e1aaed544d29930a73 [diff] |
BuildDate encoding support for FRUs This commit and vpd-json commit together enables the encoding for BuildDate and set Present state true for all the FRUs. Test: [[0;1;39mxyz.openbmc_project.Inventory.Decorator.Asset[[0m interface - - .BuildDate property s "2019-08-26 11:00" [[0;1;39mxyz.openbmc_project.Inventory.Item [[0m interface - .Present property b true Change-Id: I6d2f07477b0079c1df370908558b2ab0f17a4212 Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>
#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.