I can’t figure out why my miniport driver isn’t receiving interrupts, and
I am hoping someone can help shed some light on my problem.
In my Init routine, after a call to NdisMSetAttributesEx, I call
NdisMQueryAdapterResources to get my resources. (Using DbgPrint I can see
that I am in fact using IRQ10 as I expect.) I use the results from this
to call NdisMRegisterInterrupt, and the return value is success. Yet,
when I send a packet to my driver, which should cause the interrupt line
to be asserted, my ISR routine is never called. (I have both the
ISRHandler and HandleInterruptHandler defined.) I’m sure my problem isn’t
a hardware problem because I receive the interrupts just fine using my
Linux driver, and if I hook my hardware up to a scope, I can see the line
being driven. Furthermore, I can see from the Interrupt Mask Register,
(0x21 and 0xA1), that my interrupt is not masked.
So why isn’t my ISR or DPC being called? Is there some other
configuration that I am missing?
//Code snippet shown below
NdisMSetAttributesEx(
MiniportAdapterHandle,
(NDIS_HANDLE) Adapter,
0,
NDIS_ATTRIBUTE_DESERIALIZE,
NDIS_ATTRIBUTE_BUS_MASTER,
NIC_INTERFACE_TYPE); // NdisInterfaceInternal
NdisMQueryAdapterResources(
&Status,
WrapperConfigurationContext,
resList,
&bufSize);
for (index=0; index < resList->Count; index++) {
pResDesc = &resList->PartialDescriptors[index];
switch(pResDesc->Type) {
case CmResourceTypeInterrupt:
Adapter->AiInterrupt = pResDesc->u.Interrupt.Level;
Adapter->AiInterruptV = pResDesc->u.Interrupt.Vector;
Adapter->InterruptMode = pResDesc->Flags;
break;
case CmResourceTypePort:
…
}
}
Status = NdisMRegisterInterrupt(&Adapter->Interrupt,
Adapter->AdapterHandle,
Adapter->AiInterruptV,
Adapter->AiInterrupt,
TRUE,
TRUE,
Adapter->InterruptMode);