linux.git/drivers/net/wireless, branch v3.4-rc6

wl1251: fix crash on remove due to leftover work item

2012-04-27T19:25:25+00:00

This driver currently leaves elp_work behind when stopping, which
occasionally results in data corruption because work function ends
up accessing freed memory, typical symptoms of this are various
worker_thread crashes. Fix it by cancelling elp_work.

Cc: stable@vger.kernel.org # v2.6.37+
Signed-off-by: Grazvydas Ignotas 
Signed-off-by: John W. Linville

wl1251: fix crash on remove due to premature kfree

2012-04-27T19:25:25+00:00

Currently SDIO glue frees it's own structure before calling
wl1251_free_hw(), which in turn calls ieee80211_unregister_hw().
The later call may result in a need to communicate with the chip
to stop it (as it happens now if the interface is still up before
rmmod), which means calls are made back to the glue, resulting in
freed memory access.

Fix this by freeing glue data last.

Cc: stable@vger.kernel.org # v2.6.37+
Signed-off-by: Grazvydas Ignotas 
Signed-off-by: John W. Linville

b43: only reload config after successful initialization

2012-04-27T19:25:25+00:00

Commit 2a19032 (b43: reload phy and bss settings after core restarts)
introduced an unconditional call to b43_op_config() at the end of
b43_op_start(). When firmware fails to load this can wedge the system.
There's no need to reload the configuration after a failed
initialization anyway, so only make the call if initialization was
successful.

BugLink: http://bugs.launchpad.net/bugs/950295
Cc: Felix Fietkau 
Cc: 
Signed-off-by: Seth Forshee 
Signed-off-by: John W. Linville

iwlwifi: use 6000G2B for 6030 device series

2012-04-27T19:25:24+00:00

"iwlwifi: use correct released ucode version" change
the ucode api ok from 6000G2 to 6000G2B, but it shall belong
to 6030 device series, not the 6005 device series. Fix it

Cc: stable@vger.kernel.org #3.3+
Signed-off-by: Wey-Yi Guy 
Signed-off-by: John W. Linville

ath5k: add missing iounmap to AHB probe removal

2012-04-27T19:24:07+00:00

When our driver device is removed on the AHB bus, our IO memory is never unmapped.

Signed-off-by: Jonathan Bither 
Reviewed-by: Pavel Roskin 
Signed-off-by: John W. Linville

brcm80211: fmac: fix missing completion events issue

2012-04-27T19:20:39+00:00

dpc takes care of all data packets transmissions for sdio function
2. It is possible that it misses some completion events when the
traffic is heavy or it's running on a slow cpu. A linked list is
introduced to make sure dpc is invoked whenever needed.

Reviewed-by: Pieter-Paul Giesberts 
Reviewed-by: Arend van Spriel 
Signed-off-by: Franky Lin 
Signed-off-by: John W. Linville

brcm80211: fmac: fix SDIO function 0 register r/w issue

2012-04-27T19:20:39+00:00

SDIO stack doesn't have a structure for function 0. The structure
pointer stored in card->sdio_func[0] is actually for function 1.
With current implementation the register read/write is applied to
function 1. This pathch fixes the issue.

Reviewed-by: Pieter-Paul Giesberts 
Reviewed-by: Arend van Spriel 
Reviewed-by: Florian Fainelli 
Reviewed-by: Johannes Berg 
Signed-off-by: Franky Lin 
Signed-off-by: John W. Linville

iwlwifi: use correct released ucode version

2012-04-24T18:25:26+00:00

Report correctly the latest released version
of the iwlwifi firmware for all
iwlwifi-supported devices.

Cc: stable@vger.kernel.org #3.3+
Signed-off-by: Meenakshi Venkataraman 
Signed-off-by: Wey-Yi Guy 
Signed-off-by: John W. Linville

iwlwifi: fix hardware queue programming

2012-04-24T18:14:55+00:00

Newer devices have 20 (5000 series) or 30 (6000 series)
hardware queues, rather than the 16 that 4965 had. This
was added to the driver a long time ago, but improperly:
the queue registers for the higher queues aren't just
continuations of the registers for the first 16 queues,
they are in other places. Therefore, the hardware would
lock up when trying to activate queue 16 or above and
the device would have to be restarted.

Thanks goes to Emmanuel who identified this and told me
how the queue programming should be done.

Note that we don't use queues 20 and higher today and
doing so needs more work than this.

Cc: stable@vger.kernel.org
Signed-off-by: Johannes Berg 
Signed-off-by: Wey-Yi Guy 
Signed-off-by: John W. Linville

brcmsmac: "INTERMEDIATE but not AMPDU" only when tracing

2012-04-23T18:57:53+00:00

I keep getting the following messages on the log buffer:
[ 2167.097507] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but not AMPDU
[ 2281.331305] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but not AMPDU
[ 2281.332539] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but not AMPDU
[ 2329.876605] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but not AMPDU
[ 2329.877354] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but not AMPDU
[ 2462.280756] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but not AMPDU
[ 2615.651689] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but not AMPDU

From the code comment I understand that this something that can -
and does, quite frequently - happen.

Signed-off-by: Eldad Zack 
Acked-by: Franky Lin
Signed-off-by: John W. Linville