From owner-freebsd-net@FreeBSD.ORG Wed Oct 11 14:56:34 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9808116A4B3 for ; Wed, 11 Oct 2006 14:56:34 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp1.utdallas.edu (smtp1.utdallas.edu [129.110.10.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76DDC43DC3 for ; Wed, 11 Oct 2006 14:56:11 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) by smtp1.utdallas.edu (Postfix) with ESMTP id 210EF388DE4 for ; Wed, 11 Oct 2006 09:55:53 -0500 (CDT) Date: Wed, 11 Oct 2006 09:52:43 -0500 From: Paul Schmehl To: freebsd-net@freebsd.org Message-ID: In-Reply-To: <20061010223001.F32706@qbhto.arg> References: <200610100433.53511.max@love2party.net> <9476505F959C119216F6FF6D@paul-schmehls-powerbook59.local> <452B60E3.1060206@unsane.co.uk> <1D56A458AD95ABD932F2DF0D@utd59514.utdallas.edu> <20061010223001.F32706@qbhto.arg> X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========24F4DB398238F037D4DB==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Intel PRO 3945ABG Wireless X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2006 14:56:34 -0000 --==========24F4DB398238F037D4DB========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Tuesday, October 10, 2006 22:30:29 -0700 Doug Barton=20 wrote: > On Tue, 10 Oct 2006, Paul Schmehl wrote: > >> Why isn't anyone working on updating it? > > This is a volunteer project. No one has volunteered. > I'd volunteer if I had a clue. I'm not a programmer, and my only exposure=20 to C/C++ is two semesters a while ago. I doubt you want me writing device=20 drivers. :-) I understand that the guy who was writing the driver had some sort of=20 disagreement with someone and dropped the project. He's still maintaining=20 the driver for OpenBSD. I'm wondering how much work it would take to adapt = what's in OBSD CVS to FBSD and get the thing working? Is it a simple=20 matter of fixing paths so they point to the right source and header files?=20 Or is there more to it? Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========24F4DB398238F037D4DB==========--