1. 09 12月, 2013 1 次提交
  2. 14 6月, 2012 1 次提交
  3. 15 11月, 2011 1 次提交
    • A
      usb-storage: Accept 8020i-protocol commands longer than 12 bytes · 2f640bf4
      Alan Stern 提交于
      The 8020i protocol (also 8070i and QIC-157) uses 12-byte commands;
      shorter commands must be padded.  Simon Detheridge reports that his
      3-TB USB disk drive claims to use the 8020i protocol (which is
      normally meant for ATAPI devices like CD drives), and because of its
      large size, the disk drive requires the use of 16-byte commands.
      However the usb_stor_pad12_command() routine in usb-storage always
      sets the command length to 12, making the drive impossible to use.
      
      Since the SFF-8020i specification allows for 16-byte commands in
      future extensions, we may as well accept them.  This patch (as1490)
      changes usb_stor_pad12_command() to leave commands larger than 12
      bytes alone rather than truncating them.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Tested-by: NSimon Detheridge <simon@widgit.com>
      CC: Matthew Dharm <mdharm-usb@one-eyed-alien.net>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      2f640bf4
  4. 01 11月, 2011 1 次提交
  5. 25 3月, 2009 1 次提交
    • A
      usb-storage: prepare for subdriver separation · e6e244b6
      Alan Stern 提交于
      This patch (as1206) is the first step in converting usb-storage's
      subdrivers into separate modules.  It makes the following large-scale
      changes:
      
      	Remove a bunch of unnecessary #ifdef's from usb_usual.h.
      	Not truly necessary, but it does clean things up.
      
      	Move the USB device-ID table (which is duplicated between
      	libusual and usb-storage) into its own source file,
      	usual-tables.c, and arrange for this to be linked with
      	either libusual or usb-storage according to whether
      	USB_LIBUSUAL is configured.
      
      	Add to usual-tables.c a new usb_usual_ignore_device()
      	function to detect whether a particular device needs to be
      	managed by a subdriver and not by the standard handlers
      	in usb-storage.
      
      	Export a whole bunch of functions in usb-storage, renaming
      	some of them because their names don't already begin with
      	"usb_stor_".  These functions will be needed by the new
      	subdriver modules.
      
      	Split usb-storage's probe routine into two functions.
      	The subdrivers will call the probe1 routine, then fill in
      	their transport and protocol settings, and then call the
      	probe2 routine.
      
      	Take the default cases and error checking out of
      	get_transport() and get_protocol(), which run during
      	probe1, and instead put a check for invalid transport
      	or protocol values into the probe2 function.
      
      	Add a new probe routine to be used for standard devices,
      	i.e., those that don't need a subdriver.  This new routine
      	checks whether the device should be ignored (because it
      	should be handled by ub or by a subdriver), and if not,
      	calls the probe1 and probe2 functions.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      CC: Matthew Dharm <mdharm-usb@one-eyed-alien.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      e6e244b6
  6. 08 1月, 2009 1 次提交
  7. 22 7月, 2008 1 次提交
  8. 05 3月, 2008 1 次提交
  9. 22 2月, 2008 1 次提交
  10. 12 1月, 2008 1 次提交
  11. 23 10月, 2007 1 次提交
  12. 16 10月, 2007 1 次提交
    • J
      USB storage: sg chaining support · 1f6f31a0
      Jens Axboe 提交于
      [PATCH] USB storage: sg chaining support
      
      Modify usb_stor_access_xfer_buf() to take a pointer to an sg
      entry pointer, so we can keep track of that instead of passing
      around an integer index (which we can't use when dealing with
      multiple scatterlist arrays).
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      1f6f31a0
  13. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4