1. 12 9月, 2014 1 次提交
    • M
      storage: Add single-LUN quirk for Jaz USB Adapter · c66f1c62
      Mark 提交于
      The Iomega Jaz USB Adapter is a SCSI-USB converter cable. The hardware
      seems to be identical to e.g. the Microtech XpressSCSI, using a Shuttle/
      SCM chip set. However its firmware restricts it to only work with Jaz
      drives.
      
      On connecting the cable a message like this appears four times in the log:
       reset full speed USB device number 4 using uhci_hcd
      
      That's non-fatal but the US_FL_SINGLE_LUN quirk fixes it.
      Signed-off-by: NMark Knibbs <markk@clara.co.uk>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c66f1c62
  2. 26 8月, 2014 1 次提交
    • M
      USB: storage: add quirk for Newer Technology uSCSI SCSI-USB converter · a7e69ddb
      Mark 提交于
      The uSCSI from Newer Technology is a SCSI-USB converter with USB ID 06ca:2003.
      Like several other SCSI-USB products, it's a Shuttle Technology OEM device.
      Without a suitable entry in unusual-devs.h, the converter can only access the
      (single) device with SCSI ID 0. Copying the entry for device 04e6:0002 allows
      it to work with devices with other SCSI IDs too.
      
      There are currently six entries for Shuttle-developed SCSI-USB devices in
      unusual-devs.h (grep for euscsi):
        04e6:0002  Shuttle eUSCSI Bridge    USB_SC_DEVICE, USB_PR_DEVICE
        04e6:000b  Shuttle eUSCSI Bridge    USB_SC_SCSI, USB_PR_BULK
        04e6:000c  Shuttle eUSCSI Bridge    USB_SC_SCSI, USB_PR_BULK
        050d:0115  Belkin USB SCSI Adaptor  USB_SC_SCSI, USB_PR_BULK
        07af:0004  Microtech USB-SCSI-DB25  USB_SC_DEVICE, USB_PR_DEVICE
        07af:0005  Microtech USB-SCSI-HD50  USB_SC_DEVICE, USB_PR_DEVICE
      
      lsusb -v output for the uSCSI lists
        bInterfaceSubClass      6 SCSI
        bInterfaceProtocol     80 Bulk (Zip)
      
      This patch adds an entry for the uSCSI to unusual_devs.h.
      Signed-off-by: NMark Knibbs <markk@clara.co.uk>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      a7e69ddb
  3. 01 7月, 2014 1 次提交
  4. 04 5月, 2014 2 次提交
  5. 05 3月, 2014 1 次提交
  6. 05 2月, 2014 1 次提交
  7. 04 1月, 2014 1 次提交
  8. 17 10月, 2013 1 次提交
  9. 23 7月, 2013 1 次提交
  10. 16 3月, 2013 1 次提交
  11. 07 3月, 2013 2 次提交
    • B
      USB: storage: fix Huawei mode switching regression · ab4b7164
      Bjørn Mork 提交于
      This reverts commit 200e0d99 ("USB: storage: optimize to match the
      Huawei USB storage devices and support new switch command" and the
      followup bugfix commit cd060956 ("USB: storage: properly handle
      the endian issues of idProduct").
      
      The commit effectively added a large number of Huawei devices to
      the deprecated usb-storage mode switching logic.  Many of these
      devices have been in use and supported by the userspace
      usb_modeswitch utility for years.  Forcing the switching inside
      the kernel causes a number of regressions as a result of ignoring
      existing onfigurations, and also completely takes away the ability
      to configure mode switching per device/system/user.
      
      Known regressions caused by this:
       - Some of the devices support multiple modes, using different
        switching commands.  There are existing configurations taking
        advantage of this.
      
       - There is a real use case for disabling mode switching and
        instead mounting the exposed storage device. This becomes
        impossible with switching logic inside the usb-storage driver.
      
       - At least on device fail as a result of the usb-storage switching
        command, becoming completely unswitchable. This is possibly a
        firmware bug, but still a regression because the device work as
        expected using usb_modeswitch defaults.
      
      In-kernel mode switching was deprecated years ago with the
      development of the more user friendly userspace alternatives. The
      existing list of devices in usb-storage was only kept to prevent
      breaking already working systems.  The long term plan is to remove
      the list, not to add to it. Ref:
      http://permalink.gmane.org/gmane.linux.usb.general/28543
      
      Cc: <fangxiaozhi@huawei.com>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NBjørn Mork <bjorn@mork.no>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ab4b7164
    • B
  12. 05 2月, 2013 1 次提交
  13. 25 10月, 2012 1 次提交
  14. 06 9月, 2012 1 次提交
  15. 20 7月, 2012 1 次提交
  16. 17 7月, 2012 1 次提交
  17. 23 6月, 2012 1 次提交
  18. 14 6月, 2012 1 次提交
    • H
      usb-storage: Add 090c:1000 to unusal-devs · afff07e6
      Hans de Goede 提交于
      This device gives a bogus answer to get_capacity(16):
      [ 8628.278614] scsi 8:0:0:0: Direct-Access     USB 2.0  USB Flash Drive  1100 PQ: 0 ANSI: 4
      [ 8628.279452] sd 8:0:0:0: Attached scsi generic sg4 type 0
      [ 8628.280338] sd 8:0:0:0: [sdd] 35747322042253313 512-byte logical blocks: (18.3 EB/15.8 EiB)
      
      So set the quirk flag to avoid using get_capacity(16) with it:
      [11731.386014] usb-storage 2-1.6:1.0: Quirks match for vid 090c pid 1000: 80000
      [11731.386075] scsi9 : usb-storage 2-1.6:1.0
      [11731.386172] usbcore: registered new interface driver usb-storage
      [11731.386175] USB Mass Storage support registered.
      [11732.387394] scsi 9:0:0:0: Direct-Access     USB 2.0  USB Flash Drive  1100 PQ: 0 ANSI: 4
      [11732.388462] sd 9:0:0:0: Attached scsi generic sg3 type 0
      [11732.389432] sd 9:0:0:0: [sdc] 7975296 512-byte logical blocks: (4.08 GB/3.80 GiB)
      
      Which makes the capacity look a lot more sane :)
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Tested-by: NSimon Raffeiner <sturmflut@lieberbiber.de>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      afff07e6
  19. 10 5月, 2012 1 次提交
  20. 28 3月, 2012 1 次提交
  21. 02 1月, 2012 1 次提交
  22. 27 11月, 2011 1 次提交
  23. 09 8月, 2011 1 次提交
  24. 08 6月, 2011 1 次提交
    • A
      usb-storage: redo incorrect reads · 21c13a4f
      Alan Stern 提交于
      Some USB mass-storage devices have bugs that cause them not to handle
      the first READ(10) command they receive correctly.  The Corsair
      Padlock v2 returns completely bogus data for its first read (possibly
      it returns the data in encrypted form even though the device is
      supposed to be unlocked).  The Feiya SD/SDHC card reader fails to
      complete the first READ(10) command after it is plugged in or after a
      new card is inserted, returning a status code that indicates it thinks
      the command was invalid, which prevents the kernel from retrying the
      read.
      
      Since the first read of a new device or a new medium is for the
      partition sector, the kernel is unable to retrieve the device's
      partition table.  Users have to manually issue an "hdparm -z" or
      "blockdev --rereadpt" command before they can access the device.
      
      This patch (as1470) works around the problem.  It adds a new quirk
      flag, US_FL_INVALID_READ10, indicating that the first READ(10) should
      always be retried immediately, as should any failing READ(10) commands
      (provided the preceding READ(10) command succeeded, to avoid getting
      stuck in a loop).  The patch also adds appropriate unusual_devs
      entries containing the new flag.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Tested-by: NSven Geggus <sven-usbst@geggus.net>
      Tested-by: NPaul Hartman <paul.hartman+linux@gmail.com>
      CC: Matthew Dharm <mdharm-usb@one-eyed-alien.net>
      CC: <stable@kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      21c13a4f
  25. 04 2月, 2011 2 次提交
  26. 23 1月, 2011 2 次提交
  27. 17 12月, 2010 1 次提交
  28. 23 10月, 2010 3 次提交
  29. 21 5月, 2010 2 次提交
  30. 19 3月, 2010 2 次提交
  31. 03 3月, 2010 1 次提交
  32. 17 2月, 2010 1 次提交