drivers/macintosh/Kconfig (was: Re: Linux 2.6.3-rc1)

[Brad Boyer]

On Mon, Feb 09, 2004 at 08:29:46AM +1100, Benjamin Herrenschmidt wrote:
> Ah, good to know, as I was about to do it too ! Though I don't
> fully agree with moving it to a new directory.
>
> > Seeing this makes me
> > wonder if that's what people think is the best idea. We could have
> > ADB support on non-Mac machines at some point.
>
> What for ? NeXT cubes ? :)

Honestly, I think the NeXT cubes will never be supported, but if
someone does get back into trying that, it might happen. The most
likely thing in my opinion is the iMate. Griffin Technology does
support using it (for keyboards/mice only) in Windows, so I think
it's a good idea to have Linux support for it, too.

> Well... via-pmu at least is a lot more than just an ADB host
> driver and should stay in drivers/macintosh. But if we go that way,
> then it make little sense to have via-pmu and via-cuda in different
> locations..

I've been thinking about splitting up the ADB and other functions
of the egret, cuda, and pmu. The abuse of adb_request for non-ADB
functionality should go away. With the new driver model, the ADB
bus will be represented as a generic bus and any request should
go to a specific bus or device. I don't want to have to assume
a single, global bus the way the current code does.

I would prefer to have ADB be really just for ADB. The power
management stuff should be a separate interface, and really
should be more generic across the different Mac power management
systems. Although the egret and cuda don't do as much as pmu,
they still manage poweroff, reset, and the PRAM/RTC. These are
totally unrelated to ADB, and that stuff I think should be left
in drivers/macintosh/.

	Brad Boyer
	flar at allandria.com


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/