Looking at this, I'm more tempted to remove the test for bType in the IRQ -- this isn't the first device I've seen broken like this. It's using a UFI-style CBI interrupt for a non-UFI device. This is, apparently, one of many spec violations that windows silently ignores.
Stephen, what happens if you just remove the check (search the code for the
line that shows "CBI IRQ data showed reserved bType")?
Matt
On Wed, Oct 22, 2003 at 11:18:07AM -0700, Stephen Hemminger wrote:
> On Wed, 22 Oct 2003 10:37:28 -0700
> Matthew Dharm <[EMAIL PROTECTED]> wrote:
>
> > usb-storage isn't very picky about the response at all... what exactly was
> > happening without the patch?
> >
>
> usb-storage: *** thread awakened.
> usb-storage: Command INQUIRY (6 bytes)
> usb-storage: 12 00 00 00 24 00
> usb-storage: usb_stor_ctrl_transfer: rq=00 rqtype=21 value=0000 index=00 len=12
> usb-storage: Status code 0; transferred 12/12
> usb-storage: -- transfer complete
> usb-storage: Call to usb_stor_ctrl_transfer() returned 0
> usb-storage: usb_stor_bulk_transfer_buf: xfer 36 bytes
> usb-storage: Status code 0; transferred 36/36
> usb-storage: -- transfer complete
> usb-storage: CBI data stage result is 0x0
> usb-storage: usb_stor_intr_transfer: xfer 2 bytes
> usb-storage: Status code 0; transferred 2/2
> usb-storage: -- transfer complete
> usb-storage: Got interrupt data (0x28, 0x0)
> usb-storage: CBI IRQ data showed reserved bType 40
> usb-storage: -- transport indicates error, resetting
> usb-storage: usb_stor_CB_reset called
> usb-storage: usb_stor_control_msg: rq=00 rqtype=21 value=0000 index=00 len=12
> usb-storage: Soft reset failed: -32
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
E: You run this ship with Windows?! YOU IDIOT!
L: Give me a break, it came bundled with the computer!
-- ESR and Lan Solaris
User Friendly, 12/8/1998
pgp00000.pgp
Description: PGP signature
