| commit | 10ad7d8df4dc29778e4ff144c819e1c0210671a3 | [log] [tgz] |
|---|---|---|
| author | Sunny Srivastava <sunnsr25@in.ibm.com> | Tue Apr 01 08:58:40 2025 +0530 |
| committer | SunnySrivastava <sunnsr25@in.ibm.com> | Tue Apr 01 16:45:44 2025 +0000 |
| tree | f8820abbd490a667abf3a70a942b7e6a8df36650 | |
| parent | 677ccb6a7e0a7c0f7e40132378566f08be977479 [diff] |
IBM: Update VPD.errors.yaml Addition of Firmware error to populate com.ibm.VPD.Error.FirmwareError, the same will be used to log PEL in case any standard runtime exception is thrown by VPD Manager firmware code. Change-Id: I68d45b55ee25969b32127d1516765774e47ef8e3 Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
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 and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir