| commit | 2ea4d28e130f0019a3a060f249783ecc4d2022d0 | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Thu Apr 27 16:15:13 2023 -0500 |
| committer | Matt Spinler <spinler@us.ibm.com> | Tue May 02 14:51:35 2023 +0000 |
| tree | cb34c49344ea298ba7b2bdacc7b89a303273034a | |
| parent | df32eb57476e86044a996c5f2b6765a772c10de4 [diff] |
ibm: Add new properties to Logging.PEL.Entry interface Expose four more PEL (IBM's event log format) fields on D-Bus so they are available for other applications. Change-Id: I9cf752fadf6dfff892652dc02a55b93794b81ede Signed-off-by: Matt Spinler <spinler@us.ibm.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