Re: [BUG] 2.6.32 - Sddr-09 SM reader resets endlessly

[Andries E. Brouwer]

On Sat, Dec 05, 2009 at 12:55:40PM -0500, Alan Stern wrote:

> > [ 1259.709281] usb 3-1: new full speed USB device using ohci_hcd and address 4
> > [ 1259.867687] usb 3-1: New USB device found, idVendor=0781, idProduct=0200
> 
> Not shown explicitly, the bcdDevice value is 0208.
> 
> > [ 1259.874603] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> > [ 1259.881956] usb 3-1: Product: USB SSFDC
> > [ 1259.881958] usb 3-1: Manufacturer: SanDisk

> > [ 1266.830235] sddr09: could not read card info
> > [ 1266.847287] sddr09: could not read card info

> Skipping to the important part, where the sddr09 driver implements TEST 
> UNIT READY:
> 
> > ffff8801571e5240 2548283209 S Co:3:004:0 s 41 00 0000 0000 000c 12 = 00200000 00000000 00000000
> > ffff8801571e5240 2548536793 C Co:3:004:0 -32 12 >
> 
> That failure is responsible for the resets.
> 
> Andries, do you have any idea what's going on?  Evidently this device 
> doesn't accept the protocol used by the sddr09 driver.

Hi Alan,

Sorry, no - I have no memory and worked on these USB drivers
years ago. Forgot all details. Also my last sddr09 device broke
some time ago.

Looking at my old files I do not see the Vendor Id 0781, so maybe
this is a device I never encountered.
These old files also discuss some trickery with multi-lun devices
where the driver needed depends on the lun. This is not a reader
of multiple types of card?

Many of my SM readers worked with either sddr09 or sddr55.
Does the unusual devices section today say that such a device
needs sddr09?

Found a 2.6.31 source tree. Yes,

UNUSUAL_DEV(  0x0781, 0x0200, 0x0000, 0x9999,
                "Sandisk",
                "ImageMate SDDR-09",
                US_SC_SCSI, US_PR_EUSB_SDDR09, usb_stor_sddr09_init,
                0),

Is it known who added this? Is 0208 in the interval of known devices
for which sddr09 works?

Andries

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/