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.
Regards,
Alex
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/
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
Since there are different ways you can choose to get hardware
resources allocated to you, all I can suggest is that you verify
you are doing it correctly. The normal variant is to use
HalAssignSlotResources, parse the list and IoConnectInterrupt.
If your PCI device is screwed you might have to resort to
IoReportResourceUsage. Since you get youself into a conflict,
you should carefully analyze if you are following the correct
procedure, and check return codes.
— Alex Spelling wrote:
> 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.
>
> Regards,
> Alex
>
>
>
> Do You Yahoo!?
> Send FREE video emails in Yahoo! Mail!
> http://promo.yahoo.com/videomail/
>
> —
> You are currently subscribed to ntdev as: xxxxx@yahoo.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/
—
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