public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Leonard <ian@smallworld.cx>
To: linux-kernel@vger.kernel.org
Subject: 2.4.30 - USB serial problem
Date: Thu, 26 May 2005 18:52:10 +0100	[thread overview]
Message-ID: <42960CCA.5020703@smallworld.cx> (raw)

Greetings,

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.

It is something to do with usb serial. We are actually using the 
ftdi_sio module but a quick diff suggests it hasn't changed much. I am 
not 100% sure what is going on but we are sending out various short 
commands (11 bytes) to an external device. Most work just fine but one 
using one sequence seems to cause the driver to loop and continually 
send out the same command. The application keeps sending other commands 
but eventually the write () blocks and that's that.

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.

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.


I don't have the failing equipment with me here but will return to site 
next week. I would appreciate any words of wisdom on the problem.


-- 
Ian Leonard

Please ignore spelling and punctuation - I did.

             reply	other threads:[~2005-05-26 17:52 UTC|newest]

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

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=42960CCA.5020703@smallworld.cx \
    --to=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