From: Jan De Luyck <lkml@kcore.org>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
linux-usb-users@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [2.6.10-rc2] ehci_hcd causes oops after some use of usb harddisk
Date: Tue, 23 Nov 2004 21:38:32 +0100 [thread overview]
Message-ID: <200411232138.33454.lkml@kcore.org> (raw)
In-Reply-To: <200411231203.41184.david-b@pacbell.net>
On Tuesday 23 November 2004 21:03, David Brownell wrote:
> > lsusb -v for the specific device:
> > Bus 001 Device 002: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter
> > Device Descriptor:
> > bLength 18
> > bDescriptorType 1
> > bcdUSB 2.00
> > bDeviceClass 0 (Defined at Interface level)
> > bDeviceSubClass 0
> > bDeviceProtocol 0
> > bMaxPacketSize0 64
> > idVendor 0x05e3 Genesys Logic, Inc.
> > idProduct 0x0702 USB 2.0 IDE Adapter
>
> ... those GeneSys devices have been sufficiently problematic that I,
> for one, won't investigate bug reports involving them any more. The
> devices have several problems where they lock up when Linux does
> perfectly legal things. Avoid them.
Yeah... well, unfortunately, it's almost impossible to get your hands on a usb
enclosure, break the seals on the wrapping, test it, then go back nagging it
doesn't work at the vendor - while it does work in <insert certain os name
here>. While I do agree - and try to find linux-compatible devices whenever
possible - this isn't really helpful to the end-user imo...
I've got it working now, and it works great after the udelay(200);
modification.
Jan
--
Witch! Witch! They'll burn ya!
-- Hag, "Tomorrow is Yesterday", stardate unknown
prev parent reply other threads:[~2004-11-23 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 18:12 [2.6.10-rc2] ehci_hcd causes oops after some use of usb harddisk Jan De Luyck
2004-11-23 20:03 ` [linux-usb-devel] " David Brownell
2004-11-23 20:38 ` Jan De Luyck [this message]
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=200411232138.33454.lkml@kcore.org \
--to=lkml@kcore.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux-usb-users@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.