Dear,

I have an issue of NDIS driver on CE 5.0.

My driver needs to wait interrupt from MiniportSetInformation.
But, if MiniportISR() is called and it defers packets to let
MiniportHandleInterrupt() do rest of works, while MiniportSetInformation() is
executing,
MiniportHandleInterrupt() is defered until end of MiniportSetInformation().

So, it makes dead-lock that MiniportSetInformation() is waiting interrupt
but MiniportISR() is not called until end of MiniportSetInformation().

Did I miss something?

Thanks in advance,
Woojung

RE: MiniportSetInformation and MiniportHandleInterrupt() are serialize by Woojung_DOT_Huh_AT_smsc_DOT_com>

Woojung_DOT_Huh_AT_smsc_DOT_com>
Wed Oct 26 08:19:05 CDT 2005

Hi,

I resolved the issue using asynchronous NdisMSetInformationComplete().

I suspect MiniportHandleInterrupt() and MiniportSetInformation() are
serialized.
But, can anyone confirm that?

Thanks,
Woojung


"Woojung" wrote:

> Dear,
>
> I have an issue of NDIS driver on CE 5.0.
>
> My driver needs to wait interrupt from MiniportSetInformation.
> But, if MiniportISR() is called and it defers packets to let
> MiniportHandleInterrupt() do rest of works, while MiniportSetInformation() is
> executing,
> MiniportHandleInterrupt() is defered until end of MiniportSetInformation().
>
> So, it makes dead-lock that MiniportSetInformation() is waiting interrupt
> but MiniportISR() is not called until end of MiniportSetInformation().
>
> Did I miss something?
>
> Thanks in advance,
> Woojung