All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	tytso@mit.edu,
	Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re: [driver] New life for Serial mice
Date: Thu, 7 Jun 2001 08:25:41 +0200	[thread overview]
Message-ID: <20010607082541.A166@suse.cz> (raw)
In-Reply-To: <20010606220832.A31009@flint.arm.linux.org.uk> <Pine.LNX.4.10.10106061527580.12135-100000@transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10106061527580.12135-100000@transvirtual.com>; from jsimmons@transvirtual.com on Wed, Jun 06, 2001 at 03:39:04PM -0700

On Wed, Jun 06, 2001 at 03:39:04PM -0700, James Simmons wrote:

> > > It would be nice if we had 
> > > 
> > > 1) A seperate serial directory under drivers.
> > > 
> > > 2) A nice structure that input devices and the tty layer can use. It is
> > >    just a waste to go threw the tty layer for input devices. It would also
> > >    make serial driver writing easier if the api is designed right :-) 
> > 
> > I am planning some day (don't know when yet though) to convert the 16x50
> > driver over to the serial_core stuff.
> 
> I ported it over to my tree. I will have to figure out how to incorporate
> the input serial stuff without breaking all the input drivers we have. In
> CVS we have alot of them. This will make life so much easier since all I
> will have to do is change one file for changes I make to the tty layer. I
> have improved andrew mortons console patch to work with multiple consoles
> and for different types of console devices. Instead of altering all the 
> console drivers I'm planning on intergrating the locking into the tty
> layer. That patch is needed for serial devices as well as video terminals.
> Your work might help speed up devleopement.

Sounds cute. Where do I find the result of your work?

> > NB, Ted Tytso mentioned something at the 2.5 conference about integrating
> > some of the serial layer with the tty layer.
> 
> What does he have in mind? I like to keep my VT changes in sync with what
> he has in mind.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2001-06-07  6:52 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
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 [this message]
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=20010607082541.A166@suse.cz \
    --to=vojtech@suse.cz \
    --cc=jgarzik@mandrakesoft.com \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    --cc=rmk@arm.linux.org.uk \
    --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.