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: [email protected] Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: serial flow control appears broken
- From: Lee Howard <[email protected]>
- Re: serial flow control appears broken
- From: Paul Fulghum <[email protected]>
- Re: serial flow control appears broken
- References:
- Re: serial flow control appears broken
- From: Robert Hancock <[email protected]>
- Re: serial flow control appears broken
- From: Lee Howard <[email protected]>
- Re: serial flow control appears broken
- From: Alan Cox <[email protected]>
- Re: serial flow control appears broken
- From: Lee Howard <[email protected]>
- Re: serial flow control appears broken
- Prev by Date: Re: NFSv4 poops itself
- Next by Date: request for patches: showing mount options
- Previous by thread: Re: serial flow control appears broken
- Next by thread: Re: serial flow control appears broken
- Index(es):
 |