PPB ints. and IRQ routing

[rdunlap@atlanta.nsc.com (Randy Dunlap)]

Hi,

In testing an NDIS 3 Ethernet driver for Windows 95,
Microsoft's test spec. requires a PCI bridge test.
Microsoft even specifies that the DEC PCI bridge adapter
be used in this test.

OK.  I have the DEC PCI bridge adapter (EB52) and its
accompanying DOS utilities software.
I have several PCs with Windows 95 installed.
I have a working Ethernet driver when the Ethernet adpater
is installed in a system board PCI slot.

When I install the Ethernet adapter in the DEC PPB adapter
and use the DEC pconf program to configure the PPB's
inserted adapters, the Ethernet adapter is configured.
I can see this by using the DEC pview program.

When I load Windows 95 and my driver, Windows 95 knows where
the Ethernet adapter is and tells my driver the I/O address
of the Ethernet adapter.  The driver initializes the adapter,
etc. etc. etc.  All is well until the adapter needs to
interrupt the host/OS/driver.  NO interrupts are seen.

This looks like a PCI INT/IRQ routing problem to me.
Any suggestions/ideas for overcoming it?
Do I just need to use some BIOS code that is more recent?

I have written small programs to dump the PCI Interrupt Routing
Options table and to try to Set the PCI INT/IRQ routing.
The latter one fails.  In looking thru the AMI BIOS on the
PC I am using, the BIOS code will only attempt to set
the PCI IRQ routing for devices that are in the BIOS's
bus/device table, which only contains bus 0 devices, and
the DEC PPB's additional adapters (like my Ethernet adapter)
are on bus 1.  Windows 95 see the device (adapter) on bus 1,
but cannot fix its IRQ routing (?).

Loading the DEC PPBX TSR (to add some int. 1A support for the
DEC PPB) does not help any (at least the 1995 version that I
have does not help).

Help, ideas, suggestion, comments welcome.

Thanks,
Randy
&
èØ