Linus> And trying to impose any SBUS behaviour on the PCI resource
Linus> allocation is just NOT going to happen. Ever. Either you make
Linus> it look exactly like PCI from a device driver standpoint (at
Linus> which point you might as well just admit to the fact that it IS
Linus> PCI as far as Linux is concerned, it just has slightly
Linus> different connectors - and you shouldn't complain about
Linus> PCI-only issues), OR you make it a primary bus in its own
Linus> right, with its own resource allocation and with its own access
Linus> functions and with its own identification functions.
The only thing that sucks about this is when you have adapters with
the exact same chips on them on both PCI and SBUS and you would like
to write a generic driver which determines at runtime what type of bus
it is on. Having to recompile the same code with new macros one for
sbus and one for pci is evil as well.
Not sure what the pretty solution is though.
Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/