commit | 468e8c5b1e3d500357c82f7af55fe0de12edfff0 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 29 06:44:43 2023 -0600 |
committer | SunnySrivastava <sunnsr25@in.ibm.com> | Thu Jan 04 06:00:00 2024 +0000 |
tree | 03ddd51c3aac46d4c8cf52bd48e8a2fdfc39fb7d | |
parent | b74826bdc781747f661a4612db1d3ddebdfc2262 [diff] |
build: use allowed over enabled Meson feature options are typically in a tri-state of enabled, disabled, or auto. The enabled and disabled functions on an option (from `get_option`) no longer return true for auto features. Instead, the expectation is to use `allowed()` which is true for both enabled and auto. Switch all uses of `enabled` to `allowed`. Change-Id: I611ecba901a43acbcca19b93a4dcd9578b570bd8 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.