| commit | a0a9eaa040b8ae632e771ad9a0c7a4daad3a17b5 | [log] [tgz] |
|---|---|---|
| author | Freddie Jheng <Freddie.Jheng@quantatw.com> | Wed Feb 11 16:47:39 2026 +0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Feb 12 20:33:10 2026 +0000 |
| tree | b1ed51eff36eb60aa19edc099298868c78a9de41 | |
| parent | 237428d7ede5e03b305977cff8d2715ac2a5068f [diff] |
com.meta: add compatible device for santabarbara aeb-switchboard VR Add device compatible strings for aeb-switchboard VR. Change-Id: I3d4f3f637346fe4ebe248fb78ee3b478238c7d56 Signed-off-by: Freddie Jheng <Freddie.Jheng@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