From owner-freebsd-current@FreeBSD.ORG Tue Nov 9 08:52:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9073116A4CF for ; Tue, 9 Nov 2004 08:52:12 +0000 (GMT) Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F19D43D1F for ; Tue, 9 Nov 2004 08:52:12 +0000 (GMT) (envelope-from yb@sainte-barbe.org) Received: from taz.hsc.fr (taz.hsc.fr [192.70.106.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "taz.hsc.fr", Issuer "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id 0F9442165F for ; Tue, 9 Nov 2004 09:36:55 +0100 (CET) Received: by taz.hsc.fr (Postfix, from userid 1001) id 56DB1408D; Tue, 9 Nov 2004 09:37:09 +0100 (CET) Date: Tue, 9 Nov 2004 09:37:09 +0100 From: Yann Berthier To: freebsd-current@freebsd.org Message-ID: <20041109083709.GA721@hsc.fr> Mail-Followup-To: freebsd-current@freebsd.org References: <20041028.115737.55780539.shigeru@iij.ad.jp> <1099044833.1063.14.camel@localhost> <4182909C.6090505@twilley.org> <20041108130614.GA805@hsc.fr> <4190211A.6070805@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4190211A.6070805@elischer.org> X-Organization: Herve Schauer Consultants X-Web: http://www.hsc.fr/ X-Operating-System: FreeBSD 6.0-CURRENT User-Agent: Mutt/1.5.6i Subject: Re: who is test Intel PRO/Wireless 2100/2200BG/2915ABG? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2004 08:52:12 -0000 On Mon, 08 Nov 2004, Julian Elischer wrote: > >Another vote for "yes, I use this driver and like it". > > > > > It's hard to commit if it requires firmware that can't be distributed. The firmware can be distributed in a separated package, that's what the driver's author has proposed, see PR 71398 I suppose that this is what have done the other 2 (3 ?) BSDs > Mind you that hasn't stopped the NDIS driver.. that requires the same > firmware.. sure cheers, - yann