patch-2.1.76 linux/Documentation/networking/de4x5.txt

• Lines: 84
• Date: Sun Dec 21 22:37:32 1997
• Orig file: v2.1.75/linux/Documentation/networking/de4x5.txt
• Orig date: Sat Nov 29 11:25:08 1997

diff -u --recursive --new-file v2.1.75/linux/Documentation/networking/de4x5.txt linux/Documentation/networking/de4x5.txt
@@ -11,9 +11,9 @@
     Digital Semiconductor   SROM   Specification.    The  driver   currently
     recognises the following chips:
 
-        DC21040     (no SROM)
-	DC21041[A]
-	DC21140[A]
+        DC21040  (no SROM) 
+	DC21041[A]  
+	DC21140[A] 
 	DC21142 
 	DC21143 
 
@@ -57,7 +57,7 @@
     1) copy de4x5.c from the  /linux/drivers/net directory to your favourite
     temporary directory.
     2) for fixed  autoprobes (not  recommended),  edit the source code  near
-    line 5537 to reflect the I/O address  you're using, or assign these when
+    line 5594 to reflect the I/O address  you're using, or assign these when
     loading by:
 
                    insmod de4x5 io=0xghh           where g = bus number
@@ -92,6 +92,16 @@
     can compile with a  DEC_ONLY define, or if  loading as a module, use the
     'dec_only=1'  parameter. 
 
+    I've changed the timing routines to  use the kernel timer and scheduling
+    functions  so that the  hangs  and other assorted problems that occurred
+    while autosensing the  media  should be gone.  A  bonus  for the DC21040
+    auto  media sense algorithm is  that it can now  use one that is more in
+    line with the  rest (the DC21040  chip doesn't  have a hardware  timer).
+    The downside is the 1 'jiffies' (10ms) resolution.
+
+    IEEE 802.3u MII interface code has  been added in anticipation that some
+    products may use it in the future.
+
     The SMC9332 card  has a non-compliant SROM  which needs fixing -  I have
     patched this  driver to detect it  because the SROM format used complies
     to a previous DEC-STD format.
@@ -133,11 +143,36 @@
     is  the preferred way to use   this driver, since  it  doesn't have this
     limitation.
 
-    Where SROM  media detection is used and  full duplex is specified in the
-    SROM, the feature is ignored unless de4x5_full_duplex  is set at compile
-    time OR during a module  load (insmod de4x5 de4x5_full_duplex=1).   This
-    is because there  is no way  to automatically  detect full duplex  links
-    except through  autonegotiation.   When I  include  the  autonegotiation
-    feature  in  the  SROM  autoconf   code,   this detection  will    occur
-    automatically.
-
+    Where SROM media  detection is used and  full duplex is specified in the
+    SROM,  the feature is  ignored unless  lp->params.fdx  is set at compile
+    time  OR during  a   module load  (insmod  de4x5   args='eth??:fdx' [see
+    below]).  This is because there  is no way  to automatically detect full
+    duplex   links  except through   autonegotiation.    When I  include the
+    autonegotiation feature in  the SROM autoconf  code, this detection will
+    occur automatically for that case.
+
+    Command line arguements are  now allowed, similar to  passing arguements
+    through LILO. This will allow a per adapter board set  up of full duplex
+    and media. The only lexical constraints are:  the board name (dev->name)
+    appears in  the list before its parameters.  The list of parameters ends
+    either at the end of the parameter list or with another board name.  The
+    following parameters are allowed:
+
+            fdx        for full duplex
+	    autosense  to set the media/speed; with the following 
+	               sub-parameters:
+		       TP, TP_NW, BNC, AUI, BNC_AUI, 100Mb, 10Mb, AUTO
+
+    Case sensitivity is important  for  the sub-parameters. They *must*   be
+    upper case. Examples:
+
+        insmod de4x5 args='eth1:fdx autosense=BNC eth0:autosense=100Mb'.
+
+    For a compiled in driver, in linux/drivers/net/CONFIG, place e.g.
+	DE4X5_OPTS = -DDE4X5_PARM='"eth0:fdx autosense=AUI eth2:autosense=TP"' 
+
+    Yes,  I know full duplex  isn't permissible on BNC  or AUI; they're just
+    examples. By default, full duplex is turned  off and AUTO is the default
+    autosense setting. In  reality, I expect only the  full duplex option to
+    be used. Note the use of single quotes in the two examples above and the
+    lack of commas to separate items.