From owner-freebsd-hackers Thu Jan 25 10: 3:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id ECC9F37B6A6 for ; Thu, 25 Jan 2001 10:03:04 -0800 (PST) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id NAA73379; Thu, 25 Jan 2001 13:05:31 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010125130845.030de0f0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 25 Jan 2001 13:12:42 -0500 To: Jonathan Lemon , hackers@FreeBSD.ORG From: Dennis Subject: Re: if_fxp driver info In-Reply-To: <200101250358.f0P3w8g49073@prism.flugsvamp.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:58 PM 01/24/2001, Jonathan Lemon wrote: >In article > >you write: > > > >> > >> > I'll look into the Linux driver, however, and see if it has anything > >> > useful in it. Historically the Linux Pro/100+ driver has totally > sucked and > >> > was chalk-full of magic numbers being anded and ored. > >> > >>That's "chock full", and you're confusing the Becker driver (bad) with > >>the Intel-supplied driver (slightly less bad). > > > > > >The intel driver seems to cover all the bases and has some nice glue > >routines for determining the part and features available. > > > >I havent tested it under load, but I wonder if intel would consider > >supporting it if someone ported it over to freebsd? they have drivers for > >just about every other major OS except BSD. it would be nice if the driver > >was updated BEFORE cards and MBs that dont work started showing up on the > >loading dock. Every time I get a shipment we have to hold our breath until > >we try one out. > >The documentation is available, if you want to (or have to) sign an >NDA. People who have the NDA documentation are perfectly capable of >writing a driver, although the source can't be released. It would >probably be possible to release a binary driver, but why do anything >to help Intel, given their unhelpful attitude? If they have a published, freely distributable driver for linux. why would you have to sign an NDA to port it to FreeBSD? I dont think so. Not anymore anyway. Thats the whole point of this thread... Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message