On Sat, Nov 20, 2010 at 12:27:43PM -0500, gene heskett wrote: > On Saturday, November 20, 2010 12:20:24 pm Johan Hovold did opine: > > This could be related to a change that was incorrectly made to the > > DTR/RTS handling. This change has later been reverted (commit > > 677aeafe19e88c282af74564048243ccabb1c590 upstream). > > > How long has this incorrectness existed? I have a 9600 baud connection to > an old old machine in the basement that cannot handle a 9600 baud rzsz file > move from minicom unless I reset the port speed to 4800 baud else minicom > ignores the DTR/CTS drops and keeps on pouring the data into the pipe. The bad commit was made on June 3rd this summer. Unfortunately, it was marked for stable and then later back-ported to all stable trees. I think it hit 2.6.32 around 2.6.32.14 or so. You should be able to find out by searching the logs for the commit id of the reverted commit (6a1a82df91fa0eb1cc76069a9efe5714d087eccd "USB: ftdi_sio: fix DTR/RTS line modes"). > > Could you see if 2.6.37-rc2 works as it should? The revert will also be > > part of 2.6.36.1 (and 2.6.35.9) soon to be released. > > Sounds like a good excuse to rebuild a kernel that only has about an hours > uptime on Mike Galbraith's scheduler patches, and they are definitely a > keeper. Yeah, those ones look really promising. Thanks, Johan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
