From: Greg KH <greg@kroah.com>
To: Linux-Kernel ML <linux-kernel@vger.kernel.org>,
Linux-USB-Users <linux-usb-users@lists.sourceforge.net>
Subject: Re: USB broken in 2.5.4[56]
Date: Wed, 6 Nov 2002 10:30:46 -0800 [thread overview]
Message-ID: <20021106183046.GA23770@kroah.com> (raw)
In-Reply-To: <20021106132022.GA2101@home.ldb.ods.org>
On Wed, Nov 06, 2002 at 02:20:23PM +0100, Luca Barbieri wrote:
> In 2.5.4[56] USB has the following problems:
> - Kernel and lsusb unable to get strings (empty in driverfs and lsusb
> gets EPIPE from usbdevfs)
> - bAlternateSetting == 0 on interface 1 of my SpeedTouch USB (this
> prevents loading the firmware to it)
>
> Reverting all the USB changes in 2.5.45 fixes the problems.
_All_ the changes? Hm, that was a lot :(
Anyway, which USB drivers are you using? That might help us narrow this
down a bit.
thanks,
greg k-h
next prev parent reply other threads:[~2002-11-06 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 13:20 USB broken in 2.5.4[56] Luca Barbieri
2002-11-06 18:30 ` Greg KH [this message]
2002-11-07 20:43 ` Luca Barbieri
2002-11-08 7:43 ` Greg KH
2002-11-08 7:50 ` Greg KH
2002-11-08 16:06 ` Kees Bakker
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=20021106183046.GA23770@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox