On Fri, Jan 26, 2007 at 11:08:42AM -0500, Lennart Sorensen wrote: > OK, the tty settings according to stty that I am using are: > # stty -F /dev/ttyn0 -a > speed 230400 baud; rows 0; columns 0; line = 0; > intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = > <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; > werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; > -parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts > -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -ixon > -ixoff -iuclc -ixany -imaxbel > -opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 > ff0 > -isig -icanon iexten -echo -echoe echok -echonl -noflsh -xcase -tostop > -echoprt echoctl echoke > > So min and time seems good. I am not explicitly setting those in my > test program (unless one of the other settings implies it). I will add > it explicitly just in case too.
I have run some tests with 8 patches from Linus's 2.6 tree on top of the 2.6.16.25 along with a bit of debug code in the n_tty.c, which ran perfectly for 3 days. I now removed the debug code to see if it will still run perfectly with those 8 patches. The patches I applied in order are: commit 70522e121a521aa09bd0f4e62e1aa68708b798e1 commit 41c28ff1635e71af072c4711ff5fadd5855d48e7 commit 1aef821a6b3aeca8c19d06aee012ed9db617d1e3 commit ee37df7877eeaa16d7761cce64854110a7c17ad9 commit e1a2509023785bd3199ac068ab80155aeba01265 commit 817d6d3bceaf34c99f5343820f9b9e6021f0655c commit 2c3bb20f46709a0adfa7ea408013edbcab945d5a commit 33b37a33c242542fac2980b8ccd90977388b7a8d Hopefully it will stay working, and actually be a solution to my tty problem in 2.6.16.25. 2.6.18.2 (Debian 2.6.18-4) on the other hand was still broken, but I am not sure which if any of the above commits are not in that version (the date ranges made me think they all should be, but maybe I got the date of 2.6.18 wrong, or not all commits in the linux-2.6 tree are actually part of a given release. I am still figuring out git). -- Len Sorensen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
