linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: "David D. Kilzer" <ddkilzer@computer.org>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: mac-2.3.14.diff: adb
Date: Fri, 27 Aug 1999 16:32:37 +0200	[thread overview]
Message-ID: <19990827163237.012324@mailhost.mipsys.com> (raw)
In-Reply-To: <v03130308b3ec440550d3@[192.168.1.1]>


On Fri, Aug 27, 1999, David D. Kilzer <ddkilzer@computer.org> wrote:

>Well, drivers/macintosh is PPC ADB code.  If drivers/macintosh shouldn't
>exist, then shouldn't it be changed or moved at a higher level?
>
>In reality, there is some ADB mouse code in drivers/char, too, so I wonder
>if drivers/char/adb would make more/less sense than drivers/adb?

I personally like drivers/macintosh, from my point of view, it makes
things clearer. except for macserial, which should be killed in favor of
a more generic zilog driver, most of those drivers are really mac-centric
stuffs with no "generic" userland interface. Also, drivers/char is
already enough of a mess like this.

I didn't look at the those new patches, but the adb code in
driver/macintosh was abstracted to use a generic "adb controller"
sub-driver interface some time ago and so adb.c should be platform
independant (useable as-is on PPC and 68k). mac_keyb.c too, with all it's
specific mouse support.

David, did you make a generic (m68k/ppc) cuda driver too ?

-- 
           Perso. e-mail: <mailto:bh40@calva.net>
           Work   e-mail: <mailto:benh@mipsys.com>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  parent reply	other threads:[~1999-08-27 14:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <v03130327b3ebecbebbd3@[192.168.1.1]>
     [not found] ` <199908270917.LAA04250@lxp03.cern.ch>
1999-08-27 13:41   ` mac-2.3.14.diff: adb David D. Kilzer
1999-08-27 14:14     ` Jes Sorensen
1999-08-30 15:44       ` Michael Schmitz
1999-08-30 15:52         ` Jes Sorensen
1999-08-30 16:27           ` Michael Schmitz
1999-08-31  2:43           ` Paul Mackerras
1999-08-31  4:25             ` David D. Kilzer
1999-08-31  7:21               ` Paul Mackerras
1999-08-31  9:04                 ` Jes Sorensen
1999-08-31  9:11                   ` Geert Uytterhoeven
1999-08-31 17:00                     ` David A. Gatwood
1999-08-27 14:32     ` Benjamin Herrenschmidt [this message]
1999-08-28  1:20       ` David D. Kilzer
1999-08-28 11:58         ` Geert Uytterhoeven
1999-09-06 13:37     ` 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=19990827163237.012324@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=ddkilzer@computer.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).