commit | f8f9c866c199d427cde1c0ccb35d123f817de3e3 | [log] [tgz] |
---|---|---|
author | PriyangaRamasamy <priyanga24@in.ibm.com> | Mon Feb 22 22:53:35 2021 -0600 |
committer | PriyangaRamasamy <priyanga24@in.ibm.com> | Thu Feb 25 14:48:23 2021 -0600 |
tree | 1991189fcd0d33930675c51fe27729db66911ccc | |
parent | 640004f1367267476c6fef6069d9b0ff19f46152 [diff] |
Fix build issues due to updated arm-sdk Due to recent changes made in arm-sdk, the FORTIFY_SOURCE security flag enables optimization level 2. The repo has a default debug level of optimization which conflicts with FORTIFY_SOURCE flag. In this commit the default build type is set to debugoptimized and also made sure to disable the FORTIFY_SOURCE when we need to build without any optimization. Signed-off-by: PriyangaRamasamy <priyanga24@in.ibm.com> Change-Id: Ic1a91e58253fed283f67c44989fbc9126e18b7fe
#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:
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.