From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Paul Fulghum <paulkf@microgate.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange problem with tty layer
Date: Fri, 26 Jan 2007 09:56:08 -0500 [thread overview]
Message-ID: <20070126145608.GK7582@csclub.uwaterloo.ca> (raw)
In-Reply-To: <45BA1556.8080808@microgate.com>
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
next prev parent reply other threads:[~2007-01-26 14:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 20:40 Lennart Sorensen
2007-01-24 21:20 ` Paul Fulghum
2007-01-24 21:48 ` Lennart Sorensen
2007-01-25 15:16 ` Lennart Sorensen
2007-01-26 14:20 ` Lennart Sorensen
2007-01-26 14:51 ` Paul Fulghum
2007-01-26 14:56 ` Lennart Sorensen [this message]
2007-01-26 15:06 ` Paul Fulghum
2007-01-26 16:08 ` Lennart Sorensen
2007-01-29 19:27 ` Lennart Sorensen
2007-02-17 16:09 ` Lennart Sorensen
2007-01-24 21:19 Kilau, Scott
2007-01-24 21:34 ` Lennart Sorensen
2007-01-25 14:31 ` Russell King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070126145608.GK7582@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®