From drs@rucus.ru.ac.za  Sun Aug 18 06:50:58 2002
Return-Path: <drs@rucus.ru.ac.za>
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BAE5A37B400
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 18 Aug 2002 06:50:58 -0700 (PDT)
Received: from server.rucus.ru.ac.za (server.rucus.ru.ac.za [146.231.115.1])
	by mx1.FreeBSD.org (Postfix) with SMTP id 0DC4743E4A
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 18 Aug 2002 06:50:56 -0700 (PDT)
	(envelope-from drs@rucus.ru.ac.za)
Received: (qmail 22072 invoked from network); 18 Aug 2002 13:50:52 -0000
Received: from bashir.dsl.ru.ac.za (146.231.113.19)
  by server.rucus.ru.ac.za with SMTP; 18 Aug 2002 13:50:52 -0000
Received: (qmail 2224 invoked by uid 1001); 18 Aug 2002 13:50:51 -0000
Message-Id: <20020818135051.2223.qmail@bashir.dsl.ru.ac.za>
Date: 18 Aug 2002 13:50:51 -0000
From: David "Siebrger" <drs@rucus.ru.ac.za>
Reply-To: David "Siebrger" <drs@rucus.ru.ac.za>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Various fixes for fxp(4)
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         41759
>Category:       docs
>Synopsis:       Various fixes for fxp(4)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bmah
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Aug 18 07:00:04 PDT 2002
>Closed-Date:    Sat Aug 24 10:07:03 PDT 2002
>Last-Modified:  Sat Aug 24 15:30:02 PDT 2002
>Originator:     David Siebrger
>Release:        FreeBSD 4.6-STABLE i386
>Organization:
Rhodes University Computer Users Society
>Environment:
System: FreeBSD bashir.dsl.ru.ac.za 4.6-STABLE FreeBSD 4.6-STABLE #11: Tue Aug 6 10:43:06 SAST 2002 drs@bashir.dsl.ru.ac.za:/usr/obj/usr/src/sys/BASHIR i386

>Description:

I've found a couple of problems with the documentation for the fxp
driver.  Here are some changes to the man page; I'm about to submit a
patch for the supported hardware list.

1. Please MFC r1.21 of src/share/man/man4/fxp.4 - fxp.4.diff1 is a
   patch to do so.  The microcode loading support that it refers to
   was MFC'ed in r1.110.2.8 of src/sys/dev/fxp/if_fxp.c.

2. r1.131 of if_fxp.c added support for the i82562 chip, and it was
   MFC'ed in r1.110.2.20.  The documentation was not updated, so
   fxp.4.diff2 will do so.  It applies to -CURRENT, and should apply
   to -STABLE once the MFC mentioned above has been done.

3. Most of the newer models of Intel cards aren't mentioned. 
   fxp.4.diff3 updates the list, based on personal experience and
   http://www.intel.com/network/connectivity.  It's dependent on the
   previous patches, but should apply to both -CURRENT and -STABLE.

4. All of Intel's docs call the cards "PRO/100", but all of the
   FreeBSD docs and source call them "Pro/100".  Is it worth fixing?

>How-To-Repeat:

>Fix:

--- fxp.4.diff1 begins here ---
--- src/share/man/man4/fxp.4.orig	Sun Aug 18 14:27:51 2002
+++ src/share/man/man4/fxp.4	Sun Aug 18 14:34:57 2002
@@ -38,8 +38,8 @@
 The
 .Nm
 driver provides support for the EtherExpress Pro/10, Pro/100B, and Pro/100+
-PCI Fast Ethernet adapters based on the Intel i82557 or i82559 ethernet
-chips.
+PCI Fast Ethernet adapters based on the Intel i82557, i82558, i82559 
+or i82550 ethernet chips.
 .Pp
 The
 .Nm
@@ -66,6 +66,20 @@
 Note that 100baseTX media type is only available on the Pro/100B and Pro/100+.
 For further information on configuring this device, see
 .Xr ifconfig 8 .
+.Pp
+The
+.Nm
+driver also supports a special link option:
+.Bl -tag -width link0
+.It Cm link0
+Some chip revisions have loadable microcode which can be used to reduce the
+interrupt load on the host cpu.  Not all boards have support microcode support.
+Setting the 
+.Cm link0
+flag with
+.Xr ifconfig 8
+will load download the microcode to the chip if it is available.
+.El
 .Sh DIAGNOSTICS
 .Bl -diag
 .It "fxp%d: couldn't map memory"
@@ -77,6 +91,9 @@
 .It "fxp%d: device timeout"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).
+.It "fxp%d: Microcode loaded, int_delay: %d usec  bundle_max: %d"
+The chip has successfully downloaded the microcode, and changed the
+parametrized values to the giveng settings.
 .El
 .Sh SEE ALSO
 .Xr arp 4 ,
--- fxp.4.diff1 ends here ---

--- fxp.4.diff2 begins here ---
--- src/share/man/man4/fxp.4.1	Sun Aug 18 14:42:18 2002
+++ src/share/man/man4/fxp.4	Sun Aug 18 14:43:25 2002
@@ -39,7 +39,7 @@
 .Nm
 driver provides support for the EtherExpress Pro/10, Pro/100B, and Pro/100+
 PCI Fast Ethernet adapters based on the Intel i82557, i82558, i82559 
-or i82550 ethernet chips.
+i82550, or i82562 ethernet chips.
 .Pp
 The
 .Nm
--- fxp.4.diff2 ends here ---

--- fxp.4.diff3 begins here ---
--- src/share/man/man4/fxp.4.2	Sun Aug 18 14:49:39 2002
+++ src/share/man/man4/fxp.4	Sun Aug 18 15:15:42 2002
@@ -37,9 +37,11 @@
 .Sh DESCRIPTION
 The
 .Nm
-driver provides support for the EtherExpress Pro/10, Pro/100B, and Pro/100+
-PCI Fast Ethernet adapters based on the Intel i82557, i82558, i82559 
-i82550, or i82562 ethernet chips.
+driver provides support for the EtherExpress Pro/10, InBusiness 10/100,
+Pro/100 B, Pro/100+, Pro/100 VE, Pro/100 M, Pro/100 S PCI Fast Ethernet
+adapters based on the Intel i82557, i82558, i82559 i82550, or i82562
+ethernet chips.  Many on-board network interfaces on Intel motherboards
+use those chips and are also supported.
 .Pp
 The
 .Nm
@@ -63,7 +65,7 @@
 Set full duplex operation
 .El
 .Pp
-Note that 100baseTX media type is only available on the Pro/100B and Pro/100+.
+Note that 100baseTX media type is not available on the Pro/10.
 For further information on configuring this device, see
 .Xr ifconfig 8 .
 .Pp
--- fxp.4.diff3 ends here ---


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-doc->bmah 
Responsible-Changed-By: bmah 
Responsible-Changed-When: Wed Aug 21 08:40:46 PDT 2002 
Responsible-Changed-Why:  
Related to docs/41760, which I just grabbed, so I'll take this one too. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=41759 
State-Changed-From-To: open->closed 
State-Changed-By: bmah 
State-Changed-When: Sat Aug 24 10:02:53 PDT 2002 
State-Changed-Why:  
I committed a variant of your patches to -CURRENT and 4-STABLE. 

For future reference, the microcode patch for 4-STABLE didn't yield 
the same text as on -CURRENT.  We also try to put a newline immediately 
after the full-stop that ends a sentence, and trailing whitespace at  
the end of a line is a no-no as it sometimes makes groff do some odd 
things. 

Thanks for the diffs! 


http://www.freebsd.org/cgi/query-pr.cgi?pr=41759 

From: David =?iso-8859-1?Q?Sieb=F6rger?= <drs@rucus.ru.ac.za>
To: "Bruce A. Mah" <bmah@FreeBSD.org>,
	freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: docs/41759: Various fixes for fxp(4)
Date: Sat, 24 Aug 2002 20:01:11 +0200

 On Sat 2002-08-24 (10:06), Bruce A. Mah wrote:
 > Synopsis: Various fixes for fxp(4)
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: bmah
 > State-Changed-When: Sat Aug 24 10:02:53 PDT 2002
 > State-Changed-Why: 
 > I committed a variant of your patches to -CURRENT and 4-STABLE.
 > 
 > For future reference, the microcode patch for 4-STABLE didn't yield
 > the same text as on -CURRENT.  We also try to put a newline immediately
 > after the full-stop that ends a sentence, and trailing whitespace at 
 > the end of a line is a no-no as it sometimes makes groff do some odd
 > things.
 > 
 > Thanks for the diffs!
 > 
 > 
 > http://www.freebsd.org/cgi/query-pr.cgi?pr=41759
 
 It looks as if you've committed the new chips, but not the new card
 names.  (Apologies if the way I split the diffs up made it
 confusing.)
 
 
 -- 
 David Siebrger
 drs@rucus.ru.ac.za

From: bmah@FreeBSD.ORG (Bruce A. Mah)
To: David =?iso-8859-1?Q?Sieb=F6rger?= <drs@rucus.ru.ac.za>
Cc: "Bruce A. Mah" <bmah@FreeBSD.ORG>,
	freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: docs/41759: Various fixes for fxp(4) 
Date: Sat, 24 Aug 2002 15:28:00 -0700

 --==_Exmh_-88148992P
 Content-Type: text/plain; charset=iso-8859-1
 Content-Transfer-Encoding: 8bit
 
 If memory serves me right, David =?iso-8859-1?Q?Sieb=F6rger?= wrote:
 
 > It looks as if you've committed the new chips, but not the new card
 > names.  (Apologies if the way I split the diffs up made it
 > confusing.)
 
 My fault, sorry about that.  I think I got it right now.
 
 Thanks!
 
 Bruce.
 
 
 
 --==_Exmh_-88148992P
 Content-Type: application/pgp-signature
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.7 (FreeBSD)
 Comment: Exmh version 2.5+ 20020506
 
 iD8DBQE9aAhw2MoxcVugUsMRApT1AJ4w9vjrs8xytPrA15AUWYFLblOycQCgkha6
 1Hi36AcjoU2ylJSHDsjyAEA=
 =yB4y
 -----END PGP SIGNATURE-----
 
 --==_Exmh_-88148992P--
>Unformatted:
