Ndis wait/timer functions

I’m working on a Windows 2000 NDIS 5.0 miniport driver that needs to wait
on an event that will be signaled from its DPC routine. Basically issuing a
command to the board and waiting for a reply with an appropriate timeout.
It seems from the DDK documentation that NdisWaitEvent and NdisMSleep which
both have timeout features can only be called from the MiniportInitialize
routine. From what I can tell this only leaves me with NdisStallExecution
to achieve some sort of controlled polling and I’d rather not use it if
possible. Are there any other stall/suspend functions I can use for waiting
in a miniport driver?

Thanks,

Cathy


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Use Timer functions like NdisMSetTimer…

Daniel

-----Original Message-----
From: xxxxx@emulex.com [mailto:xxxxx@emulex.com]
Sent: Friday, May 11, 2001 8:45 AM
To: NT Developers Interest List
Subject: [ntdev] Ndis wait/timer functions

I’m working on a Windows 2000 NDIS 5.0 miniport driver that needs to wait
on an event that will be signaled from its DPC routine. Basically issuing a
command to the board and waiting for a reply with an appropriate timeout.
It seems from the DDK documentation that NdisWaitEvent and NdisMSleep which
both have timeout features can only be called from the MiniportInitialize
routine. From what I can tell this only leaves me with NdisStallExecution
to achieve some sort of controlled polling and I’d rather not use it if
possible. Are there any other stall/suspend functions I can use for waiting
in a miniport driver?

Thanks,

Cathy


You are currently subscribed to ntdev as: xxxxx@broadlogic.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

> I’m working on a Windows 2000 NDIS 5.0 miniport driver that needs to wait

on an event that will be signaled from its DPC routine. Basically issuing
a

Impossible. The miniport’s Send handler and its DPC are both called on
DISPATCH_LEVEL - and thus cannot wait on event.
Just split the work to 2 parts, and do the second part of the work directly
in your DPC instead of signaling the event and doing the second part after
wait.
The MiniportInitialize limitation is because MiniportInitialize is called on
PASSIVE_LEVEL.

Max


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com