OID_WW_TAC_GET_RESPONSE

The OID_WW_TAC_GET_RESPONSE OID requests the miniport driver to return a response to a previously issued command. A protocol issued this command using the OID_WW_TAC_SEND_COMMAND request. The miniport driver transferred this command to the NIC. Upon completion of this command, the miniport driver retrieves the response.

This OID uses the WW_TAC_GET_RESPONSE structure, defined as follows:

    typedef struct _WW_TAC_GET_RESPONSE {
         UINT SDUTag;
         NDIS_VAR_DATA_DESC Response;
 
    } WW_TAC_GET_RESPONSE;
  

The members of this structure contain the following information:

  • SDUTag
    The unique token that was previously returned to the protocol using OID_WW_TAC_UNIQUE_SDU_TAG.

  • Response
    Describes a buffer that contains the response information for a previously issued command. For more information, see OID_WW_TAC_SEND_COMMAND. This buffer is at most 2048 bytes in size.

If any bound protocol has enabled indications with OID_WW_GEN_INDICATION_REQUEST, the miniport driver must call NdisMIndicateStatusto notify such protocol(s) about the completion status and contents of the specific NCL command. If a protocol enabled an indication request, the protocol must assign an initialized WW_TAC_GET_RESPONSE structure to the InitialValue member of the NDIS_WW_INDICATION_REQUEST structure. The miniport driver interrogates the contents of this initialized WW_TAC_GET_RESPONSE and uses the value in the SDUTagmember to demultiplex and indicate the response. The miniport driver can ignore the TriggerValue member that was specified in the OID_WW_GEN_INDICATION_REQUEST.

Miniport drivers return NDIS_STATUS_INVALID_DATA if a request is issued with an invalid value in the SDUTagmember.

Sets are irrelevant for this OID.

Note   This OID is not available for use beginning with Windows Vista.

 

 

 

Send comments about this topic to Microsoft