Dave Baukus said:
> Other problems include:
> - the PCI code does not assign IO or Mem addresses to PCI devices
Correct. This should be done by a boot loader and not the kernel. The Linux kernel
was never intended to boot up a system.
> - there are some assumptions in the PCI inerrupt mapping that didn't
> work for me.vPCI interupt mapping seems to assume that the ebsa board
> is in the system slot of my PCI backplane (slot 3 has the same
> interupt mapping as the system slot).
These aren't assumptions. The fact of PCI is that there are at the most 4 interrupts.
On each card, these are labelled INTA, INTB, INTC, and INTD. The mapping between
the physical connections on the motherboard and the slots is motherboard dependent,
but normally you have something like:
System Slot 1 Slot 2 Slot 3
A B C D
B C D A
C D A B
D A B C
Cards normally drive INTA, the first row. Hence, if you plug the EBSA285 into the
system slot and a card into slot 1, then it's interrupt will normally be on System's
B. However, if you plug the EBSA285 into slot 3, ut appears on C.
Therefore, if you don't plug the EBSA285 into the correct slot, it will not work, and
there's nothing that the kernel can really do at the moment.
This sort of stuff is normally handled by the machine's BIOS, and the results are
stored into the configuration registers on each card.
--
Russell King ([EMAIL PROTECTED])
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
