PATCH: some additional unusual_devs-entries for usb-storage-driver,

Hanno Böck (hanno@gmx.de)
Mon, 21 Apr 2003 21:48:05 +0200


This patch against 2.5.68 adds support for some digital cameras.
Same patch is already applied to the 2.4-ac-series.
It is taken from the lycoris kernel-source.

Hanno Boeck

--- linux-2.5.68-old/drivers/usb/storage/unusual_devs.h 2003-04-15 14:05:09.000000000 +0200
+++ linux-2.5.68/drivers/usb/storage/unusual_devs.h 2003-04-21 21:19:53.000000000 +0200
@@ -236,6 +236,13 @@
US_SC_SCSI, US_PR_CB, NULL,
US_FL_SINGLE_LUN | US_FL_START_STOP | US_FL_MODE_XLATE ),

+/* This entry is needed because the device reports Sub=ff */
+UNUSUAL_DEV( 0x054c, 0x0010, 0x0106, 0x0432,
+ "Sony",
+ "DSC-F707/U10/U20",
+ US_SC_SCSI, US_PR_CB, NULL,
+ US_FL_SINGLE_LUN | US_FL_START_STOP | US_FL_MODE_XLATE ),
+
/* Reported by wim@geeks.nl */
UNUSUAL_DEV( 0x054c, 0x0025, 0x0100, 0x0100,
"Sony",
@@ -268,6 +275,12 @@
"PEG Mass Storage",
US_SC_8070, US_PR_CBI, NULL,
US_FL_FIX_INQUIRY ),
+
+UNUSUAL_DEV( 0x054c, 0x0058, 0x0000, 0x9999,
+ "Sony",
+ "PEG-N760C Mass Storage",
+ US_SC_8070, US_PR_CBI, NULL,
+ US_FL_FIX_INQUIRY ),

UNUSUAL_DEV( 0x057b, 0x0000, 0x0000, 0x0299,
"Y-E Data",
@@ -375,6 +388,12 @@
US_SC_SCSI, US_PR_BULK, NULL,
US_FL_FIX_INQUIRY | US_FL_MODE_XLATE),

+UNUSUAL_DEV( 0x0636, 0x0003, 0x0000, 0x9999,
+ "Vivitar",
+ "Vivicam 35Xx",
+ US_SC_SCSI, US_PR_BULK, NULL,
+ US_FL_START_STOP | US_FL_FIX_INQUIRY | US_FL_MODE_XLATE),
+
UNUSUAL_DEV( 0x0644, 0x0000, 0x0100, 0x0100,
"TEAC",
"Floppy Drive",
@@ -440,6 +459,12 @@
US_FL_SINGLE_LUN | US_FL_START_STOP ),
#endif

+UNUSUAL_DEV( 0x0784, 0x1688, 0x0000, 0x9999,
+ "Vivitar",
+ "Vivicam 36xx",
+ US_SC_SCSI, US_PR_BULK, NULL,
+ US_FL_START_STOP | US_FL_FIX_INQUIRY | US_FL_MODE_XLATE),
+
#ifdef CONFIG_USB_STORAGE_FREECOM
UNUSUAL_DEV( 0x07ab, 0xfc01, 0x0000, 0x9999,
"Freecom",
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/