Name Date Size #Lines LOC

..Today-

config/ibm/H04-Jan-2024--489-492

examples/H18-Jun-2024-1,4541,452

rules/H06-Feb-2024-43

scripts/H04-Jan-2024-1917

service_files/H04-Jan-2024-9476

subprojects/H04-Jan-2024-4836

test/H04-Jan-2024-1,2931,066

vpd-manager/H04-Nov-2024-3,8012,598

vpd-parser/H26-Aug-2024-1,7561,151

vpdecc/H18-Jun-2024-22490

.clang-formatH A D26-Aug-20243.7 KiB137135

.gitignoreH A D21-Apr-202345 54

LICENSEH A D07-Mar-202111.1 KiB202169

OWNERSH A D19-Jan-20231.8 KiB5348

README.mdH A D02-Feb-20242.1 KiB4835

app.cppH A D29-Mar-20232.5 KiB9173

args.cppH A D07-Mar-20212.7 KiB10087

args.hppH A D07-Mar-2021604 3416

common_utility.cppH A D26-Aug-20241.9 KiB7765

common_utility.hppH A D16-May-2023712 3217

const.hppH A D26-Aug-20248.1 KiB236214

defines.hppH A D07-Mar-20212.9 KiB162120

extra-properties-example.yamlH A D12-Dec-2022218 86

extra-properties.mako.hppH A D07-Mar-2021756 4134

extra-properties.pyH A D12-Dec-2022937 3725

ibm_vpd_app.cppH A D16-Oct-202471.1 KiB1,9821,425

ibm_vpd_utils.cppH A D20-Sep-202438.8 KiB1,2571,067

ibm_vpd_utils.hppH A D20-Sep-202419.3 KiB581217

impl.cppH A D26-Aug-202419.7 KiB664506

impl.hppH A D26-Aug-20246.3 KiB21286

meson.buildH A D13-Feb-202410.2 KiB259222

meson.optionsH A D18-Jun-20242.5 KiB2221

store.hppH A D16-May-20232.8 KiB11568

types.hppH A D04-Jan-20243 KiB8869

utilInterface.hppH A D16-May-2023809 4133

vpd_exceptions.hppH A D18-Jun-20244 KiB15677

vpd_tool.cppH A D20-Sep-20248.8 KiB265227

vpd_tool_impl.cppH A D26-Aug-202442.2 KiB1,3521,163

vpd_tool_impl.hppH A D26-Aug-202410 KiB32371

write.cppH A D07-Mar-20211.5 KiB6753

write.hppH A D16-May-2023470 2614

writefru.mako.hppH A D19-Apr-20212.8 KiB10984

writefru.pyH A D06-Dec-2022891 3725

writefru.yamlH A D07-Mar-2021662 2320

README.md

1# Overview
2
3This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both
4OpenPower VPD and IPZ VPD formats are structured binaries that consist of
5records and keywords. A record is a collection of multiple keywords. More
6information about the format can be found
7[here](https://www-355.ibm.com/systems/power/openpower/posting.xhtml?postingId=1D060729AC96891885257E1B0053BC95).
8
9The repository consists of two distinct applications, which are:
10
11## OpenPower VPD Parser
12
13This is a build-time YAML driven application that parses the OpenPower VPD
14format and uses the YAML configuration (see extra-properties-example.yaml and
15writefru.yaml) to determine:
16
17- The supported records and keywords.
18- How VPD data is translated into D-Bus interfaces and properties.
19
20The application instance must be passed in the file path to the VPD (this can,
21for example, be a sysfs path exposed by the EEPROM device driver) and also the
22D-Bus object path(s) that EEPROM data needs to be published under.
23
24## IBM VPD Parser
25
26This parser is can be built by passing in the `--enable-ibm-parser` configure
27option. 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) tocf
32  determine the D-Bus object path(s) that hold interfaces and properties
33  representing the VPD for a given VPD file path.
34
35Making 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
37well as making the application more flexible for future improvements.
38
39## TODOs and Future Improvements
40
411. 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 VPD
43   parser applications into a single runtime JSON driven application.
442. Add details to the README on how to configure and build the application.
453. More JSON documentation.
464. Support for more IBM VPD formats.
475. VPD Write and tool documentation.
48