| commit | 97e18987a42844de70848cd201e7edacf2263062 | [log] [tgz] |
|---|---|---|
| author | Fred Chen <Fred.Chen@quantatw.com> | Wed Sep 24 15:36:09 2025 +0800 |
| committer | Fred Chen <Fred.Chen@quantatw.com> | Wed Sep 24 20:15:55 2025 +0800 |
| tree | ad45a83c4dfcbdae5987bd3a80ec2954daef7fc3 | |
| parent | 0ab726efb41343f818cce5c48cbd18a2cbc12f64 [diff] |
com.meta: add compatible device strings for santabarbara VR and TPM Add compatible device strings for santabarbara MB/SWB/PDB2 VR and TPM. Change-Id: Ie60979d08737d04b257492e9a15f9f203d8db32a Signed-off-by: Fred Chen <Fred.Chen@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