<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/4/27 Nicolas Viéville <span dir="ltr"><<a href="mailto:nicolas.vieville@univ-valenciennes.fr" target="_blank">nicolas.vieville@univ-valenciennes.fr</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello list,<br></blockquote><div>Hi Nicolas,<br> <br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
The context:<br>
<br>
I actually maintain the broadcom-wl and the wl-kmod packages.<br>
<br>
Since kernel 3.8.x, I had to face some impossible to solve issues (rfbz<br>
#2721 for example). To be more precise, the problems seem to be located<br>
in the binary part (blob) of the Broadcom STA wireless driver.<br>
<br>
I also posted Review Requests against RPMFusion for Broadcom wireless<br>
driver for bcm43142 device<br>
(<a href="https://bugzilla.rpmfusion.org/show_bug.cgi?id=2550" target="_blank">https://bugzilla.rpmfusion.org/show_bug.cgi?id=2550</a> and<br>
<a href="https://bugzilla.rpmfusion.org/show_bug.cgi?id=2549" target="_blank">https://bugzilla.rpmfusion.org/show_bug.cgi?id=2549</a>).<br></blockquote><div>Do these kmod will works with kernel 3.8 ?<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
While trying to solve rfbz #2721, I found on an Ubuntu PPA repository a<br>
new non-official Broadcom STA wireless driver that seems to be<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
compatible with Broadcom wireless devices. <br></blockquote><div>I think it's problematic to have beta or non-official release into fedora stable.<br>If it move the problem from a sure crash, to a random crash, it doesn't worth the effort to have it in stable releases.<br>
<br></div><div>What can be done instead, is indeed to hold the kmod into updates-testing to signal to the non-stable status of the driver.<br></div><div>Also I wonder it isn't best to be back to ndiswrapper in some cases ?<br>
</div><div></div><div><br></div><div>For now, you could state the different methods on the <a href="http://rpmfusion.org">rpmfusion.org</a> wiki and to point to the link from the RPM %description field.<br></div><div>Also worth to state this is to explain how to rely on the firmware extracted from the windows driver. instead of relying on the free <br>
</div><div>(this side should be handled in the fedora wiki actually).<br><br></div><div></div><div><br></div><div>Nicolas (kwizart)<br></div><div><br><br></div><div><br><br></div></div><br></div></div>