Bewerken

Delen via

Handling OID Requests In a Miniport Adapter

  • Artikel

NDIS calls a miniport driver's MiniportOidRequest function to submit an OID request to query or set information in the driver. NDIS calls the MiniportOidRequest function either on its own behalf or on behalf of an overlying driver that called the NdisOidRequest or NdisFOidRequest function.

NDIS passes MiniportOidRequest a pointer to an NDIS_OID_REQUEST structure that contains the request information. The request structure contains an OID_Xxx identifier that indicates the type of request and other members to define the request data.

The Timeout member specifies a time-out, in seconds, for the request. NDIS can reset the driver or cancel the request if the time-out expires before the driver completes the request.

The RequestId member specifies an optional identifier for the request. Miniport drivers can set the RequestId member of a status indication to the value obtained from the RequestId member of an associated OID request. Typically, miniport drivers can ignore this member. If a driver must set this member, the reference page for the particular OID provides the required values. For more information about status indications, see Adapter Status Indications.

A miniport driver that successfully handles an OID set request must set the SupportedRevision member in the NDIS_OID_REQUEST structure upon return from the OID set request. The SupportedRevision member notifies the initiator of the request of the revision that the driver supported. For example, a miniport driver can create an Xxx_REVISION_2 structure, supply values that are appropriate for an Xxx_REVISION_1 structure, and fill the rest of the structure with zeros. The miniport driver would report Xxx_REVISION_1 in the SupportedRevision member. In this case, a protocol driver that can support an Xxx_REVISION_2 will use Xxx_REVISION_1 information that the miniport driver supported. For more information about version information in NDIS structures, see Specifying NDIS Version Information.

A miniport driver can complete an OID request synchronously by returning a success or failure status.

A miniport driver can complete an OID request asynchronously by returning NDIS_STATUS_PENDING. In this case, the miniport driver must call the NdisMOidRequestComplete function to complete the operation.

If MiniportOidRequest returns NDIS_STATUS_PENDING, NDIS will not call MiniportOidRequest with another request for the adapter until the pending request is completed.

NDIS can call a miniport driver's MiniportCancelOidRequest function to cancel an OID request.