From owner-freebsd-net Tue Sep 3 11:35:13 2002 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EE5A37B400 for ; Tue, 3 Sep 2002 11:35:11 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72CDA43E6A for ; Tue, 3 Sep 2002 11:35:10 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.5/8.12.5) with ESMTP id g83IZ9KD095737; Tue, 3 Sep 2002 12:35:09 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.5/8.12.5/Submit) id g83IZ8uI095736; Tue, 3 Sep 2002 12:35:08 -0600 (MDT) (envelope-from ken) Date: Tue, 3 Sep 2002 12:35:08 -0600 From: "Kenneth D. Merry" To: Charles Sprickman Cc: freebsd-net@FreeBSD.ORG Subject: Re: fxp and 802.3 flow control Message-ID: <20020903123508.A95635@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from spork@inch.com on Thu, Aug 29, 2002 at 09:30:01PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Aug 29, 2002 at 21:30:01 -0400, Charles Sprickman wrote: > Hi, > > I'm looking at this message in the archives: > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=172663+0+archive/2000/freebsd-net/20000220.freebsd-net > > And wondering the same thing... Don't see anything in the fxp manpage > about this, was Ken's patch included at some point? Is his explanation on > target? The problem is still there. I've got a local patch in my tree to take care of it. Jonathan Lemon did some things to attempt to make it better, but they didn't fix the problem for me. I've attached a patch against -current that fixes it for me with the new fxp driver. (The patch in the message above is against the old fxp driver.) Ken -- Kenneth Merry ken@kdm.org --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_fxp.c.20020903" --- //depot/FreeBSD-current/src/sys/dev/fxp/if_fxp.c 2002/08/19 15:56:44 +++ //depot/FreeBSD-ken/src/sys/dev/fxp/if_fxp.c 2002/08/20 13:59:13 @@ -1696,10 +1696,10 @@ cbp->fc_delay_lsb = 0x1f; cbp->fc_delay_msb = 0x01; cbp->pri_fc_thresh = 3; - cbp->tx_fc_dis = 0; /* enable transmit FC */ + cbp->tx_fc_dis = 1; /* enable transmit FC */ cbp->rx_fc_restop = 1; /* enable FC restop frames */ cbp->rx_fc_restart = 1; /* enable FC restart frames */ - cbp->fc_filter = !prm; /* drop FC frames to host */ + cbp->fc_filter = 1; /* drop FC frames to host */ cbp->pri_fc_loc = 1; /* FC pri location (byte31) */ } --envbJBWh7q8WU6mo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message