| commit | 0170a765942a3432976e06e975c07f22ed3bb8a7 | [log] [tgz] |
|---|---|---|
| author | Brandon Kim <brandonkim@google.com> | Tue Oct 19 18:51:14 2021 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 22 21:49:39 2021 +0000 |
| tree | 32b523debd69056a6b5854f59479b66d1348e40b | |
| parent | 8d3d5a2a022a135ac3d58e63d693168c83f7d783 [diff] |
Cpu: Update Step and Microcode type to uint 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 Step and Microcode information should be represented in hex. To ensure this, we should pass in uint and let the external interface do the conversion to hex string. Following Intel specs, Stepping seems to be 1 byte, and Microcode 4. https://en.wikipedia.org/wiki/CPUID#EAX=1:_Processor_Info_and_Feature_Bits Signed-off-by: Brandon Kim <brandonkim@google.com> Change-Id: Ifb2baf2c04da7bad08e2b1b01bb6db7acebc4e36
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