commit | 13d4200b2207574203c042829492776cfde897e8 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Tue Feb 04 06:44:15 2025 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Thu Feb 06 11:45:22 2025 +0000 |
tree | 3749b8bbc6ac15d2d8300e55561a858c089eede0 | |
parent | 12b01393ec98928b95a748de8f05241e95920a42 [diff] |
build: upgrade to C++23 Meson 1.1.1 and GCC-13 both support C++23 and a sufficient portion of the standard has been implemented. Upgrade the build to leverage it. Change-Id: I1637b75eb4f6dc4790026eec3418a99c465b08b3 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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.