Re: SSB AI support code

["Michael Büsch" <mb@bu3sch.de>]

On Wed, 2011-02-09 at 22:35 +0100, Rafał Miłecki wrote: 
> What about proposed solution?

Well, I'm not going to maintain it due to a lack of devices,
knowledge of the AI and a serious lack of additional time.

However, I'm certainly OK with you adopting maintainership
if people think that the code looks sane and should be merged.

One thing I really don't like is the name-confusion introduced
by this. We will have functions with the ssb_...() prefix
that don't necessarily operate on ssb devices, but on AI devices
instead, depending on the actual magic behind the scenes.
That's one of the major things I tried hard to avoid in the
SSB design from day 0 on.
It's what I hated most about Broadcom's SB implementation (there it
is pci_...() functions, which operate on PCI, SB or whatever else
depending on some serious magic).

So my proposal doesn't change: Create two separate busses (SSB and AI)
and port the device drivers to work on both. That also implies
decoupling the built-in SSB device drivers (CC, MIPS, EXTIF, PCICORE)
from the SSB implementation.
The code duplication will negligible.

-- 
Greetings Michael.