Lines Matching refs:SCSI

91 SCSI tape drive and medium changer support
94 SCSI sequential access devices and medium changer devices are supported and 
97 You must enable "SCSI tape drive support for Smart Array 5xxx" and 
98 "SCSI support" in your kernel configuration to be able to use SCSI
101 Additionally, note that the driver will engage the SCSI core at init
103 also be directed to dynamically engage the SCSI core via the /proc filesystem
114 Once the SCSI core is engaged by the driver, it cannot be disengaged 
118 detected, the SCSI core will not be engaged by the action of the above
121 Hot plug support for SCSI tape drives
124 Hot plugging of SCSI tape drives is supported, with some caveats.
125 The cciss driver must be informed that changes to the SCSI bus
132 physical SCSI buses and/or fibre channel arbitrated loop and the
136 lun used to address the device.  It then notifies the SCSI mid layer
144 as SCSI devices to the SCSI mid layer by the cciss driver.  Specifically, 
145 physical SCSI disk drives are NOT presented to the SCSI mid layer.  The 
146 physical SCSI disk drives are controlled directly by the array controller 
148 access these devices too, as if the array controller were merely a SCSI 
149 controller in the same way that we are allowing it to access SCSI tape drives.
151 SCSI error handling for tape drives and medium changers
154 The linux SCSI mid layer provides an error handling protocol which
155 kicks into gear whenever a SCSI command fails to complete within a
160 If that doesn't work, the SCSI bus is reset.  If that doesn't work
162 driver as well as a SCSI driver and only the tape drives and medium
163 changers are presented to the SCSI mid layer, and unlike more 
164 straightforward SCSI drivers, disk i/o continues through the block
165 side during the SCSI error recovery process, the cciss driver only