commit | 3e9aa3b284d54a047e694b0eb4195b60396830d3 | [log] [tgz] |
---|---|---|
author | Vijay Lobo <vijaylobo@gmail.com> | Wed Aug 11 17:24:53 2021 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Thu Aug 26 15:43:54 2021 +0000 |
tree | a5d6c81eb9fa1407f1cda5f9415e90003604db10 | |
parent | bc6b8a7649129e271404d96abb98ae24c11701aa [diff] |
PEL.Entry - Support ManagementSystemAck property This property is used to keep track of the management system acknowledging the PEL. In IBM systems this property is used by HMC to ack PEL and report back if its processed such that the same PEL is not sent again. Signed-off-by: Vijay Lobo <vijaylobo@gmail.com> Change-Id: Iedb27e843f731df7c871c24945eb8cd8679e63d1
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
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir