| commit | c2169c5b5e70bc16a84746f4ccd83bb7c827b33c | [log] [tgz] |
|---|---|---|
| author | Fred Chen <Fred.Chen@quantatw.com> | Fri Aug 22 16:56:04 2025 +0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Sep 08 16:37:16 2025 +0000 |
| tree | 8f422975fb0338829b15fde0003f422076b3ca9c | |
| parent | aab4a6c2af9df2d9f72e6e7c537b95c48c1d3386 [diff] |
com: meta: add CPLD compatible device string for santabarbara ASIC board CPLD on Rainbow board: Lattic LCMXO3D_9400 CPLD on Rainbow EVB board: Lattic LCMXO3D_9400 Change-Id: I6741cd3c96c5d32cadb361abe281f6380350d2bc 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