| commit | e0466093ab40f57a409c6d1d21043cb7506b3405 | [log] [tgz] |
|---|---|---|
| author | Matt Simmering <matthew.simmering@intel.com> | Fri Oct 27 13:07:18 2023 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Feb 08 17:41:04 2024 +0000 |
| tree | 294d8c1bdddcce8caf7db0972047e53c96a5e41c | |
| parent | 75ca2e95417a82d593670603751b319c21ac91f7 [diff] |
Update RestrictionMode enum and config file terms Update the terminology of the RestrictionMode interface enumeration as well as other language used in configuration file. Also update terminology used in Bond interface configuration file. Change-Id: I8a1e299c5644220c5190948b0621df26179c98c4 Signed-off-by: Matt Simmering <matthew.simmering@intel.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