| commit | 2794e9510f3d7872fc7485da793b50d02e0580a7 | [log] [tgz] |
|---|---|---|
| author | Potin Lai <potin.lai@quantatw.com> | Tue Nov 14 14:56:39 2023 +0800 |
| committer | Potin Lai <potin.lai@quantatw.com> | Wed Nov 15 08:40:02 2023 +0800 |
| tree | 923a7ed9384ac8f7d00dff308b4b89c3ea04c662 | |
| parent | 47ba142a6f9f6dcf416579cb85360d4defba2745 [diff] |
meta: add compatible string for Harma Adding compatible string for Harma BMC type. Change-Id: Ia2f7a6fb45ef33594c1b4fac2ae4b9706bde0a12 Signed-off-by: Potin Lai <potin.lai@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