| commit | 4206b1ac6fde78bcbaca6fc766af8a4dc34c6b0d | [log] [tgz] |
|---|---|---|
| author | Jagpal Singh Gill <paligill@gmail.com> | Sat Aug 05 11:23:59 2023 -0700 |
| committer | Jagpal Singh Gill <paligill@gmail.com> | Mon Mar 11 11:58:20 2024 -0700 |
| tree | 6546730d25a1c9a20063c815b88594b96e9b4ff7 | |
| parent | 25507c8e7eb64893063d9b55caced4a9a100334c [diff] |
code-update: simplified interface for code update Current code update invocation flow has no explicit interface but rather rely on discovery of a new file in tmpfs. This makes it more involved and hard to use. The intent of this proposal is to define an explicit interface which is easy to use. For more details, please refer to design doc - https://gerrit.openbmc.org/c/openbmc/docs/+/65739 Change-Id: I65f186856c446cf7d957591c213054dc2d5c3861 Signed-off-by: Jagpal Singh Gill <paligill@gmail.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