| commit | e791d2b581f582f6b7197355f2a6c8f07994bd28 | [log] [tgz] |
|---|---|---|
| author | Amithash Prasad <amithash@meta.com> | Mon Jun 16 11:08:01 2025 -0700 |
| committer | Amithash Prasad <amithash@meta.com> | Mon Jun 16 11:09:24 2025 -0700 |
| tree | c2cfc4ae6e364e3748701a624d09af03f0bdf9ba | |
| parent | 903f7dfdb429049d0151bcc7987410d887b4f10c [diff] |
com.meta: add Bletchley15 BMC As title, add Bletchkey15 which is a generational upgrade of Bletchley (also called Bletchley 1.0). Change-Id: I1844e331bca20dcbab9c61270dafd1aaf714be72 Signed-off-by: Amithash Prasad <amithash@meta.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