From owner-freebsd-net Wed Oct 6 10:18:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (Postfix) with ESMTP id 8C6E415759 for ; Wed, 6 Oct 1999 10:18:18 -0700 (PDT) (envelope-from lamaster@nren.nasa.gov) Received: from localhost by george.arc.nasa.gov (8.9.3/8.9.3) with SMTP id KAA13960 for ; Wed, 6 Oct 1999 10:16:52 -0700 (PDT) X-Authentication-Warning: george.arc.nasa.gov: lamaster owned process doing -bs Date: Wed, 6 Oct 1999 10:16:51 -0700 (PDT) From: Hugh LaMaster X-Sender: lamaster@george.arc.nasa.gov To: "FreeBSD-Net (FreeBSD.Org)" Subject: Re: Tulip drivers for BSD. In-Reply-To: <37EB1C97.64915398@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 24 Sep 1999, Wes Peters wrote: > > Can any one tell me the sites for "Well Documented" Tulip drivers for BSD. > > I did search a lot but failed. > > man de > > They're included in the system; you don't have to go fetch them from some > website somewhere. Yes, and, when last I looked at it, the Tulip cards were the most efficient available when it comes to multicast, and, very good wrt high-bandwidth CPU efficiency. Unfortunately, over the last year, most companies shipping NICs have stopped marking on the packages what chipset they use, and some have switched chipsets within the same product line. At this point, I have no idea how to tell which current product lines use the Tulip chipset. Is anyone keeping a current list? Is the Tulip chipset still in production/widespread use? What are FreeBSD'ers recommending these days wrt multicast and CPU efficiency (and, which is currently supported)? -- Hugh LaMaster, M/S 233-21, Email: lamaster@nren.nasa.gov NASA Ames Research Center Or: lamaster@nas.nasa.gov Moffett Field, CA 94035-1000 Or: lamaster@george.arc.nasa.gov Phone: 650/604-1056 Disc: Unofficial, personal *opinion*. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message