From: Wu Fengguang <fengguang.wu@intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: cannot reliably detect USB device
Date: Thu, 25 Dec 2008 18:47:53 +0800 [thread overview]
Message-ID: <20081225104753.GB15733@localhost> (raw)
In-Reply-To: <20081223043714.GH1928@kroah.com>
On Tue, Dec 23, 2008 at 06:37:14AM +0200, Greg KH wrote:
> On Mon, Dec 22, 2008 at 04:42:49PM +0800, Wu Fengguang wrote:
> > Hi Greg,
> >
> > I have a pl2303 USB-RS232 converter that cannot be reliably detected.
>
> Faulty hardware? Flaky cables? Bad connections? If this is
> reproducable for the same device on multiple machines, I'd just go buy a
> new device :)
I decided to give it a last try before planning a replacement - then I
find that /dev/ttyUSB0 could be created if I enlarge the retry times.
It could take 10 seconds to get a valid response. It must go crazy.
Thanks,
Fengguang
next prev parent reply other threads:[~2008-12-25 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081222084249.GA5845@localhost>
2008-12-23 4:37 ` cannot reliably detect USB device Greg KH
2008-12-25 10:47 ` Wu Fengguang [this message]
2009-01-01 17:44 ` Andreas Mohr
2009-01-03 22:07 ` Kay Sievers
2009-01-05 9:03 ` Wu Fengguang
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=20081225104753.GB15733@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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