From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Breno Leitao <leitao@linux.vnet.ibm.com>
Subject: Re: Very strange data loss with jsm driver
Date: Fri, 29 Jul 2011 12:53:42 -0400 [thread overview]
Message-ID: <20110729165342.GB8566@caffeine.csclub.uwaterloo.ca> (raw)
In-Reply-To: <20110729172736.4b199d31@lxorguk.ukuu.org.uk>
On Fri, Jul 29, 2011 at 05:27:36PM +0100, Alan Cox wrote:
> > The trigger point appears to be lines of up to 14 bytes, followed by
> > a newline. With 15 bytes or more per line it seems to be OK.
> >
> > Anyone got a clue?
>
> FIFO size perhaps - and some kind of missed wakeup or tx handling bug ?
FIFO size is 64bytes, so that doesn't immediately sound related.
The thing I find weird is that it thinks everything was sent right away.
Also why should the newline have anything to do with it? If you send
100100 bytes should it matter where the newlines are unless the tty
layer or the driver is interpreting the newlines for some reason.
--
Len Sorensen
next prev parent reply other threads:[~2011-07-29 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 16:04 Very strange data loss with jsm driver Lennart Sorensen
2011-07-29 16:27 ` Alan Cox
2011-07-29 16:53 ` Lennart Sorensen [this message]
2011-07-29 18:06 ` Lennart Sorensen
2011-07-29 18:14 ` Alan Cox
2011-07-29 18:13 ` Lennart Sorensen
2011-08-02 14:17 ` Breno Leitao
2011-08-02 14:22 ` Lennart Sorensen
2011-08-02 14:23 ` Lennart Sorensen
2011-08-02 14:49 ` Breno Leitao
2011-08-02 14:52 ` Lennart Sorensen
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=20110729165342.GB8566@caffeine.csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=leitao@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).