| commit | 45123f9741f039249fb5b7ac74586d120d5c9612 | [log] [tgz] |
|---|---|---|
| author | Jonathan Doman <jonathan.doman@intel.com> | Wed Mar 03 13:07:52 2021 -0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Apr 30 15:47:27 2021 +0000 |
| tree | 111efe0fa4d76ba9ae1e228bc77de6bff7cd3f6a | |
| parent | 5d0b767aeb11d10a91a8dd519cf1ad0b22fc76c5 [diff] |
Add UniqueIdentifier interface Some Assets, like Intel CPUs, distinguish between a serial number and a globally unique identifier (aka Protected Identification Number, which can be masked by the user to mitigate tracking/privacy concerns). This identifier is meant to be totally freeform, where the constraints and formatting may be different for each product. Since relatively few assets are likely to use this, we'll put the new property in its own interface rather than cluttering the generic Asset decorator. Signed-off-by: Jonathan Doman <jonathan.doman@intel.com> Change-Id: I9b754015c5977371dfe3b161d0f47850891cd672
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