Re: NDIS. MiniportHalt() but no MiniportInitialize() ? by Martin
Martin
Tue Apr 18 09:42:47 CDT 2006
Thanks for the reply Bill.
As far as I can tell so far, it has not crashed. I've been putting
entry/exit debug on most of the callbacks and they all seem fine.
A further test shows it all working fine on a CEPC which still implies
some kind of crash / word alignment type issue? (test was to
disable/enable the lan adapter).
What does appear strange is when I disable the WLAN on the PDA, I
receive a protocol unbind adapter call followed almost immediately by a
protocol bind adapter? When I reenable it, all I see is a status
indication.
I've double checked, the code which did have
NdisUnbindProtocolsFromAdapter() in it is now commented out (It wasn't
actually being called but I've added comment just in case someone sees
fit to try it).
Thanks
Martin
Bill Tang wrote:
> See comments inline.
>
> "Martin Evans" wrote:
>
>
>>When using an iPAQ H4150, I use the "iPAQ Wireless" utility to disable
>>and then reenable the WLAN.
>>
>>Our NDIS driver was bound to this. We get called on our halt callback
>>when it is switched off but our initialize is not then called when it is
>>switched back on? The MiniportInitialize() is called fine at boot time.
>
>
> A crash is some time not noticeable. Did it crash? ProtocolBind should be
> called at least.
>
>
>>The driver (a VPN software only NDIS implementation) is working fine
>>normally, but is failing when devices are disabled/enabled. Or for that
>>matter the unit is suspended (but I reckon that is another matter?).
>>
>
>
> MPHalt is also called when it goes into standby. So it can be the same
> problem.
>
> FYI: NdisUnbindProtocolsFromAdapter() will hang the device when waking from
> standby.
>
>
>>The almost the same source code is working fine under XP.
>>
>
>
> This just mean you have a lot more work to do.
>
>
>>Any gotchas you can think of?
>>
>>Thanks
>>
>>Martin
>>
>>