Re: serial flow control appears broken

[Tilman Schmidt <tilman@imap.cc>]

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

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@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]