From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "'Ian Leonard'" <ian@smallworld.cx>, <linux-kernel@vger.kernel.org>
Subject: RE: 2.4.30 - USB serial problem
Date: Fri, 27 May 2005 10:45:34 -0400 [thread overview]
Message-ID: <029101c562ca$bd095b30$294b82ce@stuartm> (raw)
In-Reply-To: <42960CCA.5020703@smallworld.cx>
From: linux-kernel-owner@vger.kernel.org
> 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.
[snip]
> 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.
That's a software flow control character, have you turned off software
flow control?
..Stu
next prev parent reply other threads:[~2005-05-27 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 17:52 2.4.30 - USB serial problem Ian Leonard
2005-05-27 14:45 ` Stuart MacDonald [this message]
[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='029101c562ca$bd095b30$294b82ce@stuartm' \
--to=stuartm@connecttech.com \
--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