Changes between Version 9 and Version 10 of SAT-with-UAS-Linux


Ignore:
Timestamp:
08/09/2019 01:31:04 PM (10 days ago)
Author:
Nathan Stratton Treadway
Comment:

tweak /proc/scsi/usb-storage paragraphs

Legend:

Unmodified
Added
Removed
Modified
  • SAT-with-UAS-Linux

    v9 v10  
    236236[=#proc_scsi_usb-storage] Using /proc/scsi/usb-storage/[HOSTNUMBER} to display active flag bits:
    237237
    238 * If a device is attached to the usb-storage driver, there will be an associated file under `/proc/scsi/usb-storage` which will display information related to that particular device driver instance's internal state -- including a list of the active flag bits.
    239 
    240    For example, after setting the quirks for this particular USB ID to ":u" and pugging in the device, the kernel detected it with a `scsi host4: usb-storage 2-1:1.0` message, and the /proc info file showed:
     238* If a device is attached to the usb-storage driver, there will be an associated file under `/proc/scsi/usb-storage` which will display information related to that particular device driver instance's internal state... and in particular the Quirks: line displays a list of the active flag bits for this device -- whether set by a manual override, an entry in the  unusual_devs.h or unusual_uas.h files, or by dynamically by logic coded within the driver.
     239
     240   For example, after setting the quirks string for this particular USB ID to ":u" and pugging in the device, the kernel detected it with a `scsi host4: usb-storage 2-1:1.0` message, and the /proc info file showed:
    241241   {{{
    242242============
     
    251251============
    252252   }}}
    253 
    254 * Unfortunately the uas driver does not create an equivalent `/proc/scsi/uas/*` file... so when a device does get attached to that driver, one can't use this method to determine if it has (for example) the NO_ATA_1X flag set....
    255 
     253   (thus confirming the quirks string had taken effect).
     254
     255* Unfortunately the uas driver does not create an equivalent `/proc/scsi/uas/*` file, so this method doesn't help when you are attempting to determine (for example) whether or not the NO_ATA_1X flag is set on a uas device....
     256