linux-kernel - Re: Serial Flow Control

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]

Date:	Tue, 17 Mar 2009 08:57:14 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Rocker Dude <life.does.rock@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Serial Flow Control

On Tue, 17 Mar 2009 11:04:36 +0530
Rocker Dude <life.does.rock@...il.com> wrote:

> Hi All,
> 
> I am using a powerpc8548e custom hardware and testing flow control on
> it. I have cross-wired the RTS/CTS of the board with my host terminal.
> I find that when I am reading from the powerpc, it does not change the
> CTS signal when it is running out of buffers and hence it is dropping
> bytes.
> 
> I referred to something similar at http://lkml.org/lkml/2007/7/26/46.
> 
> Can anyone please tell me if this flow control needs to be done by the SW?

Flow control needs to be enabled by the user space software (if not
enabled already), managed by the line discipline and implemented by the
device driver (or automatically in hardware in some cases)

Basically; App "set CRTSCTS"
Ldisc: buffers full/not full logic for throttling
Driver: throttling events -> flow control, honour flow on write
--
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/