| commit | f8eaa4136eecfcbb1c427f1bb2b575437be32d08 | [log] [tgz] |
|---|---|---|
| author | Nidhin MS <nidhin.ms@intel.com> | Wed Jan 14 12:08:54 2026 +0530 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Feb 06 11:24:23 2026 +0000 |
| tree | e16024b791e2469d5618455c52af7301ea956541 | |
| parent | 0421f365458940a530d33166c30e16761fb8af5a [diff] |
mctp:Endpoint: Add VDM types Add a new VendorDefinedMessageTypes property to the MCTP Endpoint interface to expose vendor-defined message type capabilities The property is defined as array[struct[byte,variant,uint16]] where each entry contains: - Vendor ID Format (byte): 0x00 for PCI Vendor ID, 0x01 for IANA Enterprise Number - Vendor ID (variant): uint16 for PCI format or uint32 for IANA format - Command Set (uint16): Vendor-defined command set identifier Change-Id: I9d51ac3fe2d43484cb41b2a34df33e3dc34ea48b Signed-off-by: Nidhin MS <nidhin.ms@intel.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
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 and org/freedesktop 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