interrupt not recognized
- From: kobi n <kobin@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 23 Jan 2008 09:44:01 -0800
Hi,
i have a problem regarding a device that sends an interrupt which is not
catched on my ISR routine.
my driver (WDF based) manages 8 different devices (on board DSPs). each
device can issue an interrupt and thus creates its own interrupt object. now,
some of the devices that send an interrupt are handled correctly but others
don't. since every device is mapped in my driver side (mapped by its PCI info
values like bus number and device number) i can see that only the four devies
on the higher pci bus are causing a problem. the problem is that when an
interrupt is issued by one of the problematic devices, i break in my ISR
routine and i can see that the devices i retrieve from the interrupt object
are all but the device that issued the interrupt - again - i can tell this by
the pci values that i save for each device(that of caurse causes a problem
since i actually do not release any interrupt).
im beginning to suspect some hardware directions in my investigation. i want
to give another piece of info - the 8 DSPs on the board are coupled to
interrupts lines - A B C D - got that info from the HW team. for eample,
device1 and device8 are bounded to interrupt line A. on the other hand, when
i look through the OS pci info i see that device1 has IntLine = 4 and device8
has IntLine = "a value different than 4" ( what is actually the meaning of
IntLine ?).
so, this problem seem to be a difficult one since there are many options here.
i hope that my explanation is clear even though i'm having a very hard time
to phrase it.
thanks a lot,
kobi.
.
- Prev by Date: Re: virtual serial driver asks for a reboot in windows 2000
- Next by Date: Re: Multiple Application is not working in Vista
- Previous by thread: Re: WinUSB on Windows 2000
- Next by thread: Re: NDIS driver and interface name
- Index(es):
Relevant Pages
|
