Name
Date
Size
#Lines
LOC

..--

configuration/H--44,06044,038

scripts/H--1915

service_files/H--4538

test/H--527406

vpd-manager/H--12,4907,969

vpd-tool/H--3,1762,101

vpdecc/H--22490

.clang-formatH A D03-Feb-20253.7 KiB137135

.gitignoreH A D13-Apr-202345 54

LICENSEH A D20-Nov-201611.1 KiB202169

OWNERSH A D11-Jan-20231.8 KiB5348

README.mdH A D12-Mar-20232.2 KiB4835

meson.buildH A D04-Feb-20252.7 KiB8870

meson_options.txtH A D12-Mar-20231.7 KiB1313

README.md

1 # Overview
2 
3 This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both
4 OpenPower VPD and IPZ VPD formats are structured binaries that consist of
5 records and keywords. A record is a collection of multiple keywords. More
6 information about the format can be found
7 [here](https://www-355.ibm.com/systems/power/openpower/posting.xhtml?postingId=1D060729AC96891885257E1B0053BC95).
8 
9 The repository consists of two distinct applications, which are:
10 
11 ## OpenPower VPD Parser
12 
13 This is a build-time YAML driven application that parses the OpenPower VPD
14 format and uses the YAML configuration (see extra-properties-example.yaml and
15 writefru.yaml) to determine:
16 
17 - The supported records and keywords.
18 - How VPD data is translated into D-Bus interfaces and properties.
19 
20 The application instance must be passed in the file path to the VPD (this can,
21 for example, be a sysfs path exposed by the EEPROM device driver) and also the
22 D-Bus object path(s) that EEPROM data needs to be published under.
23 
24 ## IBM VPD Parser
25 
26 This parser is can be built by passing in the `--enable-ibm-parser` configure
27 option. This parser differs from the OpenPower VPD parser in the following ways:
28 
29 - It parses all the records and keywords from the VPD, including large keywords
30   (Keywords that begin with a `#` and are > 255 bytes in length).
31 - It relies on a runtime JSON configuration (see examples/inventory.json) to
32   determine the D-Bus object path(s) that hold interfaces and properties
33   representing the VPD for a given VPD file path.
34 
35 Making the application runtime JSON driven allows us to support multiple systems
36 (with different FRU configurations) to be supported in a single code image as
37 well as making the application more flexible for future improvements.
38 
39 ## TODOs and Future Improvements
40 
41 1.  The long-term goal is to completely do away with the build time YAML driven
42     configurations and instead reconcile the OpenPower VPD parser and the IBM
43     VPD parser applications into a single runtime JSON driven application.
44 2.  Add details to the README on how to configure and build the application.
45 3.  More JSON documentation.
46 4.  Support for more IBM VPD formats.
47 5.  VPD Write and tool documentation.
48