commit | b74826bdc781747f661a4612db1d3ddebdfc2262 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Wed Nov 29 07:08:51 2023 -0600 |
committer | SunnySrivastava <sunnsr25@in.ibm.com> | Thu Jan 04 06:00:00 2024 +0000 |
tree | 4efaea26036d20d155961870656bf48527d81870 | |
parent | 753ee87a34339688d61ec996fa10346292b4eaf6 [diff] |
meson: disable oe-sdk by default The meson option oe-sdk is used in rare scenarios. Having it non-defaulted turns it into an `auto` feature, which is not desired. Explicitly disable it by default. Change-Id: Ib278aa93822e471c63b9f3c5a2e42eaffa441a6a 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.