From: Nick Craig-Wood <ncw@axis.demon.co.uk>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: what serial driver restructure is planned?
Date: Mon, 11 Feb 2002 16:30:59 +0000 [thread overview]
Message-ID: <20020211163059.A22996@axis.demon.co.uk> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A768A@EXCHANGE> <20020207102144.B15226@flint.arm.linux.org.uk>
In-Reply-To: <20020207102144.B15226@flint.arm.linux.org.uk>; from linux@arm.linux.org.uk on Thu, Feb 07, 2002 at 10:21:44AM +0000
On Thu, Feb 07, 2002 at 10:21:44AM +0000, Russell King - ARM Linux wrote:
> It basically started out by pulling 65K worth of the duplicated code out
> of various serial drivers. Its currently moving towards allowing the
> input layer to talk to serial devices (needed for things like iPAQ
> keyboards and IrDA-based keyboards), as well as allowing things like
> USB serial devices to use the core code.
Could we also have an interface to serial devices which bypass the tty
layer? Ie a /dev/ttyraw* which just speaks to the serial port without
going through the labyrinthine tty layers?
This would need to keep some basic ioctls for changing baud rate etc.
9 times out of 10 when I reach for /dev/ttyS* that is all I want and
the tty layer is just wasteful and gets in the way of a conceptually
very simple device.
> Some people would also like to see a "serial major" where all serial
> devices live.
Gets my vote.
--
Nick Craig-Wood
ncw@axis.demon.co.uk
next prev parent reply other threads:[~2002-02-11 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 18:32 Ed Vance
2002-02-07 10:21 ` Russell King - ARM Linux
2002-02-11 16:30 ` Nick Craig-Wood [this message]
2002-02-11 22:01 ` Alan Cox
2002-02-12 10:38 ` Rogier Wolff
2002-02-07 16:11 ` Greg KH
[not found] <194.2606a8e.299fb282@aol.com>
2002-02-16 17:06 ` Alan Cox
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=20020211163059.A22996@axis.demon.co.uk \
--to=ncw@axis.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®