patch-2.0.34 linux/Documentation/networking/tlan.README

• Lines: 131
• Date: Wed Jun 3 15:17:46 1998
• Orig file: v2.0.33/linux/Documentation/networking/tlan.README
• Orig date: Wed Dec 31 16:00:00 1969

diff -u --recursive --new-file v2.0.33/linux/Documentation/networking/tlan.README linux/Documentation/networking/tlan.README
@@ -0,0 +1,130 @@
+Caldera TLAN driver for Linux, version 0.42
+README
+
+
+I.  Supported Devices.
+
+    Only PCI devices will work with this driver.
+
+    Supported:
+    Vendor ID	Device ID	Name
+    0e11	ae32		Compaq Netelligent 10/100 TX
+    0e11	ae34		Compaq Netelligent 10 T
+    0e11	ae35		Compaq Integrated NetFlex 3/P
+    0e11	ae43		Compaq ProLiant Integrated Netelligent 10/100 TX
+    0e11	ae40		Compaq Dual Port Netelligent 10/100 TX
+    0e11	b011		Compaq Deskpro 4000 5233MMX
+    0e11	f130		Compaq NetFlex 3/P
+    0e11	f150		Compaq NetFlex 3/P
+    108d	0014		Olicom OC-2326	
+
+    Caveats:
+    
+    I don't believe 100BaseTX daughterboards will work.  I am interested
+    in any reports.
+    
+
+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
+	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:
+	   
+	   0x01		Turn on general debugging messages.
+	   0x02		Turn on receive debugging messages.
+	   0x04		Turn on transmit debugging messages.
+	   0x08		Turn on list debugging messsages.
+
+	2. You can append aui=1 to the end of the insmod line to cause
+           the adapter to use the AUI interface instead of the 10 Base T
+           interface.  This is also what to do if you want to use the BNC
+	   connector on a TLAN based device.  (Setting this option on a
+	   device that does not have an AUI/BNC connector will probably
+	   cause it to not function correctly.)
+
+	3. If the driver is built into the kernel, you can use the 3rd
+	   and 4th parameters to set aui and debug respectively.  For
+	   example:
+
+	   ether=0,0,0x1,0x7,eth0
+
+	   This sets aui to 0x1 and debug to 0x7, assuming eth0 is a
+	   supported TLAN device.
+
+	   The bits in the third byte are assigned as follows:
+
+		0x01 = aui
+		0x02 = use SA_INTERRUPT flag when reserving the irq.
+
+
+IV.  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.
+	3. Set debug to 7, either in tlan.c or through insmod as in
+	   section III.1 above.
+	4. Make sure klog is running so the kernel messages are
+	   being recorded somewhere.
+	5. Run the following sequence of programs in order (you
+	   may want to do this within an xterm, as background
+	   traffic may cause a lot of TLAN RECEIVED: messages
+	   on the console):
+
+	   ifconfig eth0 your.ip.address netmask your.net.mask up
+	   route add -net local.net.address eth0
+	   ifconfig
+	   ping some.computer.on.local.net
+	   ifconfig eth0 down
+
+	6. Mail the log of what occurred to me.  Also include the
+	   kernel version and what media/connector type (eg,
+	   10 BaseT/RJ45, 100 BaseTX/RJ45, Thinnet/BNC, etc).
+
+
+
+Please e-mail me with any comments, successes, or failures.  Thanks.
+
+There is also a tlan mailing list which you can join by sending "subscribe tlan"
+in the body of an email to majordomo@vuser.vu.union.edu.  I will announce new
+releases of the TLAN driver there.
+
+James
+james.banks@caldera.com
+