From owner-freebsd-hackers Wed Nov 28 16:38:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 7482837B417; Wed, 28 Nov 2001 16:38:18 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fAT0gCA06193; Wed, 28 Nov 2001 16:42:12 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200111290042.fAT0gCA06193@mass.dis.org> To: Andre Oppermann Cc: Prafulla Deuskar , freebsd-hackers@freebsd.org, freebsd-net@freebsd.org, msmith@mass.dis.org Subject: Re: Intel gigabit driver In-Reply-To: Message from Andre Oppermann of "Thu, 29 Nov 2001 00:50:40 +0100." <3C057850.55E9BC99@pipeline.ch> Date: Wed, 28 Nov 2001 16:42:12 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > What happend at Intel? Their driver is even released under the > BSD license! (and the Linux one under the GPL) Many Intel software products are released under a BSD-like license. Consider the ACPI CA codebase we use. > > The driver will be committed to -CURRENT first and MFC'ed to > > -STABLE later. > > Really? What about the gx driver? The 'gx' driver was committed so that Jonathan's code would be on record, since he'd spent so much time and effort on it. Testing so far has indicated that the Intel driver is generally superior, but it's not a very BSD-like driver and under some circumstances this can be considered a bad thing. The Intel driver will be the preferred driver for these cards. = Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message