Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#688823: broadcom-sta-dkms: to version >= 6.20.55.19 (r300276)
169 views
Skip to first unread message
Jasmine Hassan
Sep 25, 2012, 6:50:02 PM9/25/12
to
Package: broadcom-sta-dkms
Version: 6.20.55.19
Hello,
My newish Dell Inspiron 15R 5520 shipped with ubuntu installed, and
had this (apparently unreleased?) version of broadcom-sta-dkms, for
the bcm43142 (Dell hybrid wifi/bluetooth adapter / 14e4:4365)
# lspci -nn | tail -1
08:00.0 Network controller [0280]: Broadcom Corporation Device
[14e4:4365] (rev 01)
# dmesg | grep BCM
eth0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.20.55.19 (r300276)
Someone (owner of Vostro 3460 laptop with the same card) kindly
uploaded the original debs, at http://wielki.tk/vostro/
The driver in question:
http://wielki.tk/vostro/debs/wireless-bcm43142-oneiric-dkms_6.20.55.19~bdcom0602.0400.1000.0400-0somerville1_amd64.deb
But it had at least two main issues that needed fixing:
1. Failed to compile on kernel 3.2.x. Solution: One-line change of the
call 'ndo_set_multicast_list' to 'ndo_set_rx_mode', in wl_linux.c
2. Failed to compile on Kernel 3.4.x. Like broadcom-sta/5.100.82.112-7
, this version also suffered issue with missing asm/system.h on 3.4.x
(see bug #677193). Fixed in the same manner as that proposed in said
bug.
(Updated md5sum of wl_linux.c, per changes 1 & 2 above)
3. Removed "oneiric" (reference to Ubuntu 11.10) from package name,
and all directory & path-names everywhere in the package contents, as
it is no longer ubuntu/oneiric-specific.
Updated deb: http://jas.gemnetworks.com/debian/wireless-bcm43142-dkms-6.20.55.19_amd64.deb
Also tested on linux 3.5.0-4.dmz.1-liquorix-amd64, and it works for me
Now, given a power regression in kernel 3.5, I was eager to test drive
3.6-rc6, and found rc7 out already!
So yesterday I installed linux 3.6-rc7.towo.1-siduction-amd64, the
"wl" module compiles and installs, and loads okay upon boot to
3.6-rc7. However, I'm unable to associate to my AP:
Pointers in syslog
Sep 25 21:34:10 terra wpa_supplicant[2787]: nl80211: 'nl80211' generic
netlink not found
Sep 25 21:34:10 terra wpa_supplicant[2787]: Failed to initialize
driver 'nl80211'
[..snip]
Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Trying to associate
with 00:xx:xx:xx:xx:xx (SSID='xxxxxxx' freq=2452 MHz)
Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Association request
to the driver failed
As bcm43142 is fairly new, this proprietary driver is all that's there
to support it. Sad face.
Cheers,
Jasmine
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Version: 6.20.55.19
Hello,
My newish Dell Inspiron 15R 5520 shipped with ubuntu installed, and
had this (apparently unreleased?) version of broadcom-sta-dkms, for
the bcm43142 (Dell hybrid wifi/bluetooth adapter / 14e4:4365)
# lspci -nn | tail -1
08:00.0 Network controller [0280]: Broadcom Corporation Device
[14e4:4365] (rev 01)
# dmesg | grep BCM
eth0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.20.55.19 (r300276)
Someone (owner of Vostro 3460 laptop with the same card) kindly
uploaded the original debs, at http://wielki.tk/vostro/
The driver in question:
http://wielki.tk/vostro/debs/wireless-bcm43142-oneiric-dkms_6.20.55.19~bdcom0602.0400.1000.0400-0somerville1_amd64.deb
But it had at least two main issues that needed fixing:
1. Failed to compile on kernel 3.2.x. Solution: One-line change of the
call 'ndo_set_multicast_list' to 'ndo_set_rx_mode', in wl_linux.c
2. Failed to compile on Kernel 3.4.x. Like broadcom-sta/5.100.82.112-7
, this version also suffered issue with missing asm/system.h on 3.4.x
(see bug #677193). Fixed in the same manner as that proposed in said
bug.
(Updated md5sum of wl_linux.c, per changes 1 & 2 above)
3. Removed "oneiric" (reference to Ubuntu 11.10) from package name,
and all directory & path-names everywhere in the package contents, as
it is no longer ubuntu/oneiric-specific.
Updated deb: http://jas.gemnetworks.com/debian/wireless-bcm43142-dkms-6.20.55.19_amd64.deb
Also tested on linux 3.5.0-4.dmz.1-liquorix-amd64, and it works for me
Now, given a power regression in kernel 3.5, I was eager to test drive
3.6-rc6, and found rc7 out already!
So yesterday I installed linux 3.6-rc7.towo.1-siduction-amd64, the
"wl" module compiles and installs, and loads okay upon boot to
3.6-rc7. However, I'm unable to associate to my AP:
Pointers in syslog
Sep 25 21:34:10 terra wpa_supplicant[2787]: nl80211: 'nl80211' generic
netlink not found
Sep 25 21:34:10 terra wpa_supplicant[2787]: Failed to initialize
driver 'nl80211'
[..snip]
Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Trying to associate
with 00:xx:xx:xx:xx:xx (SSID='xxxxxxx' freq=2452 MHz)
Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Association request
to the driver failed
As bcm43142 is fairly new, this proprietary driver is all that's there
to support it. Sad face.
Cheers,
Jasmine
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Arend van Spriel
Oct 1, 2012, 8:20:02 AM10/1/12
to
On 09/27/2012 04:24 PM, Jasmine Hassan wrote:
> Update on 3.6-rc7 problems with wpasupplicant-1.0-2 and broadcom-sta
> 6.20.55.19 (r300276)
> 1. Fails to associate to AP (WPA encryption used) when wl.ko built with wext
> 2. Kernel bug when wl.ko built with nl/cfg80211
Commenting on issue 1 only, here.
>> Updated deb: http://jas.gemnetworks.com/debian/wireless-bcm43142-dkms-6.20.55.19_amd64.deb
>>
>> Also tested on linux 3.5.0-4.dmz.1-liquorix-amd64, and it works for me
>>
>> Now, given a power regression in kernel 3.5, I was eager to test drive
>> 3.6-rc6, and found rc7 out already!
>> So yesterday I installed linux 3.6-rc7.towo.1-siduction-amd64, the
>> "wl" module compiles and installs, and loads okay upon boot to
>> 3.6-rc7. However, I'm unable to associate to my AP:
>>
>> Pointers in syslog
>> Sep 25 21:34:10 terra wpa_supplicant[2787]: nl80211: 'nl80211' generic
>> netlink not found
>> Sep 25 21:34:10 terra wpa_supplicant[2787]: Failed to initialize
>> driver 'nl80211'
>> [..snip]
Not sure what is snipped here. Your wpa_supplicant seems to try nl80211.
Maybe it goes and try WEXT instead, but that is missing from the log. Do
you recall or still have the entire syslog?
>> Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Trying to associate
>> with 00:xx:xx:xx:xx:xx (SSID='xxxxxxx' freq=2452 MHz)
>> Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Association request
>> to the driver failed
>>
>> As bcm43142 is fairly new, this proprietary driver is all that's there
>> to support it. Sad face.
>>
>> Cheers,
>> Jasmine
Gr. AvS
> Update on 3.6-rc7 problems with wpasupplicant-1.0-2 and broadcom-sta
> 6.20.55.19 (r300276)
> 1. Fails to associate to AP (WPA encryption used) when wl.ko built with wext
> 2. Kernel bug when wl.ko built with nl/cfg80211
Commenting on issue 1 only, here.
>> Updated deb: http://jas.gemnetworks.com/debian/wireless-bcm43142-dkms-6.20.55.19_amd64.deb
>>
>> Also tested on linux 3.5.0-4.dmz.1-liquorix-amd64, and it works for me
>>
>> Now, given a power regression in kernel 3.5, I was eager to test drive
>> 3.6-rc6, and found rc7 out already!
>> So yesterday I installed linux 3.6-rc7.towo.1-siduction-amd64, the
>> "wl" module compiles and installs, and loads okay upon boot to
>> 3.6-rc7. However, I'm unable to associate to my AP:
>>
>> Pointers in syslog
>> Sep 25 21:34:10 terra wpa_supplicant[2787]: nl80211: 'nl80211' generic
>> netlink not found
>> Sep 25 21:34:10 terra wpa_supplicant[2787]: Failed to initialize
>> driver 'nl80211'
>> [..snip]
Maybe it goes and try WEXT instead, but that is missing from the log. Do
you recall or still have the entire syslog?
>> Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Trying to associate
>> with 00:xx:xx:xx:xx:xx (SSID='xxxxxxx' freq=2452 MHz)
>> Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Association request
>> to the driver failed
>>
>> As bcm43142 is fairly new, this proprietary driver is all that's there
>> to support it. Sad face.
>>
>> Cheers,
>> Jasmine
Jasmine Hassan
Oct 1, 2012, 8:40:02 AM10/1/12
to
Resend. Sorry, forgot to "reply all" on the last 2 emails
because wpa_supplicant 1.0 (at least on LMDE/Debian testing) always
tries nl80211 first
# grep -i wext /etc/wpa_supplicant/*
/etc/wpa_supplicant/functions.sh:# -D driver backend ('wext' if none given)
/etc/wpa_supplicant/functions.sh:
WPA_SUP_OPTIONS="$WPA_SUP_OPTIONS
-D nl80211,wext"
/etc/wpa_supplicant/functions.sh:
wpa_msg stderr "using
\"nl80211,wext\" wpa-driver instead ..."
/etc/wpa_supplicant/functions.sh:
WPA_SUP_OPTIONS="$WPA_SUP_OPTIONS
-D nl80211,wext"
/etc/wpa_supplicant/functions.sh: wpa_msg verbose "wpa-driver
nl80211,wext (default)"
--
And to answer your other question, attached the complete snipped part
--
Jasmine
because wpa_supplicant 1.0 (at least on LMDE/Debian testing) always
tries nl80211 first
# grep -i wext /etc/wpa_supplicant/*
/etc/wpa_supplicant/functions.sh:# -D driver backend ('wext' if none given)
/etc/wpa_supplicant/functions.sh:
WPA_SUP_OPTIONS="$WPA_SUP_OPTIONS
-D nl80211,wext"
/etc/wpa_supplicant/functions.sh:
wpa_msg stderr "using
\"nl80211,wext\" wpa-driver instead ..."
/etc/wpa_supplicant/functions.sh:
WPA_SUP_OPTIONS="$WPA_SUP_OPTIONS
-D nl80211,wext"
/etc/wpa_supplicant/functions.sh: wpa_msg verbose "wpa-driver
nl80211,wext (default)"
--
And to answer your other question, attached the complete snipped part
--
Jasmine
Jasmine Hassan
Oct 1, 2012, 9:00:03 AM10/1/12
to
And because, the log you're referencing, begins with:
# wpa_supplicant -d -Dnl80211,wext -ieth2 -u -s -O /var/run/wpa_supplicant
I obviously ran it with the same -D option used in functions.sh:
nl80211,wext (in the same order). Pointless, of course, as I know that
the wl.ko module loaded at the time was built with wext only. I guess
I could've just as well ran with -
# wpa_supplicant -d -Dnl80211,wext -ieth2 -u -s -O /var/run/wpa_supplicant
I obviously ran it with the same -D option used in functions.sh:
nl80211,wext (in the same order). Pointless, of course, as I know that
the wl.ko module loaded at the time was built with wext only. I guess
I could've just as well ran with -
Jasmine Hassan
Oct 19, 2012, 12:30:02 PM10/19/12
to
Reposting updated link, as I'm getting emails about it. it's also
mentioned at the bottom of the homepage jas.gemnetworks.com :)
http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms/wireless-bcm43142-dkms_6.20.55.19~bdcom0602.0400.1000.0400-0somerville1_amd64.deb
Sorry about the long file name. forgot to rename dell's stupid
mile-long package name, and when re-importing in new repo, it got
renamed back to original name.
Apparently broadcom's linux driver page is still stuck at 5.100.82.112 :p
http://www.broadcom.com/support/802.11/linux_sta.php
Arend,
Anything you can do about the latter, at least?
Thanks,
Jas
mentioned at the bottom of the homepage jas.gemnetworks.com :)
http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms/wireless-bcm43142-dkms_6.20.55.19~bdcom0602.0400.1000.0400-0somerville1_amd64.deb
Sorry about the long file name. forgot to rename dell's stupid
mile-long package name, and when re-importing in new repo, it got
renamed back to original name.
Apparently broadcom's linux driver page is still stuck at 5.100.82.112 :p
http://www.broadcom.com/support/802.11/linux_sta.php
Arend,
Anything you can do about the latter, at least?
Thanks,
Jas
Jasmine Hassan
Oct 19, 2012, 3:00:01 PM10/19/12
to
Changed the long dell/oneiric package version back to short version, and fixed lintian warnings about incorrect file ownership with recent dpkg versions.
http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms_6.20.55.19_amd64.deb
--
N.B.:
I tried to contact the original package maintainer, "Hsin-Yi Chen (hychen)" <hyc...@canonical.com>, but the email bounced
Delivery to the following recipient failed permanently:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.1.1 <hyc...@canonical.com>: Recipient address rejected: User unknown in virtual alias table (state 13).
Arend van Spriel
Oct 19, 2012, 3:20:02 PM10/19/12
to
On 10/19/2012 08:53 PM, Jasmine Hassan wrote:
> Changed the long dell/oneiric package version back to short version, and
> fixed lintian warnings about incorrect file ownership with recent dpkg
> versions.
>
> http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms_6.20.55.19_amd64.deb
Getting 404 HTTP error on this link.
> Changed the long dell/oneiric package version back to short version, and
> fixed lintian warnings about incorrect file ownership with recent dpkg
> versions.
>
> http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms_6.20.55.19_amd64.deb
Jasmine Hassan
Oct 19, 2012, 3:20:03 PM10/19/12
to
Sorry about that, and thanks for replying.
http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms/wireless-bcm43142-dkms_6.20.55.19_amd64.deb
http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms/wireless-bcm43142-dkms_6.20.55.19_amd64.deb
Jasmine Hassan
Oct 22, 2012, 10:40:01 PM10/22/12
to
Hi,
When attempting to make an upstream tarball out of the dkms package,
similar to the upstream tarball of broadcom-sta-5.100.82.112, I
noticed the dkms pacakge only includes an x86_64 binary, so that
cannot replace the current broadcom-sta package (which has an i386
binary). So, I must separately maintain this amd64 driver for
bcm43142, on private repo, at least temporarily. Should I open an ITP?
First release (6.20.55.19-1) supporting all kernels 2.6.x up to and
including 3.6.x
- known issue: limited scan results on 3.6 compared to results on any
previous kernel. personally tested on 3.2, 3.4, 3.5, and 3.6
- debian packaging based on that of broadcom-sta's, maintaining copyright file
- all changes are logged in changelog, building on changelog of the
dkms oneiric package found on dells.
from changelog, for debian/patches:
- Make all patches compliant with dep3 format.
- Add 01-Makefile: Use cfg80211 on 3.x kernels, require amd64, cleanup
- Sync 02-license: Attribute Dan Baumann, update patch for 6.20.55.19
- Sync 03-rename-to-wlan0: Attribute Cyril Lacoux, refresh patch
- Add 04-linux-semaphore-include: patch all three headers that declare
semaphore structure and use semaphore functions (wl_iw.h, wl_linux.h,
and wl_cfg80211.h). See patch header for more details
- Rename 06-3.2.0 to 05-kernel_3.1_onwards.patch: Refresh, and update
the check to >= 3.1.0, because this is when ndo_set_multicast_list
was actually dropped, and not in 3.2.0
- Import 06-user_ioctl_reqs.patch with relevant code from #672677,
attribute Cyril Lacoux, and simplify rssi error handling & return
- Add 07-kernel_3.4_onwards: include asm/system.h iff kernel < 3.4
- Add 08-kernel_3.6_onwards: nl80211: move scan API to wdev
Through apt
=========
1. add key:
wget http://jas.gemnetworks.com/jasmineaura.gpg.key -O- | sudo apt-key add -
2. add to apt sources:
# /etc/apt/sources.list.d/wireless-bcm43142.list
deb http://jas.gemnetworks.com/debian debian main
deb-src http://jas.gemnetworks.com/debian debian main
3. install
# apt-get install wireless-bcm43142-dkms
or get source:
# apt-get source wireless-bcm43142-dkms
Directly
======
browse to http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142/
for dkms package:
wireless-bcm43142-dkms_6.20.55.19-1_amd64.deb 23-Oct-2012 01:44 1.3M
Imitation of a "clean" upstream source:
wireless-bcm43142_6.20.55.19.orig.tar.bz2 23-Oct-2012 01:45 1.1M
debian packaging (including patches)
wireless-bcm43142_6.20.55.19-1.debian.tar.gz 23-Oct-2012 01:44 12K
Best,
Jasmine
When attempting to make an upstream tarball out of the dkms package,
similar to the upstream tarball of broadcom-sta-5.100.82.112, I
noticed the dkms pacakge only includes an x86_64 binary, so that
cannot replace the current broadcom-sta package (which has an i386
binary). So, I must separately maintain this amd64 driver for
bcm43142, on private repo, at least temporarily. Should I open an ITP?
First release (6.20.55.19-1) supporting all kernels 2.6.x up to and
including 3.6.x
- known issue: limited scan results on 3.6 compared to results on any
previous kernel. personally tested on 3.2, 3.4, 3.5, and 3.6
- debian packaging based on that of broadcom-sta's, maintaining copyright file
- all changes are logged in changelog, building on changelog of the
dkms oneiric package found on dells.
from changelog, for debian/patches:
- Make all patches compliant with dep3 format.
- Add 01-Makefile: Use cfg80211 on 3.x kernels, require amd64, cleanup
- Sync 02-license: Attribute Dan Baumann, update patch for 6.20.55.19
- Sync 03-rename-to-wlan0: Attribute Cyril Lacoux, refresh patch
- Add 04-linux-semaphore-include: patch all three headers that declare
semaphore structure and use semaphore functions (wl_iw.h, wl_linux.h,
and wl_cfg80211.h). See patch header for more details
- Rename 06-3.2.0 to 05-kernel_3.1_onwards.patch: Refresh, and update
the check to >= 3.1.0, because this is when ndo_set_multicast_list
was actually dropped, and not in 3.2.0
- Import 06-user_ioctl_reqs.patch with relevant code from #672677,
attribute Cyril Lacoux, and simplify rssi error handling & return
- Add 07-kernel_3.4_onwards: include asm/system.h iff kernel < 3.4
- Add 08-kernel_3.6_onwards: nl80211: move scan API to wdev
Through apt
=========
1. add key:
wget http://jas.gemnetworks.com/jasmineaura.gpg.key -O- | sudo apt-key add -
2. add to apt sources:
# /etc/apt/sources.list.d/wireless-bcm43142.list
deb http://jas.gemnetworks.com/debian debian main
deb-src http://jas.gemnetworks.com/debian debian main
3. install
# apt-get install wireless-bcm43142-dkms
or get source:
# apt-get source wireless-bcm43142-dkms
Directly
======
browse to http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142/
for dkms package:
wireless-bcm43142-dkms_6.20.55.19-1_amd64.deb 23-Oct-2012 01:44 1.3M
Imitation of a "clean" upstream source:
wireless-bcm43142_6.20.55.19.orig.tar.bz2 23-Oct-2012 01:45 1.1M
debian packaging (including patches)
wireless-bcm43142_6.20.55.19-1.debian.tar.gz 23-Oct-2012 01:44 12K
Best,
Jasmine
Cyril Lacoux
Oct 26, 2012, 2:00:02 AM10/26/12
to
Le mardi 23 octobre 2012 06:34:06, Jasmine Hassan a écrit :
Hi,
> When attempting to make an upstream tarball out of the dkms package,
> similar to the upstream tarball of broadcom-sta-5.100.82.112, I
> noticed the dkms pacakge only includes an x86_64 binary, so that
> cannot replace the current broadcom-sta package (which has an i386
> binary). So, I must separately maintain this amd64 driver for
> bcm43142, on private repo, at least temporarily. Should I open an ITP?
I think you should not do that because this driver doesn't seem to be only for
Hi,
> When attempting to make an upstream tarball out of the dkms package,
> similar to the upstream tarball of broadcom-sta-5.100.82.112, I
> noticed the dkms pacakge only includes an x86_64 binary, so that
> cannot replace the current broadcom-sta package (which has an i386
> binary). So, I must separately maintain this amd64 driver for
> bcm43142, on private repo, at least temporarily. Should I open an ITP?
this chipset but an enhanced version of the broadcom-sta driver which support
recent chipsets (see attached diff, in particular wl_id_table declaration).
I'll be pleased to upload the new version of the broadcom-sta driver when it's
released (including i386 binary).
Anyway this can't be done before Wheezy release.
Cheers,
--
Cyril Lacoux
Jasmine Hassan
Oct 26, 2012, 7:00:01 AM10/26/12
to
Hi Cyril,
Thanks for replying
On Fri, Oct 26, 2012 at 7:38 AM, Cyril Lacoux <cla...@easter-eggs.com> wrote:
> I think you should not do that because this driver doesn't seem to be only for
> this chipset but an enhanced version of the broadcom-sta driver which support
> recent chipsets (see attached diff, in particular wl_id_table declaration).
Yes, I sure have noticed, because I wanted to update the readme file
of original broadcom-wl when repacking a tarball.
It's funny how even PCI_VENDOR_ID_BROADCOM was replaced with PCI_ANY_ID.
> I'll be pleased to upload the new version of the broadcom-sta driver when it's
> released (including i386 binary).
Unfortunately, I doubt that will happen anytime soon, if at all. After
failing to get any reply from broadcom linux-sta driver support, I
contacted brcm80211 developers to ask if the linux-sta driver page
could be updated with a tarball release of this driver, and an attempt
to answer my request was simply:
"This driver version was a Dell-specific release, which they can
redistribute. However, 5.100.82.112 on our internet page is our latest
generic release."
>
> Anyway this can't be done before Wheezy release.
>
Nods. I keep forgetting about the "freeze period".
Thanks a bunch.
> Cheers,
> --
> Cyril Lacoux
Cheers,
Thanks for replying
On Fri, Oct 26, 2012 at 7:38 AM, Cyril Lacoux <cla...@easter-eggs.com> wrote:
> I think you should not do that because this driver doesn't seem to be only for
> this chipset but an enhanced version of the broadcom-sta driver which support
> recent chipsets (see attached diff, in particular wl_id_table declaration).
of original broadcom-wl when repacking a tarball.
It's funny how even PCI_VENDOR_ID_BROADCOM was replaced with PCI_ANY_ID.
> I'll be pleased to upload the new version of the broadcom-sta driver when it's
> released (including i386 binary).
failing to get any reply from broadcom linux-sta driver support, I
contacted brcm80211 developers to ask if the linux-sta driver page
could be updated with a tarball release of this driver, and an attempt
to answer my request was simply:
"This driver version was a Dell-specific release, which they can
redistribute. However, 5.100.82.112 on our internet page is our latest
generic release."
>
> Anyway this can't be done before Wheezy release.
>
Thanks a bunch.
> Cheers,
> --
> Cyril Lacoux
Cheers,
0 new messages