Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Harald Koerfgen <hkoerfg@web.de>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Ralf Baechle <ralf@uni-koblenz.de>
Cc: linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: [patch] 2.4.5: DECstation LK201 keyboard non-functional
Date: Mon, 16 Jul 2001 22:28:14 +0200	[thread overview]
Message-ID: <01071622281400.00525@intel> (raw)
In-Reply-To: <Pine.GSO.3.96.1010716195815.12988F-100000@delta.ds2.pg.gda.pl>

On Monday 16 July 2001 20:43, Maciej W. Rozycki wrote:
[DECstation Keyboard]

>  Note while putting a file away from an arch-specific tree into a generic
> driver one might seem a bad move, it really is the right thing in this
> case.  The point is the decserial.c device is not arch-specific at all,
> i.e. no more than the 8250 serial.c device is.  DEC used the devices in a
> number of their systems, including DECstations (onboard SCC and DZ11 and
> TURBOchannel PMAC-A DZ11 devices), DEC 3000 Alpha systems (onboard SCC and
> PMAC-A devices) and VAXstations (onboard DZ11 and PMAC-A devices).  Thus I
> believe they should be treated as generic devices, especially as the VAX
> and the DEC 3000 Alpha (to some extent) Linux ports are underway.

I tend to agree, but maybe I'm biased.  On the other hand, it would prpbably 
be better to modularize the dz and zs drivers.

However, if nobody has any objections I'll commit this for the 2.4 series.

Greetings,
Harald
-- 
Don't look now, but there is a multi-legged creature on your shoulder.

  reply	other threads:[~2001-07-16 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 18:43 [patch] 2.4.5: DECstation LK201 keyboard non-functional Maciej W. Rozycki
2001-07-16 20:28 ` Harald Koerfgen [this message]
2001-07-16 20:38   ` Maciej W. Rozycki
2001-07-17 20:05 ` Dave Airlie
2001-07-17 20:05   ` Dave Airlie
2001-07-18 13:33   ` Maciej W. Rozycki

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=01071622281400.00525@intel \
    --to=hkoerfg@web.de \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=ralf@uni-koblenz.de \
    /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