commit | 3b99c1855fedd937cd2ce46ff0a4c1024847dff3 | [log] [tgz] |
---|---|---|
author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Tue Mar 29 23:24:08 2022 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Tue Apr 05 11:53:08 2022 +0000 |
tree | 437842f1cd62e0a377e0a48cc065fdd519c01353 | |
parent | 2f103d919ae272f0c8aa721c6c866bfe0b9e68c9 [diff] |
Dump: InitiateOffload: Add Unavailable error The offload may not be available due to various resources needed for offload is busy or not available in such cases Unavailable error needs to be returned. Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> Change-Id: Ibaec718c12ed53ca83977aeb41e10d4cac2fb30f
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir