| commit | 234e1fecde1061b567b7ade52cf38b2136ada244 | [log] [tgz] |
|---|---|---|
| author | Kevin Tung <Kevin.Tung@quantatw.com> | Tue Jun 17 16:06:23 2025 +0800 |
| committer | Kevin Tung <Kevin.Tung@quantatw.com> | Thu Jun 26 13:59:01 2025 +0800 |
| tree | 35de8cece8aa9df23995ba13272402b93995f454 | |
| parent | 160f88c729493ed96b66151b5dd0b02ad192ea6a [diff] |
com.meta: add compatible device strings for yosemite5 Add compatible device strings specific to yosemite5 hardware. These compatible strings will be used to identify supported devices in firmware updates. Change-Id: I1e143486e72c41b6b6e6c4190f9ec122f6e70a4e Signed-off-by: Kevin Tung <Kevin.Tung@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