Re: CVS access probably blocked
Hello list,
> In short, I wonder it it wouldn't be wise to have this new
driver
> enabled from the stating-kmod than the wl-kmod that might become
> unmaintained.
For the moment, as shown in this table
http://wireless.kernel.org/en/users/Drivers/b43#Supported_devices the
bcm4313 wireless chipset isn't supported by the b43 driver (WIP). As
it's my wireless chipset, I've only been able to use it with the wl
driver (hybrid driver: wireless + Bluetooth) provided by Broadcom.
Broadcom just released the 5.100.82.111 version of this driver, and it
seems to be compatible with kernels 3.x as the 5.100.82.38. For my part,
I haven't only tested these two versions with 2.6.40 kernel series on
Fedora. 5.100.82.111 kernel panics, like others maintainers noticed it
(http://aur.archlinux.org/packages.php?ID=19514). 5.100.82.38 works.
I've also tested the 5.100.82.38 driver on Ubuntu Oneiric amd64 with
kernel version 3.0.0-12 (Ubuntu names and versions) and a bcm4313
chipset too. It works too.
Responding to myself!
To correct this, from the 10/25/2011 (yesterday) Broadcom provided a new
version of the wl driver: 5.100.82.112. This one compiles fine and most
important works (no kernel panic) on my bcm4313. I have both broadcom-wl
and wl-kmod spec files and srpms files ready to be reviewed if
necessary. Let me know if I have to open new requests reviews or if I
have to modify 1998 and 1999 ones made for the 5.100.82.38 version
(https://bugzilla.rpmfusion.org/show_bug.cgi?id=1998
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1999).
I think that kernel drivers developers discussions about kernel-staging
branch and brcm drivers, and Broadcom attitude in providing yesterday a
new working wl driver, indicates that both alternatives have to be
considered for the moment. Of course, as a newcomer, I'm not enough
aware of such questions and my point of view has to be considered as a
modest contribution to the discussion.
Thanks in advance for your responses!
--
Nicolas Viéville