unusual_devs.h, kernel 2.6.15.6
Subsystems (2)
PATCH 1/1 unusual_devs.h, kernel 2.6.15.6
This patch adds an UNUSUAL_DEV entry which prevents a particular usb drive from flooding the console with useless SCSI messages. It is patterned after similar ones for other manufacturers. I also took the opportunity to correct the order of entries, manufacturer 0x0451 was out of order.
I thank David Härdeman for help with this one.
Denis Sunko
drivers/usb/storage/unusual_devs.h +16 -7
@@ -127,6 +127,14 @@ US_SC_SCSI, US_PR_DPCM_USB, NULL, 0 ),#endif +/* Patch submitted by Daniel Drake <[email protected]> +* Device reports nonsense bInterfaceProtocol 6 when connected over USB2 */ +UNUSUAL_DEV (0x0451 ,0x5416 ,0x0100 ,0x0100 , +"Neuros Audio" , +"USB 2.0 HD 2.5" , +US_SC_DEVICE ,US_PR_BULK ,NULL , + US_FL_NEED_OVERRIDE ), +/* * Pete Zaitcev <[email protected]>, from Patrick C. F. Ernzer, bz#162559. * The key does not actually break, but it returns zero sense which
@@ -137,13 +145,14 @@ "USB Mass Storage Device", US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_NOT_LOCKABLE ), -/* Patch submitted by Daniel Drake <[email protected]> -* Device reports nonsense bInterfaceProtocol 6 when connected over USB2 */ -UNUSUAL_DEV (0x0451 ,0x5416 ,0x0100 ,0x0100 , -"Neuros Audio" , -"USB 2.0 HD 2.5" , -US_SC_DEVICE ,US_PR_BULK ,NULL , -US_FL_NEED_OVERRIDE ), +/* +* Denis Sunko <[email protected]> +* The key makes the SCSI stack print confusing (but harmless) messages +*/ +UNUSUAL_DEV (0x0457 ,0x0151 ,0x0100 ,0x0100 , +"Silicon Integrated Systems Corp." , +"Drive UT_USB20" , +US_SC_DEVICE ,US_PR_DEVICE ,NULL ,US_FL_NOT_LOCKABLE ),/* Patch submitted by Philipp Friedrich <[email protected]> */ UNUSUAL_DEV( 0x0482, 0x0100, 0x0100, 0x0100,
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Quoted 7 lines · Denis Sunko
This patch adds an
UNUSUAL_DEVentry which prevents a particular usb drive from flooding the console with useless SCSI messages. It is patterned after similar ones for other manufacturers. I also took the opportunity to correct the order of entries, manufacturer0x0451was out of order.I thank David H?rdeman for help with this one.
This has already been submitted, sorry, someone beat you :)
thanks,
greg k-h