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 for Android: free password hash cracker in your pocket

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

Message-ID: <46A9F712.70706@imap.cc>
Date:	Fri, 27 Jul 2007 15:45:54 +0200
From:	Tilman Schmidt <tilman@...p.cc>
To:	Lee Howard <faxguy@...ardsilvan.com>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	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

Lee Howard schrieb:
> 
> So, does this explain why I wouldn't have a problem at 115200 bps with 
> kernel 2.2.5 but why I do with 2.6.5 and 2.6.18?  Both hardware and 
> software flow control work fine with 2.2.5 (meaning I don't see any 
> error message and I don't have any data corruption), but neither works 
> to avoid the "kernel: ttyS1: 1 input overrun(s)" and consequent data 
> corruption issue in 2.6.5 nor 2.6.18.
> 
> Was there some associated application change in tty handling that needed 
> to occur between the 2.2 and 2.6 kernels to properly implement flow control?

Could this be related?

http://lkml.org/lkml/2007/7/18/245

Quote:
"I've recently found (using 2.6.21.4) that configuring a serial ports
(ST16654) which use the 8250 driver using setserial results in the
UART's FIFOs being disabled (unless you specify autoconfig)."

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


Download attachment "signature.asc" of type "application/pgp-signature" (251 bytes)