Messages in this thread |  | | Date | Wed, 4 Sep 2002 16:10:42 -0700 | From | Matthew Dharm <> | Subject | Re: [linux-usb-devel] Feiya 5-in-1 Card Reader |
| |
Nope, not confused.
I'm trying to find out why Windows doesn't choke on the strange READ_CAPACITY value. My guess is that there is code somewhere to universally fixup READ_CAPACITY, and I'd like to know what the magic formula is.
The MODE_SENSE bit is fine by me. But it's a SCSI change, so I'm not the person to ask. The fix to sddr09.c for that seems reasonable, but you put it all together and I haven't had time to split it up. Of course, I fully expect the changes to MODE_SENSE in the SCSI layer to break other USB devices, but there is only one way to find out....
Matt
On Thu, Sep 05, 2002 at 12:56:00AM +0200, Andries.Brouwer@cwi.nl wrote: > >> Matt, is it ok with you for me to add this patch to the tree? > > > I'd like to hold off a few more days while I try to find out what the > > 'secret sauce' that the other OSes use for a device like this. > > Hmm. You do not confuse two situations, do you? > In the past few days I made two devices work. > > One was a Feiya 5-in-1 CF / SM / SD card reader > (Vendor Id: 090c, Product Id: 1132, Revision 1.00). > It returned a capacity that is one too large, and becomes > very unhappy if one tries to read a sector past the end. > So, a flag was needed to tell that the result of READ CAPACITY > needs fixing. > > The other was a Travelmate CF / SM / SD card reader > (Vendor Id: 3538, Product Id: 0001, Revision 2.05). > It became unhappy when MODE_SENSE asked for too much data. > A patch on sd.c solved this. > > Andries
-- Matthew Dharm Home: mdharm-usb@one-eyed-alien.net Maintainer, Linux USB Mass Storage Driver
It's not that hard. No matter what the problem is, tell the customer to reinstall Windows. -- Nurse User Friendly, 3/22/1998 [unhandled content-type:application/pgp-signature] |  |