Hi -
Sorry to add to the Casio-induced headache, but...
In february I sent in a patch to split the Casio QV entry in
unusual_devs.h into 2 entries, the first of which overrode both the
protocol and the subclass to work around what I assume are Casio bugs.
(Originally there was a single entry with the overrides, but later
Casios didn't need them and they were removed; I just reverted that
change for a certain range of cameras.) Now I find that the entry was
again "fixed" to remove the subclass override (patch as190); this again
breaks compatibility with the QV2000UX (device ID 0x9009). To remedy
this and try to avoid it happening a 3rd time, I offer the following
patch which gives the QV2000UX its very own entry.
Dan Scholnik
--- drivers/usb/storage/unusual_devs.h.orig 2004-05-15 13:08:53.000000000 -0400
+++ drivers/usb/storage/unusual_devs.h 2004-05-31 17:27:34.313458368 -0400
@@ -625,12 +625,19 @@
* bInterfaceProtocol=0x00 (US_PR_CBI) while others have 0x01 (US_PR_CB).
* So don't remove the US_PR_CB override!
*/
-UNUSUAL_DEV( 0x07cf, 0x1001, 0x1000, 0x9009,
+UNUSUAL_DEV( 0x07cf, 0x1001, 0x1000, 0x9008,
"Casio",
"QV DigitalCamera",
US_SC_DEVICE, US_PR_CB, NULL,
US_FL_FIX_INQUIRY ),
+/* The Casio QV2000UX needs the SubClass override, please don't remove */
+UNUSUAL_DEV( 0x07cf, 0x1001, 0x9009, 0x9009,
+ "Casio",
+ "QV DigitalCamera",
+ US_SC_8070, US_PR_CB, NULL,
+ US_FL_FIX_INQUIRY ),
+
/* Later Casio cameras apparently tell the truth */
UNUSUAL_DEV( 0x07cf, 0x1001, 0x9010, 0x9999,
"Casio",
