> -----Original Message-----
From: Alex Spelling [mailto:xxxxx@yahoo.com]
Sent: Monday, January 21, 2002 7:06 PM
To: NT Developers Interest List
Subject: [ntdev] IDT and PCI interrupts under NT and XP with ACPI
Guys,
I try to localize the problem with my driver.
As far as I understand Win uses interrupts from 0x30
to 0x3F to map IRQ0-IRQ15. Say, PCI device sits on
IRQ5, then I put bp into code where int35 points.
I put breakpoint under SoftIce into the code where IDT
points.
Under NT I always get interrupt in SoftIce and later
on in my ISR.
When I do the same under XP with ACPI driver installed
I never see interrupts on vector 0x3B (IRQ11 this time
- or whatever interrupt board uses).
I know for sure that PCI device driver has requested
this interrupt (WinXP reports IRQ11 in the Device
Manager) and device driver is up and running. Also
memory mapped I/O with this device works just fine. I
can see INTA line asserted under bus analyzer, I can
verify timing according to PCI specs, etc.
Could you please explain me where the problem can be?
Also, in Device Manager I see memory range conflict
and in the list of conflicting devices I see… my own
driver.
Looks like you are using unmodified NT4 code on Win2K/XP;
I’ve seen exactly the described behavior for such a beast
(with HalAssignSlotResources NT4-style, NULL instead of pDeviceObject)
- it run on non-ACPI and silently failed to receive interrupts on ACPI;
Device Manager showed memory conflict as you described; and I/O was just
fine.
Regards,
Alexander Krol
Software Engineer, Technologies/Data Group
E-mail: xxxxx@creo.com
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/
You are currently subscribed to ntdev as: xxxxx@creoscitex.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com