| commit | c6f2d7a7f1e68c63d242f1adef729fc57cb49c94 | [log] [tgz] |
|---|---|---|
| author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Wed Jun 23 06:33:32 2021 -0500 |
| committer | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Mon Jul 19 08:20:52 2021 -0500 |
| tree | 4dd5c1d0be9e0de68eed473988b64335c62b5819 | |
| parent | 178cae08d6b79eac7cf3eca963526eeefc53a5af [diff] |
In dump create add type uint64 for values in additional parameters The additional parameters passed to the dump create interfaces are accepting a key-value pair and the value should be a string. In some of the dump use cases an integer error log id needs to be passed, it was being passed as a string. But to make it more readable and to reduce conversion errors, updating the dict definition to accept 32 bit unsigned integer. Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> Change-Id: Iefc3a49c2d569a4b179fc515938349f8f84bb3ae
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