Date: Wed, 14 Jan 2009 00:14:05 +0100 From: "Paul B. Mahol" <onemda@gmail.com> To: "Alex Keda" <admin@lissyara.su> Cc: freebsd-current@freebsd.org Subject: Re: About bwi Message-ID: <3a142e750901131514i9473a56u9c886bbe8eb635b5@mail.gmail.com> In-Reply-To: <496CE64F.3060703@lissyara.su> References: <496CDDD8.6020704@lissyara.su> <496CE02A.5000002@lissyara.su> <496CE2CC.300@freebsd.org> <496CE64F.3060703@lissyara.su>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/13/09, Alex Keda <admin@lissyara.su> wrote: > Sam Leffler pishet: >> Alex Keda wrote: >>> Alex Keda D-?D-,N^D-uN': >>>> We want to know - that the driver bwi >>>> Are there any time limits may need some help feasible >>> >>> Explain =) >>> We want to know - how to promote the development of the driver, is >>> there a time frame for its appearance in the source tree? >> >> I know of noone working on bwi. Until there's a developer willing to >> support/maintain the code it's unlikely to go in the tree. > Can you porting bwi from perforce to CURRENT? > I know human who working with driver... > Only porting. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > It actually was ported, and sources for 8.0-CURRENT was available for testing(and probably still is). Last time I checked it, bwi was still in perforce but development stopped. On other hand bwi have its own bugs (performance was suboptimal in my environment) and development of driver itself is in stagnation. Not mentioning imposibility for supporting newer broadcom chips. -- Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750901131514i9473a56u9c886bbe8eb635b5>