From owner-freebsd-current Mon Oct 30 15:11:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from dataloss.net (massive.dataloss.net [212.189.232.193]) by hub.freebsd.org (Postfix) with SMTP id 4FEEF37B479 for ; Mon, 30 Oct 2000 15:11:31 -0800 (PST) Received: (qmail 424 invoked by uid 1000); 30 Oct 2000 23:08:55 -0000 Date: Tue, 31 Oct 2000 00:08:55 +0100 From: Peter van Dijk To: current@FreeBSD.ORG Subject: Re: Intel Etherexpress support? Message-ID: <20001031000855.C260@dataloss.net> Mail-Followup-To: current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from winter@jurai.net on Thu, Oct 26, 2000 at 12:58:28AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 26, 2000 at 12:58:28AM -0400, Matthew N. Dodd wrote: > On Tue, 24 Oct 2000, Glendon Gross wrote: > > Is it possible to use the old Intel EtherExpress-16 cards with FreeBSD? > > The driver was broken a while back and I'm right in the middle of trying > to fix it. I've actually given up on the FreeBSD driver and ported the > NetBSD driver with mixed success. I've got 3c503 boards working great but > the EE16s are really nasty and I'm still tracking down a few issues. > > You might try the attached patch against sys/dev/ie/if_ie.c though as I'm > not quite ready to commit what I've got. Without looking at any of your code, I would kindly like to ask you not to look at the Linux driver for eexpress too much - it's severely broken and has all kinds of timing problems that can crash boxes at predictable moments (some boxes crash when you ifconfig, some crash when you run tcpdump [probably on the switch to PROMISC]). Slower boxes seem to work better. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me 'Het leven is een stuiterbal, maar de mijne plakt aan t plafond!' - me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message