commit | 40a42aa5db808bf791135461e924259de0429f69 | [log] [tgz] |
---|---|---|
author | Brandon Kim <brandonkim@google.com> | Thu Sep 09 19:17:04 2021 -0700 |
committer | Patrick Williams <patrick@stwcx.xyz> | Tue Sep 14 11:11:39 2021 +0000 |
tree | d075b8fd01c2c68259e02928d664fc9b97639cf0 | |
parent | 6b50623459b54af222cb9a79c5a0c7912c92da41 [diff] |
Add Model property to Cpu Interface Follow the Redfish Schema for ProcessorId - EffectiveModel: https://redfish.dmtf.org/schemas/v1/Processor.v1_12_0.json Signed-off-by: Brandon Kim <brandonkim@google.com> Change-Id: I4832c0b2155d9478286f63979a1383fe13d74d4c
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