Okay, it looks like it's stuffing some extra status data in the interrupt data.
I'm low on time right now... can you remind me next week to look at this?
What you basically need to do is edit linux/drivers/usb/storage/transport.c
in CBI_irq and comment out the test against the first byte of the interrupt
data.
Matt
On Thu, Nov 29, 2001 at 10:52:42AM +0800, Stefan van der Eijk wrote:
> Matt,
>
> >Well, it's violating the specification alright. It's returning bogus
> >command-completion data.
> >
> hmmm... great.
>
> >Did this device come with it's own drivers? Or does it use the built-in
> >drivers under windows?
> >
> It's got it's own drivers.
>
> >Feel like hacking the source code to try to make it work?
> >
> Sure, I'll do what I can. I must warn you that I'm not a programmer...
> What I can do is help test. Or perhaps give you (root-) access to one of
> my boxes, with the clie connected to it.
>
> Here's the output of usbsniffer on my windows box (snoopy.log.bz2).
>
> Stefan
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
A: The most ironic oxymoron wins ...
DP: "Microsoft Works"
A: Uh, okay, you win.
-- A.J. & Dust Puppy
User Friendly, 1/18/1998
msg01694/pgp00000.pgp
Description: PGP signature
