NDIS and priorities

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: "Joseph Garibaldi" <joseph_garibaldi@xxxxxxxxxxxxx>
Date: Sun, 31 Jul 2005 08:34:28 +0530

hi all,

i was under the impression that in CE miniport drivers, MiniportISR()
and MiniportDisableInterrupt() run @ priority 116 and the rest of the
functions in the miniport run at priority 118. But breakpoints at
MiniportSendPackets() and MiniportISR() both indicate the same priority of
116. Can somebody shed some light on this?

further,

1. Should we only use MiniportSynchronizeISR to obtain sync. between
ISR() ( or MiniportDisableInterrupt() ) and other functions? (Guess the docs
say yes) i don't get the pic as to why a simple spin lock can't be used to
do the job.

2. Does the same thing apply for sync. between
MiniportHandleInterrupt() and the other callbacks in CE miniports ?

--
cheers,

Joseph Garibaldi.
B'lore, India.

.

Follow-Ups:
- RE: NDIS and priorities
  - From: "David Kanz [MSFT]"
- Re: NDIS and priorities
  - From: Jeff Kelley [MS]

Prev by Date: Customise build for PXA270
Next by Date: Re: Is it possible to install CE5 not from CDs?
Previous by thread: Customise build for PXA270
Next by thread: Re: NDIS and priorities
Index(es):
- Date
- Thread

Relevant Pages

Re: NDIS marshalling pointers
... It appears to me that NDIS must be marshalling pointers being passed between ... the protocol drivers and the miniport drivers. ... I have not found any documentation saying that miniport drivers need to ...
(microsoft.public.development.device.drivers)
Miniport question
... when do miniport drivers get unloaded by the system ... how does a video miniport ... video miniport never exits. ...
(microsoft.public.development.device.drivers)