Commit e8166f0e authored by Phil Oester's avatar Phil Oester Committed by Linus Torvalds

[PATCH] doc: scsihosts parameter no longer exists

The scsihosts boot parameter was removed in 2.5.73, but references to it
still exist in docs.  Cleanup below.
Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
parent edafeee3
...@@ -1349,47 +1349,6 @@ This will cause devfsd to create (and destroy) symbolic links which ...@@ -1349,47 +1349,6 @@ This will cause devfsd to create (and destroy) symbolic links which
point to the kernel-supplied names. point to the kernel-supplied names.
SCSI Host Probing Issues
Devfs allows you to identify SCSI discs based in part on SCSI host
numbers. If you have only one SCSI host (card) in your computer, then
clearly it will be given host number 0. Life is not always that easy
is you have multiple SCSI hosts. Unfortunately, it can sometimes be
difficult to guess what the probing order of SCSI hosts is. You need
to know the probe order before you can use device names. To make this
easy, there is a kernel boot parameter called "scsihosts". This allows
you to specify the probe order for different types of SCSI hosts. The
syntax of this parameter is:
scsihosts=<name_1>:<name_2>:<name_3>:...:<name_n>
where <name_1>,<name_2>,...,<name_n> are the names
of drivers used in the /proc filesystem. For example:
scsihosts=aha1542:ppa:aha1542::ncr53c7xx
means that devices connected to
- first aha1542 controller - will be /dev/scsi/host0/bus#/target#/lun#
- first parallel port ZIP - will be /dev/scsi/host1/bus#/target#/lun#
- second aha1542 controller - will be /dev/scsi/host2/bus#/target#/lun#
- first NCR53C7xx controller - will be /dev/scsi/host4/bus#/target#/lun#
- any extra controller - will be /dev/scsi/host5/bus#/target#/lun#,
/dev/scsi/host6/bus#/target#/lun#, etc
- if any of above controllers will not be found - the reserved names will
not be used by any other device.
- /dev/scsi/host3/bus#/target#/lun# names will never be used
You can use ',' instead of ':' as the separator character if you
wish. I have used the devfsd naming scheme
here.
Note that this scheme does not address the SCSI host order if you have
multiple cards of the same type (such as NCR53c8xx). In this case you
need to use the driver-specific boot parameters to control this.
----------------------------------------------------------------------------- -----------------------------------------------------------------------------
...@@ -1952,12 +1911,6 @@ explores the SCSI subsystem and how it interacts with devfs ...@@ -1952,12 +1911,6 @@ explores the SCSI subsystem and how it interacts with devfs
Douglas Gilbert has written another useful document at Douglas Gilbert has written another useful document at
http://www.torque.net/scsi/scsihosts.html which
discusses the scsihosts= boot option
Douglas Gilbert has written yet another useful document at
http://www.torque.net/scsi/SCSI-2.4-HOWTO/ which http://www.torque.net/scsi/SCSI-2.4-HOWTO/ which
discusses the Linux SCSI subsystem in 2.4. discusses the Linux SCSI subsystem in 2.4.
......
...@@ -1060,8 +1060,6 @@ running once the system is up. ...@@ -1060,8 +1060,6 @@ running once the system is up.
scsi_logging= [SCSI] scsi_logging= [SCSI]
scsihosts= [SCSI]
serialnumber [BUGS=IA-32] serialnumber [BUGS=IA-32]
sf16fm= [HW] SF16FMI radio driver for Linux sf16fm= [HW] SF16FMI radio driver for Linux
......
...@@ -1357,9 +1357,7 @@ is created (in scsi_host_alloc() in hosts.c) those common members are ...@@ -1357,9 +1357,7 @@ is created (in scsi_host_alloc() in hosts.c) those common members are
initialized from the driver's struct scsi_host_template instance. Members initialized from the driver's struct scsi_host_template instance. Members
of interest: of interest:
host_no - system wide unique number that is used for identifying host_no - system wide unique number that is used for identifying
this host. Issued in ascending order from 0 (and the this host. Issued in ascending order from 0.
positioning can be influenced by the scsihosts
kernel boot (or module) parameter)
can_queue - must be greater than 0; do not send more than can_queue can_queue - must be greater than 0; do not send more than can_queue
commands to the adapter. commands to the adapter.
this_id - scsi id of host (scsi initiator) or -1 if not known this_id - scsi id of host (scsi initiator) or -1 if not known
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment