On Tue, Jul 19, 2005 at 08:07:38PM +0300, Mihnea-Costin Grigore wrote: > > Hello, > > I have recently purchased a card-reader/floppy combo produced by > Mitsumi, and found out that under Linux it exhibits the behaviour > described at http://bugme.osdl.org/show_bug.cgi?id=3223. > Accordingly, I wrote a new entry in the unusual_devs.h file and now > the device is working flawlessly. The (really short) patch follows: > > =====[usb-storage-patch]===== > --- drivers/usb/storage/unusual_devs.h.old 2005-07-19 > 18:36:17.000000000 +0300 > +++ drivers/usb/storage/unusual_devs.h 2005-07-19 19:27:49.000000000 > +0300 > @@ -79,6 +79,13 @@ UNUSUAL_DEV( 0x03f0, 0x0307, 0x0001, 0x > US_SC_8070, US_PR_SCM_ATAPI, init_usbat, 0), > #endif > > +/* Patch submitted by Mihnea-Costin Grigore <[EMAIL PROTECTED]> */ > +UNUSUAL_DEV( 0x040d, 0x6205, 0x0000, 0xFFFF, > + "VIA Technologies Inc.", > + "USB 2.0 Card Reader", > + US_SC_DEVICE, US_PR_DEVICE, NULL, > + US_FL_IGNORE_RESIDUE ), > + > /* Deduced by Jonathan Woithe <[EMAIL PROTECTED]> > * Entry needed for flags: US_FL_FIX_INQUIRY because initial inquiry > message > * always fails and confuses drive. > =====[end usb-storage-patch]===== > > As you can see, I was unable to deduce the bcdDeviceMin/Max values so > I entered the whole range there (previously tried with 0x0100 and 0x0001 > like other entries in the file, but it didn't work). Maybe you can tell me > where that value is found (and how to convert it to hex) from the > following output (is it the bcdDevice 0.03 line?): >
Yes it is... your bcdDevice number is 0x0003. Care to redo the patch? -- Phil Dibowitz [EMAIL PROTECTED] Freeware and Technical Pages Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759
signature.asc
Description: Digital signature
