| commit | 4450b764f84d543dd00a2d96cf14e45c680580f4 | [log] [tgz] |
|---|---|---|
| author | Alpana07 <46918005+Alpana07@users.noreply.github.com> | Thu Jan 27 22:11:08 2022 +0530 |
| committer | Andrew Geissler <geissonator@yahoo.com> | Wed Jan 10 15:07:47 2024 -0600 |
| tree | 8c9857a8224bf02b4df715c3a324af10fb84eecb | |
| parent | cc4ce70daa8ffed4848c15c5ddc50c51b31dda4a [diff] |
VPD Error interface UnknownSystemType supported DevTree gets selected based on HW and IM of the system VPD. If we get anything unexpected from these keywords, it couldn't determine which systemType it is and so shouldn't load DevTree. A PEL with this error interface UnknownSystemType will be logged and break the booting process there itself. Change-Id: I0437f4db87b4ab556d7c5433a861689c682fafe4 Signed-off-by: Giridhari Krishna <giridharikrishnan@gmail.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