| commit | 8d3d5a2a022a135ac3d58e63d693168c83f7d783 | [log] [tgz] |
|---|---|---|
| author | Brandon Kim <brandonkim@google.com> | Wed Oct 06 12:51:31 2021 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 22 21:49:39 2021 +0000 |
| tree | 46479d2e45790a1f71cf1af9764b5d6a929cbd1e | |
| parent | df55704398ec8fc3cc608206f05a2226f134c786 [diff] |
Cpu: Add EffectiveFamily and update Model to EffectiveModel Looking at the Redfish Resource and Schema guide: https://www.dmtf.org/sites/default/files/standards/documents/DSP2046_2021.2.pdf Section 6.86.6 at page 668, we see: ``` "Manufacturer": "Intel(R) Corporation", "Model": "Multi-Core Intel(R) Xeon(R) processor 7xxx Series", "ProcessorId": { "VendorId": "GenuineIntel", "IdentificationRegisters": "0x34AC34DC8901274A", "EffectiveFamily": "0x42", "EffectiveModel": "0x61", "Step": "0x1", "MicrocodeInfo": "0x429943" }, ``` We see that EffectiveFamily and EffectiveModel should be the hex CPU ID values, while "Model" should be the human-readable name. Set type of EffectiveFamily and EffectiveModel to uint. Signed-off-by: Brandon Kim <brandonkim@google.com> Change-Id: I1a0893a9ec04d41c2ba8d8737a6d210d1633f73b
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