Hi,

I am porting USB-IrDA Device, which is based on NDIS5.1-WDM, to
NDIS6.0-WDF, i took sample of NDISEDGE under, WinDDK\6000\src\kmdf
\ndisedge\60

My Driver's SendHandler is not called, Can anyone suggest me why send
handler is not called ??Under what circumstances will the SendHandler
will not get called ???

NOTE :
The InitializeHandlerEx is completed with STATUS_SUCCESS.
All the OID's Called and Completed with STATUS_SUCCESS.

Any Other Suggestions are also Welcome,
Thanks in Advance.

Thanks and Regards,
Neo

RE: Possibilities for SendHandler is Not Called in the Miniport IrDA D by AntonBassov

AntonBassov
Fri Jul 13 09:08:01 CDT 2007

> ??Under what circumstances will the SendHandler
> will not get called ???

If no call to NdisSend() or NdisSendPackets() is made by the bound
protocols.....

Anton Bassov


"Neo" wrote:

> Hi,
>
> I am porting USB-IrDA Device, which is based on NDIS5.1-WDM, to
> NDIS6.0-WDF, i took sample of NDISEDGE under, WinDDK\6000\src\kmdf
> \ndisedge\60
>
> My Driver's SendHandler is not called, Can anyone suggest me why send
> handler is not called ??Under what circumstances will the SendHandler
> will not get called ???
>
> NOTE :
> The InitializeHandlerEx is completed with STATUS_SUCCESS.
> All the OID's Called and Completed with STATUS_SUCCESS.
>
> Any Other Suggestions are also Welcome,
> Thanks in Advance.
>
> Thanks and Regards,
> Neo
>
>

Re: Possibilities for SendHandler is Not Called in the Miniport IrDA D by Neo

Neo
Fri Jul 13 10:26:02 CDT 2007

Actually this being IrDA-Miniport Driver based on WDF-NDIS, According
to the IrDA protocol the upper driver will be continuosly sending the
data, so that any other IrDA reciepents if available can recognise
this device. So, the Upper driver will be continuosly sending the
data !!!