| commit | 406e3d474fcf5d27734a1578e439963d62377adb | [log] [tgz] |
|---|---|---|
| author | Ramesh Iyyar <rameshi1@in.ibm.com> | Thu Jun 24 04:27:46 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jul 06 18:30:55 2021 +0000 |
| tree | 2cabfedff0e0adbbbfd513ff12b6e7819f6ecbb5 | |
| parent | e7f718fc49e86ff9b2b363b2bfa048df1ca054f7 [diff] |
open_power: PEL: Added the GetBMCLogIdFromPELId method In OpenPOWER based system, the application may need to get the BMC event log id by using the PEL id (aka Entry ID (EID) which is a unique id in the PEL) so added the interface for the same. Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com> Change-Id: Ie0efdde3783b5e217779f01bfc654ce7199c381d
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=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir