I still don't think the PALs on the card need to know Jack. The CPU and driver only need to know the Slot ID and Address Block in which the NIC resides. If the Slot manager can identify the NIC, it can run the NIC, the NIC itself is a relatively dumb I/O device. Only the DeclROM of the Card has any preconceived notions about what the card is supposed to be, what it's supposed to do and where it's supposed to be doing it . . .
. . . and that, can be changed. [}
] ]'>
I'm not even certain the LC cards need to know what slot they are in, it's always the same and it's the slot that knows it's $E, wire the LC NIC to a different interrupt that's available on the /30 & si and the Slot Manager will find it and run it. The NIC doesn't run anything or know from where its strings are being pulled.
Buzz the connections on an SE/30/IIsi NIC with jumpers for changing the addresses. Dollars to Doughnuts they only A/B switch the card Slot Address input between whatever address lines it's wired to.
. . . and that, can be changed. [}
] ]'>I'm not even certain the LC cards need to know what slot they are in, it's always the same and it's the slot that knows it's $E, wire the LC NIC to a different interrupt that's available on the /30 & si and the Slot Manager will find it and run it. The NIC doesn't run anything or know from where its strings are being pulled.
Buzz the connections on an SE/30/IIsi NIC with jumpers for changing the addresses. Dollars to Doughnuts they only A/B switch the card Slot Address input between whatever address lines it's wired to.