commit | b48e6ffaf1f1973e18a3392af65975a667abf585 | [log] [tgz] |
---|---|---|
author | Alpana Kumari <alpankum@in.ibm.com> | Sun Apr 24 23:42:28 2022 -0500 |
committer | Santosh Puranik <santosh.puranik@in.ibm.com> | Wed Dec 21 09:11:44 2022 +0530 |
tree | 0b3fa254ee456d4e661b87ca23356e67e27bc192 | |
parent | c04e1858f8305fc263e939098913725a77cac3c4 [diff] |
Move Jsons, services and rules to VPD repo This commit moves Jsons, service files and rules to the VPD repo, and installing it by meson. Test: Tested the image on simics and a rainier system , booted to standby succesfully. Also, I verified all the jsons, rules and service files are in the appropriate location. Signed-off-by: Alpana Kumari <alpankum@in.ibm.com> Change-Id: I538b7159e5226134c3e0d16bbb1686166cd17441
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.