| commit | 630894209984a024cbed7560f3a428d49f26f5ef | [log] [tgz] |
|---|---|---|
| author | Souvik Roy <souvikroyofficial10@gmail.com> | Thu Jan 23 02:48:21 2025 -0600 |
| committer | Souvik Roy <souvikroyofficial10@gmail.com> | Mon Feb 03 08:39:33 2025 +0000 |
| tree | 796d24fdc36037ee1f683046b647db4b7036decd | |
| parent | d7d3b51160edad6aa745232dc91d9dc03bfe5d02 [diff] |
vpd-tool mfgClean: Sync BIOS attributes stub This commit adds --syncBiosAttributes flag to vpd-tool --mfgClean option. The changes in this commit allows user to specify --syncBiosAttributes/-s with --mfgClean option. --syncBiosAttributes flag when used along with --mfgClean will sync those VPD keywords on hardware and D-Bus, with the corresponding values of BIOS attributes. The other keywords not associated with BIOS attribute backup continue to be updated with the default value in backup_restore JSON file. Test: ``` root@p10bmc:~# vpd-tool VPD Command Line Tool Usage: vpd-tool [OPTIONS] Options: -s,--syncBiosAttributes Sync BIOS attribute related keywords from BIOS Config Manager MfgClean: Flag to clean and reset specific keywords on system VPD to its default value. vpd-tool --mfgClean To sync BIOS attribute related keywords with BIOS Config Manager: vpd-tool --mfgClean --syncBiosAttributes ``` Change-Id: Icdff0bc08e629d12e4de2a21c2499ea621a03c38 Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
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.