From: Lee Howard <faxguy@howardsilvan.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-serial@vger.kernel.org, tytso@mit.edu,
rmk@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: serial flow control appears broken
Date: Fri, 27 Jul 2007 10:11:36 -0700 [thread overview]
Message-ID: <46AA2748.80703@howardsilvan.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0707271216410.425@blysk.ds.pg.gda.pl>
Maciej W. Rozycki wrote:
>On Thu, 26 Jul 2007, Lee Howard wrote:
>
>
>
>>If the application were to use TIOCM_RTS how would it know when to apply it or
>>not? Is there some approach that the application could take to manage flow
>>control on the serial port? What about software flow control? Does the
>>
>>
>
> Well, an application could negate RTS when it receives a character and
>is running out of resources for further processing of incoming data.
>
> Smarter UARTs may be able to negate RTS themselves based on the amount of
>data in their receive FIFO. The threshold may be configurable.
>
Okay, so let's say we've got a loop around a blocking read on the modem
file descriptor...
for (;;) {
read some data from modem
process data from modem
if (end-of-data detected) break;
}
Are you suggesting that the application should be using deasserting RTS
after the read and asserting it before?
I had previously thought that the control of RTS was something that the
serial/tty driver was supposed to do independently based on the buffer
fill. Was I wrong?
Thanks,
Lee.
next prev parent reply other threads:[~2007-07-27 17:13 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.Z6O0xFRT69zes0Mg+agt3Uiwux4@ifi.uio.no>
2007-07-26 7:20 ` serial flow control appears broken Robert Hancock
2007-07-26 16:08 ` Lee Howard
2007-07-26 16:31 ` Alan Cox
2007-07-27 5:53 ` Lee Howard
2007-07-27 13:45 ` Tilman Schmidt
2007-07-27 20:05 ` Lee Howard
2007-08-27 20:38 ` Paul Fulghum
2007-07-27 20:48 ` Lee Howard
2007-07-27 23:28 ` Paul Fulghum
2007-07-28 4:51 ` Lee Howard
2007-07-28 9:18 ` Russell King
2007-07-28 12:00 ` Alan Cox
2007-07-28 15:39 ` Lee Howard
2007-07-28 16:41 ` Ray Lee
2007-08-04 18:21 ` Lee Howard
2007-08-04 22:07 ` Paul Fulghum
2007-08-05 0:00 ` Lee Howard
2007-08-05 14:52 ` Paul Fulghum
2007-07-27 11:32 ` Maciej W. Rozycki
2007-07-27 17:11 ` Lee Howard [this message]
2007-07-27 17:41 ` Alan Cox
2007-07-27 17:53 ` Maciej W. Rozycki
2007-07-27 18:11 ` Lee Howard
2007-07-30 9:36 ` Maciej W. Rozycki
2007-07-27 18:22 ` Robert Hancock
2007-07-27 18:46 ` Paul Fulghum
2007-07-27 19:05 ` Paul Fulghum
2007-07-30 9:39 ` Maciej W. Rozycki
2007-07-27 19:14 ` Paul Fulghum
2007-07-28 9:28 ` Russell King
2007-07-30 9:45 ` Maciej W. Rozycki
2007-07-30 9:59 ` Russell King
2007-08-02 14:57 ` Mark Lord
2007-08-02 16:14 ` Robert Hancock
2007-08-02 16:29 ` Mark Lord
2007-08-02 16:40 ` Robert Hancock
2007-08-02 17:13 ` Alan Cox
2007-08-04 19:38 ` Lee Howard
2007-08-02 16:57 ` Alan Cox
2007-08-02 17:02 ` Robert Hancock
2007-08-03 9:32 ` Maciej W. Rozycki
2007-07-30 9:34 ` Maciej W. Rozycki
2007-08-04 18:19 ` Lee Howard
2007-07-26 1:52 Lee Howard
2007-07-26 12:34 ` Uwe Kleine-König
2007-07-26 16:28 ` Lee Howard
2007-07-26 16:41 ` Alan Cox
2007-07-27 6:17 ` Lee Howard
2007-07-27 11:56 ` Alan Cox
2007-07-27 18:00 ` Lee Howard
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=46AA2748.80703@howardsilvan.com \
--to=faxguy@howardsilvan.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=macro@linux-mips.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).