> 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 Without a scope on the board running both 2.2 and 2.6 that would be hard to tell. > 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? Can we do this in a sensible, logical diagnostic order please. You are making assumptions that seem unwise - eg that the code didn't happen to work in 2.2.5 even though it was not correctly setting hardware flow control, or that the defaults set by the user space apps run with the distribution haven't changed and thus shown up such a problem. Also was the 2.2 and 2.6 on the same exact mainboard ? You've verified that flow control does not seem to be getting asserted for h/w control on the wires Next question on the software side therefore is does the serial port have CRTSCTS set when the problem is showing up. (stty -a </dev/ttyWhatever) - To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
