From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Brad Boyer <flar@allandria.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Linux/m68k on Mac <linux-mac68k@mac.linux-m68k.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: drivers/macintosh/Kconfig (was: Re: Linux 2.6.3-rc1)
Date: Mon, 09 Feb 2004 08:29:46 +1100 [thread overview]
Message-ID: <1076275785.885.94.camel@gaston> (raw)
In-Reply-To: <20040208205734.GA13906@pants.nu>
> I've started rewriting ADB for the new driver model, and I have been
> putting it into a new directory, drivers/adb/.
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 ? :)
> I'll try to get the
> Griffin iMate (a UDB-ADB converter) working at some point, although
> the built-in interfaces take priority for me. The hydra chip is
> technically not in any Mac either, although it's very much a Mac
> oriented chip. I personally think drivers/macintosh/ should be
> limited to things like macio-*, mediabay, and other similar stuff.
> Anyone care to comment?
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..
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-08 21:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0402061823040.30672@home.osdl.org>
2004-02-08 14:25 ` drivers/macintosh/Kconfig (was: Re: Linux 2.6.3-rc1) Geert Uytterhoeven
2004-02-08 14:53 ` David D. Kilzer
2004-02-08 19:32 ` Geert Uytterhoeven
2004-02-08 20:57 ` Brad Boyer
2004-02-08 21:15 ` [linux-mac68k] " David D. Kilzer
2004-02-08 22:16 ` Geert Uytterhoeven
2004-02-08 23:00 ` David D. Kilzer
2004-02-08 21:29 ` Benjamin Herrenschmidt [this message]
2004-02-08 21:59 ` Brad Boyer
2004-02-08 22:22 ` Benjamin Herrenschmidt
2004-02-08 23:05 ` Brad Boyer
2004-02-08 22:07 ` [linux-mac68k] " Matthias Urlichs
2004-02-08 22:19 ` Brad Boyer
2004-02-08 22:25 ` Benjamin Herrenschmidt
2004-02-08 22:39 ` Matthias Urlichs
2004-02-08 21:26 ` Benjamin Herrenschmidt
2004-02-08 22:07 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1076275785.885.94.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=flar@allandria.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mac68k@mac.linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).