I would like to use the Device Installation Functions of the DDK to “force”
a PnP device to use a different interrupt than what was selected at boot
time. My problem is the driver in question is the MS 1394 OHCI driver so I
don’t have access to source code for it.
I have a 1394 device on the secondary side of a PCI bridge (an Intel 960 RN
device) and PnP sometimes (most times) assigns a different IRQ to the 1394
device when it needs to use the same IRQ as the Intel 960 (since there is
only one INTR coming off the board). Is this possible by using the Device
Installation Functions to create a “forced configuration” or am I hosed?
Does anyone have any other suggestions?
Thanks
Jeff
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
xxxxx@pinnaclesys.com said:
I have a 1394 device on the secondary side of a PCI bridge (an Intel
960 RN device) and PnP sometimes (most times) assigns a different IRQ
to the 1394 device when it needs to use the same IRQ as the Intel 960
(since there is only one INTR coming off the board).
Ths BIOS is supposed to make assumptions about INTx# routing when
a PCI-to-PCI bridge is plugged into a PCI slot.
for device number 0, 4, 8, 12… INTA# connects to INTA# of the card,
for device nubmer 1, 5, 9, 13,… INTA# connects to INTB# of the card,
etc. What IRQ is assigned to INTB# of the card is a hardware constraint.
You can’t in general change the IRQ assignment in software.
You can generate the INTx# interupts from the i960RN processor, so
you can arrange for the routing to be like this in i960 software. If
your board designer was hip enough to realize this rule, then you
might be able to set the i960bridge to pass through the interrupts.
Steve Williams “The woods are lovely, dark and deep.
xxxxx@icarus.com But I have promises to keep,
xxxxx@picturel.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep.”
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