From: Russell King <rmk@arm.linux.org.uk>
To: Stuart MacDonald <stuartm@connecttech.com>
Cc: Matthew Wilcox <willy@debian.org>,
greg@kroah.com, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.linuxppc.org
Subject: Re: [parisc-linux] 3 Serial issues up for discussion (was: Re: Serial core problems on embedded PPC)
Date: Tue, 30 Jul 2002 16:53:51 +0100 [thread overview]
Message-ID: <20020730165351.C7677@flint.arm.linux.org.uk> (raw)
In-Reply-To: <00f801c237df$d09d4e40$294b82ce@connecttech.com>; from stuartm@connecttech.com on Tue, Jul 30, 2002 at 11:43:13AM -0400
On Tue, Jul 30, 2002 at 11:43:13AM -0400, Stuart MacDonald wrote:
> No, I was wondering if leaving the USB serial major 18[89] alone would
> be a better idea. Since posting, I've been thinking that the usb
> serial driver presents the same interface to the tty layer as any
> other serial device so I guess it's not a bad idea.
To be able to suck in USB (and some of the other drivers), two changes
need to be made to the core:
1. the change_speed method needs to be handled differently; we currently
assume a UART-style implementation here. We need to change this
around before 2.6 anyway for ports which don't support all the
termios settings (SuSv3 requires that any unimplemented features
retain their original values, so for example if we don't have RTS
and CTS lines on a particular implementation, CRTSCTS should be
initially off and not turn on-able.)
2. USB devices want "packets" of data to write rather than the ring-
buffer we currently use for UARTs.
(time to start ebaying for USB serial devices...)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-07-30 15:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 4:08 Serial core problems on embedded PPC David Gibson
2002-07-29 9:00 ` Russell King
2002-07-29 14:44 ` Tom Rini
2002-07-29 17:17 ` 3 Serial issues up for discussion (was: Re: Serial core problems on embedded PPC) Russell King
2002-07-29 17:43 ` Tom Rini
2002-07-29 18:13 ` Benjamin Herrenschmidt
2002-07-29 19:07 ` Tom Rini
2002-07-29 19:09 ` 3 Serial issues up for discussion (was: " Dan Malek
2002-07-29 19:46 ` Remco Treffkorn
2002-07-29 20:18 ` Russell King
2002-07-30 2:54 ` 3 Serial issues up for discussion David S. Miller
2002-07-30 18:23 ` Remco Treffkorn
2002-07-30 18:47 ` Nicolas Pitre
2002-07-30 18:51 ` Russell King
2002-07-30 18:44 ` Nicolas Pitre
2002-07-29 18:15 ` 3 Serial issues up for discussion (was: Re: Serial core problems on embedded PPC) Matt Porter
2002-07-29 17:47 ` [parisc-linux] " Christoph Plattner
2002-07-29 22:19 ` Matthew Wilcox
2002-07-30 14:36 ` Stuart MacDonald
2002-07-30 15:19 ` Matthew Wilcox
2002-07-30 15:43 ` Stuart MacDonald
2002-07-30 15:53 ` Russell King [this message]
2002-07-30 15:59 ` Greg KH
2002-07-30 16:06 ` Stuart MacDonald
2002-08-02 1:57 ` Jeff Randall
2002-07-30 2:51 ` 3 Serial issues up for discussion David S. Miller
2002-07-30 1:12 ` Serial core problems on embedded PPC David Gibson
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=20020730165351.C7677@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=stuartm@connecttech.com \
--cc=willy@debian.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