| commit | 846182e0017cd90d15cf586ed8398e345b20373b | [log] [tgz] |
|---|---|---|
| author | Willy Tu <wltu@google.com> | Fri Jun 04 13:16:42 2021 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jul 06 18:40:40 2021 +0000 |
| tree | bd6344909f14e7a313855435b7e0bbefaefd2639 | |
| parent | 406e3d474fcf5d27734a1578e439963d62377adb [diff] |
location code: add new item interface to support more connections types Provide informaiton on different types of physical connections. Supporting: - Slot - Embedded Only supporting these two options since it can be used to cover most cases. The location type can be used by the IPMI OEM or Redfish to represent the physical location of the hardware. A client wrapper client around IPMI/Redfish can use it along with physical location to determine/build device path of the hardware. Change-Id: I2a8cf408d52f2434bc0c7874f5006215fc7203f5 Signed-off-by: Willy Tu <wltu@google.com>
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