I have a pci card which contains multiple pci devices behind a transparant
bridge. The majority of the secondary devices are controlled by i960
processor which actually also performs the bridge function. One of the
secondary devices is a 1394 device which was added for expandability and
the hope was that the windows 2000 provided 1394 drivers would provide
access to this device. Problem was that when the hardware was done it
didn’t follow the recommendation in the pci spec concerning how to map
interrupts. The 1394 device is devsel id 2 which according to my
interpretation of the recommendation should interrupt via INTC. However my
hardware maps this to INTA. This hardware doesn’t even connect the INTC
output from the 960 processor to the primary pci interface so I can’t catch
the interrupt in the embedded processor and forward it to the pci via an
output doorbell.
What I was wondering was if there is a way to catch the interrupt in kernel
mode driver and then pass it along to the windows driver via some software
interrupt mechanism. I already have a kmd which services interrupts from
my board for the other “supported devices”. If I could recognize an
interrupt from the 1394 device and I had read the config space of the
device, could I somehow (via int nn command) generate an interrupt which
would correctly propagate to the windows 1394 device driver?
TIA
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