commit | c91c8bd0af9fce9f26f33c623276f1dad6f6f79c | [log] [tgz] |
---|---|---|
author | Sunny Srivastava <sunnsr25@in.ibm.com> | Mon Feb 12 05:01:35 2024 -0600 |
committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Mon Feb 12 14:49:16 2024 +0000 |
tree | cb3d85753b61412a03c40660e919f7f6d430f81a | |
parent | fe4a99b3659861c2b55919247a268ed43a8d35c0 [diff] |
Add mux entry for 1S4U systems The commit fixes the missing entries for mux in 1S4U system JSON. Change-Id: Ia3e73d00d3bce3d8855b32a932319d187c7869fc 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.