@@ -32,6 +32,7 @@ the MCTP stack, such as supported message types.
3232NAME TYPE SIGNATURE RESULT/VALUE FLAGS
3333au.com.codeconstruct.MCTP1 interface - - -
3434.RegisterTypeSupport method yau - -
35+ .RegisterVDMTypeSupport method yvq - -
3536```
3637
3738#### ` .RegisterTypeSupport ` : ` yau `
@@ -53,6 +54,28 @@ De-registration is automatic - the specified types (and versions) are registered
5354for as long as the dbus sender remains attached to the message bus, and are
5455unregistered on disconnect.
5556
57+ #### ` .RegisterVDMTypeSupport ` : ` yvq `
58+
59+ This method is used to add support for MCTP Vendor Defined Message (VDM) types.
60+ Once called successfully, subsequent responses for Get Vendor Defined Message
61+ Support control commands will include this new VDM type.
62+
63+ ` RegisterVDMTypeSupport <vid format> <vendor id> <command set type> `
64+
65+ If the VDM type is already registered, then dbus call will fail.
66+
67+ - ` <vid format> ` Vendor ID format:
68+ - ` 0x00 ` - PCI/PCIe Vendor ID (16-bit)
69+ - ` 0x01 ` - IANA Enterprise Number (32-bit)
70+ - ` <vendor id> ` Vendor identifier as a variant type:
71+ - For PCIe format: 16-bit unsigned integer (` q ` )
72+ - For IANA format: 32-bit unsigned integer (` u ` )
73+ - ` <command set type> ` Command set type (16-bit unsigned integer) as defined by the vendor
74+
75+ De-registration is automatic - the specified VDM types are registered for as
76+ long as the dbus sender remains attached to the message bus, and are
77+ removed when the sender disconnects.
78+
5679Also it hosts two trees of MCTP objects:
5780
5881 * Interfaces: Local hardware transport bindings that connect us to a MCTP bus
0 commit comments