From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Ed Vance <EdV@macrolink.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: what serial driver restructure is planned?
Date: Thu, 7 Feb 2002 10:21:44 +0000 [thread overview]
Message-ID: <20020207102144.B15226@flint.arm.linux.org.uk> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A768A@EXCHANGE>
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A768A@EXCHANGE>; from EdV@macrolink.com on Wed, Feb 06, 2002 at 10:32:11AM -0800
On Wed, Feb 06, 2002 at 10:32:11AM -0800, Ed Vance wrote:
>
> > o Beta Serial driver restructure (Russell King)
>
> Regarding the above line from the 2.5 STATUS report, what is the nature of
> the planned restructuring? I have a CompactPCI hot swap serial mux card
> that I need to support with hot swap functionality on Linux. Has anybody
> already worked on issues like locking port names to physical slots, etc.?
> Any basic advice?
You can checkout a copy of the code - see www.arm.linux.org.uk/cvs
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. Some people would also like
to see a "serial major" where all serial devices live.
next prev parent reply other threads:[~2002-02-07 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 18:32 what serial driver restructure is planned? Ed Vance
2002-02-07 10:21 ` Russell King - ARM Linux [this message]
2002-02-11 16:30 ` Nick Craig-Wood
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=20020207102144.B15226@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=EdV@macrolink.com \
--cc=linux-kernel@vger.kernel.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