> Ah.  I had overlooked another difference in the lsusb output.  If you 
> compare the lines for bDeviceClass, you'll see that the 
> hotplugged-version says "Vendor Specific Class".  That means you'll 
> this additional patch to make it work with usb-storage.
> 
> Alan Stern

Great shot!
This patch fix the problem so now the device is properly initialized and 
a file (sdb in this case) is added to the /dev directory.
Do you need the usb-debug output for any purpose?
Thank you again for the time you spent solving my problem,
best regards
Fabio

PS:
 +/* Reported by Fabio Venturi <[EMAIL PROTECTED]>

Oh man!!! My name is in Linux!!!  :)

> 
> 
> Index: 2.6.24/drivers/usb/storage/unusual_devs.h
> ===================================================================
> --- 2.6.24.orig/drivers/usb/storage/unusual_devs.h
> +++ 2.6.24/drivers/usb/storage/unusual_devs.h
> @@ -1469,6 +1469,15 @@ UNUSUAL_DEV(  0x1019, 0x0c55, 0x0000, 0x
>               US_SC_DEVICE, US_PR_DEVICE, usb_stor_ucr61s2b_init,
>               0 ),
>  
> +/* Reported by Fabio Venturi <[EMAIL PROTECTED]>
> + * The device reports a vendor-specific bDeviceClass.
> + */
> +UNUSUAL_DEV(  0x10d6, 0x2200, 0x0100, 0x0100,
> +             "Actions Semiconductor",
> +             "Mtp device",
> +             US_SC_DEVICE, US_PR_DEVICE, NULL,
> +             0),
> +
>  /* Reported by Kevin Lloyd <[EMAIL PROTECTED]>
>   * Entry is needed for the initializer function override,
>   * which instructs the device to load as a modem
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to