code-update: Add interface for MultipartUpdate

This commit adds interface to identify the multi part update
to delegate the code update with the multi part image when no
firmware targets are specified.

The design doc update on how to handle multi part image when
no firmware targets are specified.
https://gerrit.openbmc.org/c/openbmc/docs/+/76645

Change-Id: I34581dedf2cf9c21619c64a7f07e531578cf317c
Signed-off-by: Tom Joseph <rushtotom@gmail.com>
3 files changed
tree: 718a4cc6e0b3f7fe669f99273388061c504d2ac1
  1. gen/
  2. registry/
  3. subprojects/
  4. yaml/
  5. .gitignore
  6. .markdownlint.yaml
  7. .prettierrc.yaml
  8. .shellcheck
  9. LICENSE
  10. meson.build
  11. meson.options
  12. OWNERS
  13. README.md
  14. requirements.md
README.md

phosphor-dbus-interfaces

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.

Building

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.

Configuration

Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References