Commit eb24df0d authored by James Nelson's avatar James Nelson Committed by Linus Torvalds

[PATCH] cciss: Documentation update

Updates to cciss documentation.

mkdev.cciss is no longer needed, since it is handled by the MAKEDEV program.
Signed-off-by: default avatarJames Nelson <james4765@gmail.com>
Acked-by: default avatarMike Miller <mike.miller@hp.com>
Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
parent a9f36aaa
...@@ -172,8 +172,6 @@ memory.txt ...@@ -172,8 +172,6 @@ memory.txt
- info on typical Linux memory problems. - info on typical Linux memory problems.
mips/ mips/
- directory with info about Linux on MIPS architecture. - directory with info about Linux on MIPS architecture.
mkdev.cciss
- script to make /dev entries for SMART controllers (see cciss.txt).
mono.txt mono.txt
- how to execute Mono-based .NET binaries with the help of BINFMT_MISC. - how to execute Mono-based .NET binaries with the help of BINFMT_MISC.
moxa-smartio moxa-smartio
......
...@@ -17,17 +17,15 @@ This driver is known to work with the following cards: ...@@ -17,17 +17,15 @@ This driver is known to work with the following cards:
* SA 6422 * SA 6422
* SA V100 * SA V100
If nodes are not already created in the /dev/cciss directory If nodes are not already created in the /dev/cciss directory, run as root:
# mkdev.cciss [ctlrs] # cd /dev
# ./MAKEDEV cciss
Where ctlrs is the number of controllers you have (defaults to 1 if not
specified).
Device Naming: Device Naming:
-------------- --------------
You need some entries in /dev for the cciss device. The mkdev.cciss script You need some entries in /dev for the cciss device. The MAKEDEV script
can make device nodes for you automatically. Currently the device setup can make device nodes for you automatically. Currently the device setup
is as follows: is as follows:
...@@ -35,7 +33,11 @@ Major numbers: ...@@ -35,7 +33,11 @@ Major numbers:
104 cciss0 104 cciss0
105 cciss1 105 cciss1
106 cciss2 106 cciss2
etc... 105 cciss3
108 cciss4
109 cciss5
110 cciss6
111 cciss7
Minor numbers: Minor numbers:
b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0
...@@ -45,7 +47,7 @@ Minor numbers: ...@@ -45,7 +47,7 @@ Minor numbers:
| |
+-------------------- Logical Volume number +-------------------- Logical Volume number
The suggested device naming scheme is: The device naming scheme is:
/dev/cciss/c0d0 Controller 0, disk 0, whole device /dev/cciss/c0d0 Controller 0, disk 0, whole device
/dev/cciss/c0d0p1 Controller 0, disk 0, partition 1 /dev/cciss/c0d0p1 Controller 0, disk 0, partition 1
/dev/cciss/c0d0p2 Controller 0, disk 0, partition 2 /dev/cciss/c0d0p2 Controller 0, disk 0, partition 2
...@@ -117,16 +119,13 @@ from the adapter, informing the SCSI mid layer may not be necessary. ...@@ -117,16 +119,13 @@ from the adapter, informing the SCSI mid layer may not be necessary.
Note that the naming convention of the /proc filesystem entries Note that the naming convention of the /proc filesystem entries
contains a number in addition to the driver name. (E.g. "cciss0" contains a number in addition to the driver name. (E.g. "cciss0"
instead of just "cciss" which you might expect.) This is because instead of just "cciss" which you might expect.)
of changes to the 2.4 kernel PCI interface related to PCI hot plug
that imply the driver must register with the SCSI mid layer once per
adapter instance rather than once per driver.
Note: ONLY sequential access devices and medium changers are presented Note: ONLY sequential access devices and medium changers are presented
as SCSI devices to the SCSI mid layer by the cciss driver. Specifically, as SCSI devices to the SCSI mid layer by the cciss driver. Specifically,
physical SCSI disk drives are NOT presented to the SCSI mid layer. The physical SCSI disk drives are NOT presented to the SCSI mid layer. The
physical SCSI disk drives are controlled directly by the array controller physical SCSI disk drives are controlled directly by the array controller
hardware and it is important to prevent the OS from attempting to directly hardware and it is important to prevent the kernel from attempting to directly
access these devices too, as if the array controller were merely a SCSI access these devices too, as if the array controller were merely a SCSI
controller in the same way that we are allowing it to access SCSI tape drives. controller in the same way that we are allowing it to access SCSI tape drives.
#!/bin/sh
# Script to create device nodes for SMART array controllers
# Usage:
# mkdev.cciss [num controllers] [num log volumes] [num partitions]
#
# With no arguments, the script assumes 1 controller, 16 logical volumes,
# and 16 partitions/volume, which is adequate for most configurations.
#
# If you had 5 controllers and were planning on no more than 4 logical volumes
# each, using a maximum of 8 partitions per volume, you could say:
#
# mkdev.cciss 5 4 8
#
# Of course, this has no real benefit over "mkdev.cciss 5" except that it
# doesn't create so many device nodes in /dev/cciss.
NR_CTLR=${1-1}
NR_VOL=${2-16}
NR_PART=${3-16}
if [ ! -d /dev/cciss ]; then
mkdir -p /dev/cciss
fi
C=0; while [ $C -lt $NR_CTLR ]; do
MAJ=`expr $C + 104`
D=0; while [ $D -lt $NR_VOL ]; do
P=0; while [ $P -lt $NR_PART ]; do
MIN=`expr $D \* 16 + $P`
if [ $P -eq 0 ]; then
mknod /dev/cciss/c${C}d${D} b $MAJ $MIN
else
mknod /dev/cciss/c${C}d${D}p${P} b $MAJ $MIN
fi
P=`expr $P + 1`
done
D=`expr $D + 1`
done
C=`expr $C + 1`
done
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