commit | c023f9bf85550b1f9676cf2d214d497124530f16 | [log] [tgz] |
---|---|---|
author | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Sun Aug 25 22:42:34 2024 -0500 |
committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Sun Aug 25 22:42:34 2024 -0500 |
tree | 779e2399150293384dba25a0cb1e46fbb0633b02 | |
parent | 08dc31cd99172460b86e7552d0eeb21eb4197446 [diff] |
IBM: P12 kernel device tree addition Added Huygens DTB file Added Huygens json file Change-Id: I030964db6398b506877eef84bb94374c90947708 Signed-off-by: Jinu Joy Thomas <jinu.joy.thomas@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.