Hi,
I recently noted a strange problem in my NDIS 4.0 driver. When my card is
the only network card in the system (PCI bus), the driver works perfectly
fine.
However when I install a different network card, I get a failure for my
NdisMRegisterInterrupt call !
Both these cards are using the same IRQ (11 in my case). First I call
NdisMPciAssignResources and get the values for InterruptVector and
InterruptLevel, and same I pass to NdisMRegisterInterrupt. (I get both these
values as 11 again).
The DDK gives the reason of the failure as : “The attempt to initialize the
interrupt object failed, possibly due to another driver’s prior claim on the
InterruptVector or InterruptLevel in the registry.”
Can anyone please tell me how am I expected to handle the situation when
another driver has already claimed the InterruptVector or InterruptLevel ?
Thanks,
Regards,
Abhijit
Set SharedInterrupt parameter to TRUE - PCI bus requires this.
Max
----- Original Message -----
From: “Abhijit Mirajkar”
To: “NT Developers Interest List”
Sent: Friday, April 04, 2003 2:54 PM
Subject: [ntdev] NdisMRegisterInterrupt failure
> Hi,
>
> I recently noted a strange problem in my NDIS 4.0 driver. When my
card is
> the only network card in the system (PCI bus), the driver works
perfectly
> fine.
> However when I install a different network card, I get a failure for
my
> NdisMRegisterInterrupt call !
>
> Both these cards are using the same IRQ (11 in my case). First I
call
> NdisMPciAssignResources and get the values for InterruptVector and
> InterruptLevel, and same I pass to NdisMRegisterInterrupt. (I get
both these
> values as 11 again).
> The DDK gives the reason of the failure as : “The attempt to
initialize the
> interrupt object failed, possibly due to another driver’s prior
claim on the
> InterruptVector or InterruptLevel in the registry.”
>
> Can anyone please tell me how am I expected to handle the situation
when
> another driver has already claimed the InterruptVector or
InterruptLevel ?
> Thanks,
>
> Regards,
> Abhijit
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to
xxxxx@lists.osr.com
Hi,
Thanks for your input. However I have already set the SharedInterrupt
parameter to TRUE. That’s why I am puzzled.
Any input will be greatly appreciated.
Thanks,
Regards,
Abhijit
Set SharedInterrupt parameter to TRUE - PCI bus requires this.
Max
----- Original Message -----
Hi,
I recently noted a strange problem in my NDIS 4.0 driver. When my
card is
the only network card in the system (PCI bus), the driver works
perfectly
fine.
However when I install a different network card, I get a failure for
my
NdisMRegisterInterrupt call !
Both these cards are using the same IRQ (11 in my case). First I
call
NdisMPciAssignResources and get the values for InterruptVector and
InterruptLevel, and same I pass to NdisMRegisterInterrupt. (I get
both these
values as 11 again).
The DDK gives the reason of the failure as : “The attempt to
initialize the
interrupt object failed, possibly due to another driver’s prior
claim on the
InterruptVector or InterruptLevel in the registry.”
Can anyone please tell me how am I expected to handle the situation
when
another driver has already claimed the InterruptVector or
InterruptLevel ?
Thanks,
Regards,
Abhijit
Does that network card co-exist with any other NIC in
the market???
-Daniel
— Abhijit Mirajkar wrote:
> Hi,
>
> Thanks for your input. However I have already set
> the SharedInterrupt
> parameter to TRUE. That’s why I am puzzled.
>
> Any input will be greatly appreciated.
> Thanks,
>
> Regards,
> Abhijit
>
> > Set SharedInterrupt parameter to TRUE - PCI bus
> requires this.
>
> > Max
>
> ----- Original Message -----
>
>
> > Hi,
> >
> > I recently noted a strange problem in my NDIS 4.0
> driver. When my
> card is
> > the only network card in the system (PCI bus), the
> driver works
> perfectly
> > fine.
> > However when I install a different network card, I
> get a failure for
> my
> > NdisMRegisterInterrupt call !
> >
> > Both these cards are using the same IRQ (11 in my
> case). First I
> call
> > NdisMPciAssignResources and get the values for
> InterruptVector and
> > InterruptLevel, and same I pass to
> NdisMRegisterInterrupt. (I get
> both these
> > values as 11 again).
> > The DDK gives the reason of the failure as : “The
> attempt to
> initialize the
> > interrupt object failed, possibly due to another
> driver’s prior
> claim on the
> > InterruptVector or InterruptLevel in the
> registry.”
> >
> > Can anyone please tell me how am I expected to
> handle the situation
> when
> > another driver has already claimed the
> InterruptVector or
> InterruptLevel ?
> > Thanks,
> >
> > Regards,
> > Abhijit
>
>
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
xxxxx@lists.osr.com
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com