commit | 2dfdbdd54aa70f6978994b871d2a9a6ca2940084 | [log] [tgz] |
---|---|---|
author | Priyanga Ramasamy <priyanga24@in.ibm.com> | Fri Aug 18 10:07:37 2023 +0000 |
committer | Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> | Mon Sep 11 04:04:00 2023 +0000 |
tree | c1dce6f20d1bdf2a50f99f0cdfe67e6d0b123239 | |
parent | f98768142fb53215c5aeb312ed7525dbc9fae654 [diff] |
Skip displaying asset only if VINI is not present This commit has logic in vpd-tool to display properties under Asset interface only if VINI properties are not required to display. This is done to avoid duplicate entries in vpd-tool output as the properties from Asset interface are derived from keyowrds under VINI interface. Test: vpd-tool -o -O /system [ { "/system": { "LocationCode": "U9105.42A.13BEA10", "Model": "9105-42A", "Present": "true", "PrettyName": "System", "SerialNumber": "13BEA10", "SubModel": "S0", "TYPE": "FRU", "type": "xyz.openbmc_project.Inventory.Item.System" } } ] vpd-tool -o -O /system/chassis/motherboard/fan1 [ { "/system/chassis/motherboard/fan1": { "CC": "7B5F", "DR": "Blower", "FN": "02YK323", "LocationCode": "U78DB.ND0.WZS0018-A1", "PN": "02YK323", "Present": "true", "RI": "", "RT": "", "SN": "YL12JP1C1234", "TYPE": "FRU", "type": "xyz.openbmc_project.Inventory.Item.Fan" } } ] Signed-off-by: Priyanga Ramasamy <priyanga24@in.ibm.com> Change-Id: Ia9c76bd03220b7218cb5f7792100e01fc57a6131
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.