patch-2.2.15 linux/Documentation/networking/tlan.txt

• Lines: 109
• Date: Fri Apr 21 12:45:49 2000
• Orig file: v2.2.14/Documentation/networking/tlan.txt
• Orig date: Tue Jan 4 21:18:38 2000

diff -u --new-file --recursive --exclude-from ../../exclude v2.2.14/Documentation/networking/tlan.txt linux/Documentation/networking/tlan.txt
@@ -1,25 +1,4 @@
-
-
-I haven't had any time to do anything for a long time, and this isn't
-likely to change.  So there's a driver here for anyone looking to
-carry forward a project :)
-
-For those who are looking for help, I can't.  I haven't looked at
-a kernel since the early 2.0 series, so I won't know what's going on.
-Your best chance at help would be joining the TLAN mailing list and
-posting your question there.
-
-You can join by sending "subscribe tlan" in the body of an email to
-majordomo@vuser.vu.union.edu.
-
-Thanks to those who have (and who will ;) put work in to keep the TLAN
-driver working as the kernel moves on.
-
-James
-james@sovereign.org
-
-
-TLAN driver for Linux, version 1.0
+TLAN driver for Linux, version 1.2
 README
 
 
@@ -57,43 +36,7 @@
     but I do not expect any problems.
     
 
-II.  Building the Driver.
-
-    The TLAN driver may be compiled into the kernel, or it may be compiled
-    as a module separately, or in the kernel.  A patch is included for
-    2.0.29 (which also works for 2.0.30, 2.0.31, and 2.0.32).
-
-    To compile it as part of the kernel:
-        1. Download and untar the TLAN driver package.
-	2. If your kernel is 2.1.45 or later, you do not need to patch the
-           kernel sources.  Copy the tlan.c and tlan.h to drivers/net in
-           the kernel source tree.
-        3. Otherwise, apply the appropriate patch for your kernel.  For
-	   example:
-
-	       cd /usr/src/linux
-               patch -p1 < kernel.2.0.29
-
-        4. Copy the files tlan.c and tlan.h from the TLAN package to the
-           directory drivers/net in the Linux kernel source tree.
-        5. Configure your kernel for the TLAN driver.  Answer 'Y' when
-           prompted to ask about experimental code (the first question).
-           Then answer 'Y' when prompted if to include TI ThunderLAN
-           support.  If you want the driver compiled as a module, answer 'M'
-           instead of 'Y'.
-        6. Make the kernel and, if necessary, the modules.
-    
-    To compile the TLAN driver independently:
-        1. Download and untar the TLAN driver package.
-        2. Change to the tlan directory.
-        3. If you are NOT using a versioned kernel (ie, want an non-
-           versioned module), edit the Makefile, and comment out the
-           line:
-                 MODVERSIONS = -DMODVERSIONS
-        4. Run 'make'.
-
-
-III.  Driver Options
+II.  Driver Options
 	1. You can append debug=x to the end of the insmod line to get
            debug messages, where x is a bit field where the bits mean
 	   the following:
@@ -110,15 +53,15 @@
 	   device that does not have an AUI/BNC connector will probably
 	   cause it to not function correctly.)
 
-	4. You can set duplex=1 to force half duplex, and duplex=2 to
+	3. You can set duplex=1 to force half duplex, and duplex=2 to
 	   force full duplex.
 
-	5. You can set speed=10 to force 10Mbs operation, and speed=100Mbs
+	4. You can set speed=10 to force 10Mbs operation, and speed=100
 	   to force 100Mbs operation. (I'm not sure what will happen
 	   if a card which only supports 10Mbs is forced into 100Mbs
 	   mode.)
 
-	3. If the driver is built into the kernel, you can use the 3rd
+	5. If the driver is built into the kernel, you can use the 3rd
 	   and 4th parameters to set aui and debug respectively.  For
 	   example:
 
@@ -136,13 +79,13 @@
 		0x10 = use 10BaseT
 		0x20 = use 100BaseTx
 
+	6. This driver can be used as a loadable module. Se net-modules.txt
+	   for details.
 
-IV.  Things to try if you have problems.
+III.  Things to try if you have problems.
 	1. Make sure your card's PCI id is among those listed in
 	   section I, above.
-	1. Make sure routing is correct.
-	2. If you are using a 2.1.x kernel, try to duplicate the
-	   problem on a 2.0.x (preferably 2.0.29 or 2.0.30) kernel.
+	2. Make sure routing is correct.
 
 
 There is also a tlan mailing list which you can join by sending "subscribe tlan"