On Sun, 26 Nov 2006, Greg Folkert wrote:

> Okay, I have tried before here, but have been unsuccessful in making
> this device work.
> 
> I have a Sandisk Sansa e250, I'd like to see it work like my other USB
> storage devices. When I plug it in, pmount and udevd and hal all do the
> right thing and it just works. Except my E250 just fails to work.

> # lsusb -v -s 001:006
> 
> Bus 001 Device 006: ID 0781:7420 SanDisk Corp.
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               2.00
>   bDeviceClass            0 (Defined at Interface level)
>   bDeviceSubClass         0
>   bDeviceProtocol         0
>   bMaxPacketSize0        64
>   idVendor           0x0781 SanDisk Corp.
>   idProduct          0x7420
>   bcdDevice            7.20
>   iManufacturer           1 SanDisk
>   iProduct                2 Sansa e250
>   iSerial                 3 00000000-00000000-5526b389-d921e405-00000000
>   bNumConfigurations      1
>   Configuration Descriptor:
>     bLength                 9
>     bDescriptorType         2
>     wTotalLength           39
>     bNumInterfaces          1
>     bConfigurationValue   128
>     iConfiguration          0
>     bmAttributes         0xc0
>       Self Powered
>     MaxPower                0mA
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           3
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass    255 Vendor Specific Subclass
>       bInterfaceProtocol    255 Vendor Specific Protocol

See those "Vendor Specific" thingies?  They indicate that the e250 doesn't
use a standard USB mass-storage protocol.  Consequently the usb-storage 
driver won't talk to it.

> Device Qualifier (for other device speed):
>   bLength                10
>   bDescriptorType         6
>   bcdUSB               2.00
>   bDeviceClass          255 Vendor Specific Class
>   bDeviceSubClass       255 Vendor Specific Subclass
>   bDeviceProtocol       255 Vendor Specific Protocol

Same here.

Now it's possible that the device really does use a standard protocol
instead of a vendor-specific protocol, in spite of what the descriptors
say.  If it does, there's a good chance the patch below will make it work.  
Try it and see.

Alan Stern


Index: usb-2.6/drivers/usb/storage/unusual_devs.h
===================================================================
--- usb-2.6.orig/drivers/usb/storage/unusual_devs.h
+++ usb-2.6/drivers/usb/storage/unusual_devs.h
@@ -885,6 +885,13 @@ UNUSUAL_DEV(  0x0781, 0x0200, 0x0000, 0x
                0),
 #endif
 
+/* Reported by Greg Folkert <[EMAIL PROTECTED]> */
+UNUSUAL_DEV(  0x0781, 0x7420, 0x0720, 0x0720,
+               "Sandisk",
+               "Sansa e250",
+               US_SC_SCSI, US_PR_BULK, NULL,
+               0),
+
 #ifdef CONFIG_USB_STORAGE_FREECOM
 UNUSUAL_DEV(  0x07ab, 0xfc01, 0x0000, 0x9999,
                "Freecom",


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to