From: Vojtech Pavlik <vojtech@suse.cz>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org, tytso@mit.edu
Subject: Re: [driver] New life for Serial mice
Date: Wed, 6 Jun 2001 19:01:58 +0200 [thread overview]
Message-ID: <20010606190158.A2010@suse.cz> (raw)
In-Reply-To: <20010606125556.A1766@suse.cz> <3B1E5AE0.9202DD00@mandrakesoft.com>
In-Reply-To: <3B1E5AE0.9202DD00@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, Jun 06, 2001 at 12:31:28PM -0400
On Wed, Jun 06, 2001 at 12:31:28PM -0400, Jeff Garzik wrote:
> hmmm. I just looked over this, and drivers/char/joystick/ser*.[ch].
>
> Bad trend.
>
> Serial needs to be treated just like parport: the basic hardware code,
> then on top of that, a selection of drivers, all peers: dumb serial
> port, serial mouse, joystick, etc.
Agreed. Completely.
And proposed a couple times before.
But not in my power.
So I used a N_MOUSE line discipline instead
- the best tap into the serial/tty stack I found.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-06-06 17:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 10:55 [driver] New life for Serial mice Vojtech Pavlik
2001-06-06 11:23 ` Guest section DW
2001-06-06 16:17 ` James Simmons
2001-06-06 17:04 ` Vojtech Pavlik
2001-06-06 16:31 ` Jeff Garzik
2001-06-06 17:01 ` Vojtech Pavlik [this message]
2001-06-06 17:22 ` Russell King
2001-06-06 20:20 ` James Simmons
2001-06-06 21:08 ` Russell King
2001-06-06 22:39 ` James Simmons
2001-06-07 6:25 ` Vojtech Pavlik
2001-06-07 17:09 ` James Simmons
2001-06-06 23:21 ` Pavel Machek
2001-06-08 16:15 ` Vojtech Pavlik
2001-06-08 16:20 ` Pavel Machek
2001-06-08 16:28 ` Vojtech Pavlik
2001-06-08 20:19 ` Mike Coleman
2001-06-08 20:57 ` (driver) " Pavel Machek
2001-06-09 9:01 ` [driver] " Vojtech Pavlik
2001-06-08 18:28 ` John R Lenton
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=20010606190158.A2010@suse.cz \
--to=vojtech@suse.cz \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.