From owner-freebsd-questions Tue Sep 3 19:06:34 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA15318 for questions-outgoing; Tue, 3 Sep 1996 19:06:34 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts6-line5.uoregon.edu [128.223.150.35]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA15309 for ; Tue, 3 Sep 1996 19:06:29 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id TAA00336; Tue, 3 Sep 1996 19:06:01 -0700 (PDT) Date: Tue, 3 Sep 1996 19:06:01 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Garth Corral cc: FreeBSD Questions Subject: Re: ep driver buggy? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 3 Sep 1996, Garth Corral wrote: > Found this while browsing the FreeBSD handbook at freebsd.org: > > [from section 5.3.8. Networking] > > device ep0 at isa? port 0x300 net irq 10 vector epintr > > 3Com 3C509 (buggy) > > What exactly does 'buggy' mean? Is this up to date? The 3c509 driver has come on hard times recently. It isn't very stable, main example being that the card will 'disappear' until it is disabled and re-enabled with 'ifconfig ed0 down' and 'ifconfig ed0 up'. The NE2000 code is still as solid as ever :-) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major