Re: No IST in an NDIS Miniport?

Normally you don't have to deal with the interrupts directly
in your NDIS miniport as this is handled by the NDIS
itself. You don't need to call InterruptDone in your
driver.

Please provide some additional details. What platform is it,
what ethernet chip (is the speak about etherent?), etc.
The power-cycle means suspend/resume or true
power off/on?

Did you try to look through the controller registers
when it happens? Is the controller configured properly,
interrupts enabled/cleared etc?


"Airohead" <Airohead@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:48F55D19-CE77-42AA-9D5C-BCFEDF03B540@xxxxxxxxxxxxxxxx
Hello All,

I have just inherited a CE NDIS driver and am trying to debug a problem
where, after several quick power-cycles, the driver comes up in a state
where
it receives no interrupts. As such I am trying to learn about the WinCE
interrupt model.

Everything I've read so far refers to an ISR/IST model where an event is
created at initialization time and linked to a system interrupt such that
all
interrupts result in activation of a waiting thread. I've also read that
InterruptInitialize and IniterruptDone are essential calls in this
process.

I see none of that in this driver. The interrupt handler seems to be a
function that was registered with NDIS via the NdisMRegisterMiniport call.
So my question is, does the ISR/IST model not apply to NDIS miniports,
i.e.,
is it handled invisibly by NDIS? For example, should there be a call to
InterruptDone anywhere in an NDIS miniport?

Also, I have been dumping portions of the interrupt object during startup
(there's a lot to dump!) but so far have been unable to detect any
difference
between normal start-ups where interrupts work fine, and those where the
ISR
is never called. Does anyone have any suggestions on how to debug this
sort
of thing.

Thanks.

(I have not tried putting a scope on the interrupt line to verify that it
is
being generated. This device is not m company's; it's all self-contained
and
might be difficult to get at. For the moment I am assuming that the h/w
is
not the problem.)


.

Relevant Pages

  • Re: No IST in an NDIS Miniport?
    ... can you check the registry and verify ... in your NDIS miniport as this is handled by the NDIS ... I've read the device register that indicates interrupts and have been able ... I have just inherited a CE NDIS driver and am trying to debug a problem ...
    (microsoft.public.windowsce.platbuilder)
  • Re: No IST in an NDIS Miniport?
    ... in your NDIS miniport as this is handled by the NDIS ... I've read the device register that indicates interrupts and have been able ... I have just inherited a CE NDIS driver and am trying to debug a problem ... The interrupt handler seems to be a ...
    (microsoft.public.windowsce.platbuilder)
  • Re: No IST in an NDIS Miniport?
    ... I set ResumeOnReset=1 and the driver still gets ... sure changes to the registry are actually seen by Windows. ... in your NDIS miniport as this is handled by the NDIS ... I've read the device register that indicates interrupts and have been able ...
    (microsoft.public.windowsce.platbuilder)
  • Re: two network adapters on a dual processor - on interrupt routing
    ... RSS is in NDIS 6.0 but it is also in SNP released ... interrupts can be distributed as well. ... I have two network cards on an Inte lXeon, ...
    (microsoft.public.development.device.drivers)
  • Re: No IST in an NDIS Miniport?
    ... can you check the registry and verify ... in your NDIS miniport as this is handled by the NDIS ... I've read the device register that indicates interrupts and have been able ... I have just inherited a CE NDIS driver and am trying to debug a problem ...
    (microsoft.public.windowsce.platbuilder)