| commit | 4b6755c9894cf5d4e983c6e3b86fc752695a1d8e | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Tue Dec 05 14:42:04 2023 -0600 |
| committer | Matt Spinler <spinler@us.ibm.com> | Wed Dec 06 10:48:53 2023 -0600 |
| tree | 3e1d3694acef4a867dc25fbf6149128b3ff9a10b | |
| parent | 6cfd0d08a7083263102cb8e7a216f818a4c210eb [diff] |
ibm: Add compatible strings for chassis Add enums for the compatible strings used by entity-manager for the various chassis types. Change-Id: Ibea95513a38359b7c378add391afbb77235a4900 Signed-off-by: Matt Spinler <spinler@us.ibm.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