public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Ian Leonard <ian@smallworld.cx>
Cc: zaitcev@redhat.com, linux-kernel@vger.kernel.org,
	Ian Abbott <abbotti@mev.co.uk>
Subject: Re: 2.4.30 - USB serial problem
Date: Tue, 31 May 2005 18:40:48 -0700	[thread overview]
Message-ID: <20050531184048.5ef9fd44.zaitcev@redhat.com> (raw)
In-Reply-To: <mailman.1117130162.21749.linux-kernel2news@redhat.com>

On Thu, 26 May 2005 18:52:10 +0100, Ian Leonard <ian@smallworld.cx> wrote:

> We recently upgraded from 2.4.24 to 2.4.28 and the problem described 
> below appeared. I have tested it on 2.4.30 and the fault still exists.
>[...]
> Examining the packet that caused the problem showed it was very similar 
> to the others but it contained 0x0a. This obviously stuck out as being a 
> candidate for some sort of translation problem.

The above looks almost too obvious but for this:

> I also built a 2.4.28 kernel with the ftdi_sio and usbserial code from 
> the 2.4.24 release. It also failed. This was a surprise and I am 
> wondering of I did it correctly.

Did you nail down a scenario which we can debug? Frankly it's not credible
that transplanted usbserial and ftsi_sio would fail to work. I know that
I changed quite a bit between 2.4.24 and 2.4.28, but your experiment
undoes that.

-- Pete

       reply	other threads:[~2005-06-01  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1117130162.21749.linux-kernel2news@redhat.com>
2005-06-01  1:40 ` Pete Zaitcev [this message]
2005-06-02  8:41   ` 2.4.30 - USB serial problem Ian Leonard
2005-06-07  8:28     ` Ian Leonard
2005-06-07  9:07       ` Ian Abbott
2005-05-26 17:52 Ian Leonard
2005-05-27 14:45 ` Stuart MacDonald

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=20050531184048.5ef9fd44.zaitcev@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=abbotti@mev.co.uk \
    --cc=ian@smallworld.cx \
    --cc=linux-kernel@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