| commit | f85ae8afbb5e4be7d83a15ef9b6f24da74d41c4f | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Wed Sep 03 14:14:11 2025 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 10 00:12:49 2025 +0000 |
| tree | 150150d0184ad65bb5e0acc0ab79f1a721012a06 | |
| parent | f7f4a2b95f7321f17802d577048f1b97b68d9162 [diff] |
Failover: Add requester to StartFailover method Add a 'Requester' parameter to the StartFailover method so that the source of the failover can be known. It is an enum to limit the scope of what it can be. Change-Id: I9122ed2b7fd1040e8ddb2c5c840b68c8a18a272f 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