| commit | 71eaf8b1db7d903c5a62da3bae178116e69892e1 | [log] [tgz] |
|---|---|---|
| author | Manojkiran Eda <manojkiran.eda@gmail.com> | Thu Feb 25 06:57:14 2021 +0530 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Mar 10 13:35:39 2021 +0000 |
| tree | 0722347e395a4dbfacd262098d89325f8b4cf00f | |
| parent | 9a96970ebb93eb1f495c200801343a4d1c53977c [diff] |
Change Post codes signature to contain Secondary Code - The intent behind this commit is to change the Post Code signature used in all the Dbus methods on the post code interface to contain the secondary post code. - This was needed because, on IBM systems the progress codes are typically 72 bytes which consists of an 8 byte primary reference code along with a bunch of hex words(secondary code). Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: Ic58b2853a9e2ec5327f0b1afe5712e75a41318a9
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