| commit | 9ca8d347eddb12250a17ddbdff9e52de92f8d7e9 | [log] [tgz] |
|---|---|---|
| author | Daniel Hsu <Daniel-Hsu@quantatw.com> | Mon May 26 19:59:17 2025 +0800 |
| committer | Daniel Hsu <Daniel-Hsu@quantatw.com> | Tue May 27 08:41:44 2025 +0800 |
| tree | 217d969bd1fceb2124d5c252237b1bc8eab9364f | |
| parent | 1cc8bb4b4253ed5c3547bb9130c51a1a81736841 [diff] |
meta: add device compatible strings for Harma Add the 'Harma' hierarchy under Meta (Facebook) and define compatible strings for the currently supported devices. These will be used to indicate hardware compatibility in device update images. Change-Id: I9079b161499089e3caa8a6f3eece401bf1d27f9c Signed-off-by: Daniel Hsu <Daniel-Hsu@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