linux-kernel - Re: serial flow control appears broken

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64N.0707271216410.425@blysk.ds.pg.gda.pl>
Date:	Fri, 27 Jul 2007 12:32:54 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Lee Howard <faxguy@...ardsilvan.com>
cc:	Robert Hancock <hancockr@...w.ca>, linux-serial@...r.kernel.org,
	tytso@....edu, rmk@....linux.org.uk, linux-kernel@...r.kernel.org
Subject: Re: serial flow control appears broken

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.

  Maciej
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/