Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 43c3afcaff90c75efe002b0ff858a2762a77ec62
commit43c3afcaff90c75efe002b0ff858a2762a77ec62[log] [tgz]
authorSantosh Puranik <santosh.puranik@in.ibm.com>Wed Aug 12 17:52:32 2020 +0530
committerSantosh Puranik <santosh.puranik@in.ibm.com>Wed Aug 12 18:04:49 2020 +0530
treee4a35f907d1fef29341c2aee867dbdd827e5ca09
parentd5d52bb49b7232aca198885168b16f01e7d471e9 [diff]
Remove make build system support

This commit removes autoconf/automake support
Only meson buildsystem will be used going forward.

Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com>
Change-Id: Ib4a0c9766fbeb8068de268c37083117ad0ad34df
4 files changed
tree: e4a35f907d1fef29341c2aee867dbdd827e5ca09
  1. examples/
  2. test/
  3. vpd-manager/
  4. vpdecc/
  5. .clang-format
  6. .gitignore
  7. app.cpp
  8. args.cpp
  9. args.hpp
  10. const.hpp
  11. defines.hpp
  12. extra-properties-example.yaml
  13. extra-properties.mako.hpp
  14. extra-properties.py
  15. ibm_vpd_app.cpp
  16. ibm_vpd_type_check.cpp
  17. ibm_vpd_type_check.hpp
  18. impl.cpp
  19. impl.hpp
  20. keyword_vpd_parser.cpp
  21. keyword_vpd_parser.hpp
  22. keyword_vpd_types.hpp
  23. LICENSE
  24. MAINTAINERS
  25. meson.build
  26. meson_options.txt
  27. parser.cpp
  28. parser.hpp
  29. README.md
  30. store.hpp
  31. types.hpp
  32. utilInterface.hpp
  33. utils.cpp
  34. utils.hpp
  35. vpd_tool.cpp
  36. vpd_tool_impl.cpp
  37. vpd_tool_impl.hpp
  38. write.cpp
  39. write.hpp
  40. writefru.mako.hpp
  41. writefru.py
  42. writefru.yaml
README.md

#Overview 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:

OpenPower VPD Parser

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 supported records and keywords.
  • How VPD data is translated into D-Bus interfaces and properties.

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.

IBM VPD Parser

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:

  • It parses all the records and keywords from the VPD, including large keywords (Keywords that begin with a # and are > 255 bytes in length).
  • It relies on a runtime JSON configuration (see examples/inventory.json) to determine the D-Bus object path(s) that hold interfaces and properties representing the VPD for a given VPD file path.

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.

TODOs and Future Improvements

  1. The long-term goal is to completely do away with the build time YAML driven configurations and instead reconcile the OpenPower VPD parser and the IBM VPD parser applications into a single runtime JSON driven application.
  2. Add details to the README on how to configure and build the application.
  3. More JSON documentation.
  4. Support for more IBM VPD formats.
  5. VPD Write and tool documentation.