linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 11:11:42 -0700	[thread overview]
Message-ID: <46AA355E.20901@howardsilvan.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0707271825220.425@blysk.ds.pg.gda.pl>

Maciej W. Rozycki wrote:

> The TTY line discipline driver could do that based on the amount of 
>received data present in its buffer.  And it should if asked to (a brief 
>look at drivers/char/n_tty.c reveals it does; obviously there may be a bug 
>somewhere though).  So could e.g. the SLIP and PPP line discipline 
>drivers, though the criteria might be different (apparently they do not, 
>which is a shame).
>
> The serial drivers have nothing to do about it -- all they can do is 
>pushing data upstream, to the discipline driver.  They can provide an 
>interface to hardware flow control features though, if implemented by a 
>given UART.
>

Thank you for this clarification.  So I should have more correctly been 
saying that "tty flow control appears broken".  Right?

I've asked the manufacturer to take a look at drivers/char/n_tty.c to 
see if they can't see anything obvious.

Thanks,

Lee.

  reply	other threads:[~2007-07-27 18: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
2007-07-27 17:41         ` Alan Cox
2007-07-27 17:53         ` Maciej W. Rozycki
2007-07-27 18:11           ` Lee Howard [this message]
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=46AA355E.20901@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).