public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	Oleksiy <Oleksiy@kharkiv.com.ua>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: pl2303/usb-serial driver problem in 2.4.27-pre6
Date: Fri, 29 Oct 2004 20:49:20 -0700	[thread overview]
Message-ID: <20041030034920.GA1501@kroah.com> (raw)
In-Reply-To: <1098908206.2856.17.camel@deimos.microgate.com>

On Wed, Oct 27, 2004 at 03:16:46PM -0500, Paul Fulghum wrote:
> On Sat, 2004-10-23 at 19:14, Paul Fulghum wrote:
> > This change fits the reported symptom (loss of receive data).
> > 
> > The change preserves line status errors
> > across multiple read interrupt callbacks until the error
> > can be applied to the contents of the next read bulk callback.
> > 
> > What looks wrong to me is that the line status error,
> > which should be associated with an individual character,
> > is applied to the entire contents of the next bulk read.
> > Wouldn't this potentially invalidate good data?
> > 
> > I'm not familiar with the operation of USB-serial converters,
> > so I don't know exactly how the flow of read interrupt and
> > read bulk callbacks are implemented to handle character errors.
> > 
> > If I was to guess, before the change, errors were lost
> > (overwritten by the next read interrupt callback)
> > so the mask was added to preserve the error.
> > But the error is applied to more data than it should,
> > causing loss of valid receive data.
> 
> USB CDC 1.1 does not specify how these error indications
> relate to subsequent bulk data packets. I could not find
> manufacturer info that helps. BSD drivers don't do
> error processing at all.
> 
> Here is a patch that applies the error only to the
> next receive byte instead of all bytes in the
> next read bulk packet.
> 
> Greg: Any comment?

Your patch looks sane, thanks.

> Oleksiy: Can you try this patch?

Let us know if this works or not.  If so, Paul, care to resend this for
2.6 also?

thanks,

greg k-h

  reply	other threads:[~2004-10-30 16:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11 11:22 pl2303/usb-serial driver problem in 2.4.27-pre6 Oleksiy
2004-10-11 11:36 ` Marcelo Tosatti
2004-10-12 14:34   ` Oleksiy
2004-10-12 17:48   ` Pete Zaitcev
2004-10-13 19:32     ` Alexander Wigen
2004-10-13 17:42       ` Greg KH
2004-10-14 14:06         ` Alexander Wigen
2004-10-14  7:50           ` Jan-Benedict Glaw
2004-10-12 17:10 ` Greg KH
2004-10-23 18:06   ` Marcelo Tosatti
2004-10-23 23:00     ` Paul Fulghum
2004-10-24  0:14       ` Paul Fulghum
2004-10-27 20:16         ` Paul Fulghum
2004-10-30  3:49           ` Greg KH [this message]
2004-10-30 15:36             ` Paul Fulghum
2004-10-30 23:52               ` Paul Fulghum

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=20041030034920.GA1501@kroah.com \
    --to=greg@kroah.com \
    --cc=Oleksiy@kharkiv.com.ua \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --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