| commit | cd2d64a7fecced8da8fe951542a76c987d28231c | [log] [tgz] |
|---|---|---|
| author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Fri Apr 26 03:23:12 2024 -0500 |
| committer | Dhruvaraj S <dhruvaraj@gmail.com> | Thu May 16 14:16:56 2024 +0000 |
| tree | ee27e49ab6ed69bae73a988ad151bcff5dd3562d | |
| parent | 1e5573e42823d37ebbdf2459a6024bdbeff93ee4 [diff] |
com.ibm: Add ErrorLogId to Hostboot dump Adding the error log id field to the hostboot dump which will help identifying the event caused to create this particular dump Change-Id: I5469ade25214c750ef3fa4bc7fd21a76a43a6cf8 Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.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