| commit | 9a96970ebb93eb1f495c200801343a4d1c53977c | [log] [tgz] |
|---|---|---|
| author | Manojkiran Eda <manojkiran.eda@gmail.com> | Wed Feb 24 19:19:50 2021 +0530 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Mar 10 13:35:29 2021 +0000 |
| tree | c969bc591ccb2a881e978b773355c69daf2621b3 | |
| parent | d01d1f84191894ad605a9ba5b546280bcfc64f7d [diff] |
Change the signature of Raw PostCode property - On IBM systems, typically the progress code is of size 72bytes which includes an 8-byte primary reference code along with a section of additional hex words that are used during boot hangs e.t.c to provide additional debug data. - Unlike Intel Postcodes, IBM Hosts would use pldm to send these progress codes down to BMC. - The intent behind this commit is to extend the raw progress codes structure to accommodate (8 bytes)Primary progress code & a secondary code(array[byte]). - On IBM systems, the secondary code would be filled with the complete 72-byte buffer. And on Intel systems, the secondary code would be just an empty array. Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I5f46823a7ce553c934fe8da15fb85a831b11c214
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