public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux Kernel List <linux-kernel@vger.kernel.org>,
	Ralf Baechle <ralf@linux-mips.org>
Subject: Re: drivers/char/dz.[ch]: reason for keeping?
Date: Sun, 4 Apr 2004 14:00:51 +0200	[thread overview]
Message-ID: <20040404120051.GF27362@lug-owl.de> (raw)
In-Reply-To: <20040404122958.A14991@flint.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]

On Sun, 2004-04-04 12:29:58 +0100, Russell King <rmk+lkml@arm.linux.org.uk>
wrote in message <20040404122958.A14991@flint.arm.linux.org.uk>:
> On Sun, Apr 04, 2004 at 01:17:12PM +0200, Jan-Benedict Glaw wrote:
> So we just need the VAX people to confirm that the new driver works
> for them, and then for _someone_ to remove the old driver (either
> the MIPS or the VAX people.)

Let me do some surgery :)

Interrupt setup is a bit tricky on the VAXen. First, they actually have
separated RX and TX IRQ and these aren't static. IRQ probing needs to be
redone (at least can't be easily copied) since the new dz_init() is
basically a complete new rewrite...

> > While at it, I've already implemented some SERIO changes. That'll allow
> > the dz.c driver to announce that it waits for LK-style keyboard on one
> > port and VSXXX-style mouse/digitizer on the 2nd port...
> 
> Which dz.c ? 8)

Old ./drivers/char/dz.c + VAX changes + SERIO changes, that is :)  I
guess best practice is that VAX people first merge up with MIPS folks,
then we snatch the old driver together and have a beer...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-04-04 12:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-04  9:12 drivers/char/dz.[ch]: reason for keeping? Russell King
2004-04-04 11:17 ` Jan-Benedict Glaw
2004-04-04 11:29   ` Russell King
2004-04-04 12:00     ` Jan-Benedict Glaw [this message]
2004-04-07 11:16       ` Maciej W. Rozycki
2004-04-07 12:39         ` Jan-Benedict Glaw
2004-04-07 13:27           ` Maciej W. Rozycki
2004-04-08 21:23         ` Kenn Humborg
2004-04-05 13:15 ` Maciej W. Rozycki
2004-04-05 13:19   ` Russell King
2004-04-05 13:35     ` Maciej W. Rozycki
2004-04-05 19:14     ` Ralf Baechle

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=20040404120051.GF27362@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.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