>As for whether or not this code should be in the kernel is an interesting
>question. If it is not, then where does it go? How does the kernel
>figure out the PCI topology? You could have a bootloader/console that
I'd like to see it go in the kernel at least as an option. With the exception
of interrupt routing, the kernel can do as good a job of the PCI configuration
as the console could. On platforms where the interrupt lines are fixed
(NetWinder and CATS for example, but not EBSA-285) it can do everything.
Also, experience shows that we tend to end up having code in the kernel to go
through and fix up things that the console didn't do the way we wanted them in
any case. We might as well not bother and just let the kernel do the whole
lot in the first place.
p.
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
