diff options
author | Stephen M. Cameron <scameron@beardog.cce.hp.com> | 2011-11-16 09:21:49 +0100 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2011-11-16 09:21:49 +0100 |
commit | 0007a4c90a11a5371c8b3f80b220fa402a399189 (patch) | |
tree | 3fb4a0158f87f539b2415fad35e958d1d1259910 /block | |
parent | 7035b5df3c071ccaf2f1694b96bd8958b0eb37ca (diff) | |
download | linux-3.10-0007a4c90a11a5371c8b3f80b220fa402a399189.tar.gz linux-3.10-0007a4c90a11a5371c8b3f80b220fa402a399189.tar.bz2 linux-3.10-0007a4c90a11a5371c8b3f80b220fa402a399189.zip |
cciss: auto engage SCSI mid layer at driver load time
A long time ago, probably in 2002, one of the distros, or maybe more than
one, loaded block drivers prior to loading the SCSI mid layer. This meant
that the cciss driver, being a block driver, could not engage the SCSI mid
layer at init time without panicking, and relied on being poked by a
userland program after the system was up (and the SCSI mid layer was
therefore present) to engage the SCSI mid layer.
This is no longer the case, and cciss can safely rely on the SCSI mid
layer being present at init time and engage the SCSI mid layer straight
away. This means that users will see their tape drives and medium
changers at driver load time without need for a script in /etc/rc.d that
does this:
for x in /proc/driver/cciss/cciss*
do
echo "engage scsi" > $x
done
However, if no tape drives or medium changers are detected, the SCSI mid
layer will not be engaged. If a tape drive or medium change is later
hot-added to the system it will then be necessary to use the above script
or similar for the device(s) to be acceesible.
Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions