commit | ac7adcb5471eed5eaa9474a697dc1db254fa9187 | [log] [tgz] |
---|---|---|
author | Carlos J. Mazieri <carlos.mazieri@hcl.com> | Fri Nov 05 10:47:30 2021 -0300 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Dec 01 10:33:58 2021 -0600 |
tree | f88643136a5cd7b0261d98d08d50c8fb95d67e24 | |
parent | 52f37113f231b6e4235677b3ad375e075e921892 [diff] |
software: define multi-slot/multi-device update Enhance the Software update design to be capable of handling updates to multiple devices of the same type or a single device with multiple update locations. Signed-off-by: Carlos J. Mazieri <carlos.mazieri@hcl.com> Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I58008fddb532f4bba4c77b4a8228b8df2abec164
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 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