| commit | 4da53b259a90834d198458259c984a54d7a0fbc2 | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Fri Aug 14 09:42:48 2020 -0500 |
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Wed Sep 16 18:53:23 2020 +0000 |
| tree | 4130b88eb8946e975932dfc6badb2a835eb94da7 | |
| parent | f9959724f2550127800add775271ad921e053078 [diff] |
openpower: Add CreatePELWithFFDCFiles method This method will create a PEL and a corresponding OpenBMC event log. It is similar to the CreateWithFFDCFiles method on the xyz.openbmc_project.Logging.Create interface, except it returns the two IDs that represent the created PEL and OpenBMC event log: 1. The OpenBMC event log ID 2. The PEL log ID The event log creator may need one of these fields, for example to save one of the IDs in a guard record related to the event log. Change-Id: Iaab7042ebf8e922fae4aab46299b81f5e4f86caa 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++.
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