| commit | 2eba3cbebf9b4ba455562c3726a47a14896e2ba9 | [log] [tgz] |
|---|---|---|
| author | SunnySrivastava1984 <sunnsr25@in.ibm.com> | Tue Aug 18 08:14:08 2020 -0500 |
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Wed Sep 16 19:03:42 2020 +0000 |
| tree | 8bf4fbbe3f2a03cd9ecd8e3eefbcbb0923f57136 | |
| parent | bd7651a0375940880d063e0030d64cfd35bb59d8 [diff] |
ibm: Error interface for blank system VPD. This commit adds error interface to handle blank system VPD in case of system VPD restore. For system VPD restore, VPD data is first checked at the EEPROM path, if blank then the data from DBus is used to re-store. In case where VPD data is blank at both EEPROM path and Dbus cache the process of system VPD restore fails and hence PEL is logged in that scenario. This interface serves as the key into the message registry, and is the Message property of the OpenBMC event log that the PEL is being created from. Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com> Change-Id: Ieac334a1819a31e3964abde3a326106f2ab2ec62
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.
The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.
Only the xyz/openbmc_project interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=true