On Fri, Jan 26, 2007 at 08:51:02AM -0600, Paul Fulghum wrote: > You can eliminate the tty buffering altogether > by observing what gets passed to the line discipline.
I will have to find where in the code that is happening. > I assume you are using the default line discipline N_TTY. > > Look at what is passed to drivers/char/n_tty.c:n_tty_receive_buf() > If all the data gets that far, then there is some issue > with the line discipline or something further downstream. > If not, then the problem is with the tty buffering (assuming > you are correct that all data gets to the tty buffering code > followed by a tty_flip_buffer_push call). I am not sure actually. I just open /dev/ttyn0 and /dev/ttyn1 and write to one, and read from the other. I didn't even know about the line diciplines actually. How do I tell which one I am using? I have confirmed that all the data is being passed to tty_insert_flip_string() in jsm_input(). -- 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/
