X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=Documentation%2Fcpqarray.txt;h=c7154e20ef5ed8720a1c7ea93eed137e8f8983ea;hb=eb61ad45c131d68a2c3a8da3a4d7e5a64c8a1f8f;hp=d0e185f7c9300e9b17336a3e811d3072bd60df84;hpb=daddc0d38b3571bed170afa273a49a0eba090c1e;p=linux-2.6.git

diff --git a/Documentation/cpqarray.txt b/Documentation/cpqarray.txt
index d0e185f7c..c7154e20e 100644
--- a/Documentation/cpqarray.txt
+++ b/Documentation/cpqarray.txt
@@ -26,31 +26,13 @@ unable to test against these cards:
 	* IDA-2
 	* IAES
 
-Installing:
------------
-
-You need to build a new kernel to use this device, even if you want to
-use a loadable module.  
-
-Apply the patch to a 2.2.x kernel:
-
-# cd linux
-# patch -p1 <smart2.patch
-
-Then build a new kernel and turn on Compaq SMART2 Disk Array support.
-Create device nodes for the diskarray device:
-
-# mkdev.ida [ctlrs]
-
-Where ctlrs is the number of controllers you have (defaults to 1 if not
-specified).
 
 EISA Controllers:
 -----------------
 
 If you want to use an EISA controller you'll have to supply some
-insmod/lilo parameters.  If the driver is compiled into the kernel, must
-give it the controller's IO port address at boot time (it is no longer
+modprobe/lilo parameters.  If the driver is compiled into the kernel, must
+give it the controller's IO port address at boot time (it is not
 necessary to specify the IRQ).  For example, if you had two SMART-2/E
 controllers, in EISA slots 1 and 2 you'd give it a boot argument like
 this:
@@ -59,29 +41,27 @@ this:
 
 If you were loading the driver as a module, you'd give load it like this:
 
-	insmod cpqarray.o eisa=0x1000,0x2000
+	modprobe cpqarray eisa=0x1000,0x2000
 
 You can use EISA and PCI adapters at the same time.
 
-Booting:
---------
-
-You'll need to use a modified lilo if you want to boot from a disk array.
-Its simply a version of lilo with some code added to tell it how to
-understand Compaq diskarray devices.
 
 Device Naming:
 --------------
 
-You need some entries in /dev for the ida device.  The mkdev.ida script
-can make device nodes for you automatically.  Currently the device setup
-is as follows:
+You need some entries in /dev for the ida device.  MAKEDEV in the /dev
+directory can make device nodes for you automatically.  The device setup is
+as follows:
 
 Major numbers:
 	72	ida0
 	73	ida1
 	74	ida2
-	etc...
+	75	ida3
+	76	ida4
+	77	ida5
+	78	ida6
+	79	ida7
 
 Minor numbers:
         b7 b6 b5 b4 b3 b2 b1 b0
@@ -91,7 +71,7 @@ Minor numbers:
              |
              +-------------------- Logical Volume number
 
-The suggested device naming scheme is:
+The device naming scheme is:
 /dev/ida/c0d0		Controller 0, disk 0, whole device
 /dev/ida/c0d0p1		Controller 0, disk 0, partition 1
 /dev/ida/c0d0p2		Controller 0, disk 0, partition 2
@@ -101,3 +81,13 @@ The suggested device naming scheme is:
 /dev/ida/c1d1p1		Controller 1, disk 1, partition 1
 /dev/ida/c1d1p2		Controller 1, disk 1, partition 2
 /dev/ida/c1d1p3		Controller 1, disk 1, partition 3
+
+
+Changelog:
+==========
+
+10-28-2004 :	General cleanup, syntax fixes for in-kernel driver version.
+		James Nelson <james4765@gmail.com>
+
+
+1999 :		Original Document