| commit | 3d500d70755659e8a107c901201f874bfea4d4ba | [log] [tgz] |
|---|---|---|
| author | Leo Yang <Leo-Yang@quantatw.com> | Thu Jan 08 10:37:39 2026 +0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Jan 08 03:27:50 2026 +0000 |
| tree | fef1a0c13bfd333b98dafc9914432b1fa8f3cddc | |
| parent | 1e4506c787e71a1f772931f5a7e6cfad28e7b57f [diff] |
com.meta: yosemite5: add compatible strings for HSC/VR Add compatible device strings specific to yosemite5 HSC:XDP71X_p52v_hsc VR:RAA228006_discrete_vr Change-Id: I5170d79bc5d451250cb3ba091989ef7e87e0bdd9 Signed-off-by: Leo Yang <Leo-Yang@quantatw.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