linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Breno Leitao <leitao@linux.vnet.ibm.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Very strange data loss with jsm driver
Date: Tue, 2 Aug 2011 10:22:25 -0400	[thread overview]
Message-ID: <20110802142225.GO8562@caffeine.csclub.uwaterloo.ca> (raw)
In-Reply-To: <4E380710.1010204@linux.vnet.ibm.com>

On Tue, Aug 02, 2011 at 11:17:52AM -0300, Breno Leitao wrote:
> Well, I finally tested it over here, and what I found is:
> 
> If the line has a \r among the first 16 bytes, then the information
> is TXed immediately. If there is no \r in the first 16 bytes, then the
> information seems to be buffered.

Where in the driver is this happening?

> So, it seems that that the patch should ask the driver to TX the
> information when we receive a \r or when the buffer is full. Does it
> make sense to you ?

Not sure.  I just wonder why the data is disappearing rather than getting
buffered somewhere.  Clearly the other serial drivers are doing that
successfully.

I don't even know why the driver should care about the contents at all.
Just send data when it is ready.

-- 
Len Sorensen

  reply	other threads:[~2011-08-02 14:22 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
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 [this message]
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=20110802142225.GO8562@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).