- usb-storage-unusual_devs-entries-for-iriver-t10-and-datafab-cfsm-reader.patch removed from -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The patch titled
     usb-storage: unusual_devs entries for iRiver T10 and Datafab CF+SM reader
has been removed from the -mm tree.  Its filename was
     usb-storage-unusual_devs-entries-for-iriver-t10-and-datafab-cfsm-reader.patch

This patch was dropped because it was merged into mainline or a subsystem tree

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: usb-storage: unusual_devs entries for iRiver T10 and Datafab CF+SM reader
From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>

This patch (as1115) adds unusual_devs entries with the IGNORE_RESIDE flag
for the iRiver T10 and the Simple Tech/Datafab CF+SM card reader. 
Apparently these devices provide reasonable residue values for READ and
WRITE operations, but not for others like INQUIRY or READ CAPACITY.

This fixes the iRiver T10 problem reported in Bugzilla #11125.

Signed-off-by: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
Cc: Greg KH <greg@xxxxxxxxx>
Cc: <stable@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---

 drivers/usb/storage/unusual_devs.h |   14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff -puN drivers/usb/storage/unusual_devs.h~usb-storage-unusual_devs-entries-for-iriver-t10-and-datafab-cfsm-reader drivers/usb/storage/unusual_devs.h
--- a/drivers/usb/storage/unusual_devs.h~usb-storage-unusual_devs-entries-for-iriver-t10-and-datafab-cfsm-reader
+++ a/drivers/usb/storage/unusual_devs.h
@@ -1185,6 +1185,13 @@ UNUSUAL_DEV(  0x07c4, 0xa400, 0x0000, 0x
 		US_SC_DEVICE, US_PR_DEVICE, NULL,
 		US_FL_FIX_INQUIRY ),
 
+/* Reported by Rauch Wolke <rauchwolke@xxxxxxx> */
+UNUSUAL_DEV(  0x07c4, 0xa4a5, 0x0000, 0xffff,
+		"Simple Tech/Datafab",
+		"CF+SM Reader",
+		US_SC_DEVICE, US_PR_DEVICE, NULL,
+		US_FL_IGNORE_RESIDUE ),
+
 /* Casio QV 2x00/3x00/4000/8000 digital still cameras are not conformant
  * to the USB storage specification in two ways:
  * - They tell us they are using transport protocol CBI. In reality they
@@ -1767,6 +1774,13 @@ UNUSUAL_DEV(  0x2770, 0x915d, 0x0010, 0x
 		US_SC_DEVICE, US_PR_DEVICE, NULL,
 		US_FL_FIX_CAPACITY ),
 
+/* Reported by Andrey Rahmatullin <wrar@xxxxxxxxxxxx> */
+UNUSUAL_DEV(  0x4102, 0x1020, 0x0100,  0x0100,
+		"iRiver",
+		"MP3 T10",
+		US_SC_DEVICE, US_PR_DEVICE, NULL,
+		US_FL_IGNORE_RESIDUE ),
+
 /*
  * David Härdeman <david@xxxxxxxx>
  * The key makes the SCSI stack print confusing (but harmless) messages
_

Patches currently in -mm which might be from stern@xxxxxxxxxxxxxxxxxxx are

linux-next.patch
usb-hubc-fix-build-with-config_pm=n.patch
unrevert-usb-dont-explicitly-reenable-root-hub-status-interrupts.patch

--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Newbies FAQ]     [Kernel Archive]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux