NDIS_TAPI_DEV_SPECIFIC (Windows Embedded CE 6.0)

1/6/2010

The NDIS_TAPI_DEV_SPECIFIC structure is used with the OID_TAPI_DEV_SPECIFIC when it requests the miniport driver to provide access to features not accessible through other object identifier requests. The extension meanings are device-specific, so the application must be fully aware of them to take advantage of these extensions.

Support for this request is optional.

Syntax

typedef struct _NDIS_TAPI_DEV_SPECIFIC { 
  ULONG ulRequestID; 
  HDRV_LINE hdLine; 
  ULONG ulAddressID; 
  HDRV_CALL hdCall; 
  ULONG ulParamsSize; 
  UCHAR Params[1]; 
} NDIS_TAPI_DEV_SPECIFIC, *PNDIS_TAPI_DEV_SPECIFIC; 

Members

• ulRequestID
  [in] Reserved.

• hdLine
  [in] Specifies the miniport driver's handle to the line to be operated on.

• ulAddressID
  [in] Specifies the address on the specified line to be operated on.

• hdCall
  [in] Specifies the miniport driver's handle to the call to be operated on. This member can be NULL.

• ulParamsSize
  [in, out] Specifies the number of bytes in the following parameter block. On entry, this member will contain the size in bytes of the parameter block passed in to the miniport driver.

  If the miniport driver returns information in the parameter block, it should set this member to the size in bytes of the returned information, which cannot exceed the input ulParamsSize. Otherwise, the miniport driver should set this member to zero to indicate that it is returning no information.

• Params
  [in, out] Specifies a device-specific parameter block.

Remarks

The MiniportQueryInformation function can return one of the following:

• NDIS_STATUS_SUCCESS
• NDIS_STATUS_PENDING
• NDIS_STATUS_TAPI_INVALLINEHANDLE
• NDIS_STATUS_TAPI_INVALADDRESSID
• NDIS_STATUS_TAPI_OPERATIONUNAVAIL
• NDIS_STATUS_TAPI_RESOURCEUNAVAIL
• NDIS_STATUS_FAILURE

Requirements

See Also

Reference

NDIS Structures
OID_TAPI_DEV_SPECIFIC
MiniportQueryInformation