Date: Wed, 11 Oct 2006 09:52:43 -0500 From: Paul Schmehl <pauls@utdallas.edu> To: freebsd-net@freebsd.org Subject: Re: Intel PRO 3945ABG Wireless Message-ID: <EA29EF1E773CDD1D19FD470E@utd59514.utdallas.edu> In-Reply-To: <20061010223001.F32706@qbhto.arg> References: <C59FC984C46D83A90D0BC287@paul-schmehls-powerbook59.local> <200610100433.53511.max@love2party.net> <9476505F959C119216F6FF6D@paul-schmehls-powerbook59.local> <452B60E3.1060206@unsane.co.uk> <1D56A458AD95ABD932F2DF0D@utd59514.utdallas.edu> <20061010223001.F32706@qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
--On Tuesday, October 10, 2006 22:30:29 -0700 Doug Barton <dougb@FreeBSD.org> 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 to C/C++ is two semesters a while ago. I doubt you want me writing device drivers. :-) I understand that the guy who was writing the driver had some sort of disagreement with someone and dropped the project. He's still maintaining 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 matter of fixing paths so they point to the right source and header files? 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EA29EF1E773CDD1D19FD470E>