Searched refs:TLV (Results 1 – 4 of 4) sorted by relevance
34 #define TLV2TYPE(TLV) \ argument35 (TLV)->attr_id >= FIRST_TAG_DD ? OBJ_DD : \36 (TLV)->attr_id >= FIRST_TAG_DDS ? OBJ_DDS : \37 (TLV)->attr_id >= FIRST_TAG_PG ? OBJ_PG : \38 (TLV)->attr_id >= FIRST_TAG_ISCSI ? OBJ_ISCSI : \39 (TLV)->attr_id >= FIRST_TAG_PORTAL ? OBJ_PORTAL : \40 (TLV)->attr_id >= FIRST_TAG_ENTITY ? OBJ_ENTITY : 0;
508 Called on PF side to indicate the VF to PF TLV Request type send by VF in 720 for further processing of the TLV request.724 Called from ecore to get the TLV values of a given type. Ecore client
803 …ides the TLV request interface for MFW for querying the driver/device attributes. MFW uses mailbox…805 …TLV request notification from the MFW. The execution context in interrupt mode, hence ecore client…806 …\item OSAL\_MFW\_FILL\_TLV\_DATA - Ecore invokes this callback to get the TLV values of a given ty…1487 \section{IWARP APP TLV configuration}1613 To support this, there is a mechanism of \myindex{TLV}\footnote{Type-Length-Value} message passing …1624 …unaware that inside the ecore this will send a VPORT\_START TLV message from VF to PF, and that th…1710 The Channel achieves compatibility through a TLV interface. Messages will always contain a type, le…
1133 10. Request: Add ecore support to recognize the iwarp app TLV, and configure1283 2. Request: Add ecore support for processing the TLV request from MFW.1398 3. Request: Add ecore interfaces for MFW TLV request processing.2205 1. Problem: CQ88564 - duplicate iSCSI app TLV when setting iSCSI3055 Change: If RoCE-V2 TLV is not detected, use RoCE app data for RoCE-v2.6684 11. Request: Pass FW & MFW versions to VF via acquire response TLV.6688 13. Request: Add support to use VPORT update TLV as list of extended tlvs.