linux-stable.git/drivers/net/wireless, branch linux-2.6.19.y

prism54: correct assignment of DOT1XENABLE in WE-19 codepaths

2007-02-24T00:24:27+00:00

Correct assignment of DOT1XENABLE in WE-19 codepaths.
RX_UNENCRYPTED_EAPOL = 1 really means setting DOT1XENABLE _off_, and
vice versa.  The original WE-19 patch erroneously reversed that.  This
patch fixes association with unencrypted and WEP networks when using
wpa_supplicant.

It also adds two missing break statements that, left out, could result
in incorrect card configuration.

Applies to (I think) 2.6.19 and later.

Signed-off-by: Dan Williams 
Signed-off-by: Greg Kroah-Hartman

bcm43xx: Fix for oops on ampdu status

2007-02-24T00:24:26+00:00

If bcm43xx were to process an afterburner (ampdu) status response, Linux would oops. The
ampdu and intermediate status bits are properly named.

Signed-off-by: Michael Buesch 
Signed-off-by: Larry Finger 
Signed-off-by: Greg Kroah-Hartman

bcm43xx: Fix for oops on resume

2007-02-24T00:24:26+00:00

There is a kernel oops on bcm43xx when resuming due to an overly tight timeout loop.

Signed-off-by: Larry Finger
Signed-off-by: Greg Kroah-Hartman

[PATCH] zd1211rw: Call ieee80211_rx in tasklet

2007-01-10T19:05:20+00:00

The driver called ieee80211_rx in hardware interrupt context.  This has
been against the intention of the ieee80211_rx function.  It caused a bug
in the crypto routines used by WPA.  This patch calls ieee80211_rx in a
tasklet.

Signed-off-by: Ulrich Kunitz 
Signed-off-by: Andrew Morton 
Signed-off-by: John W. Linville 
Signed-off-by: Chris Wright

[PATCH] Revert "[PATCH] zd1211rw: Removed unneeded packed attributes"

2007-01-10T19:05:18+00:00

This reverts commit 4e1bbd846d00a245dcf78b6b331d8a9afed8e6d7.

Quoth Daniel Drake :

"A user reported that commit 4e1bbd846d00a245dcf78b6b331d8a9afed8e6d7
(Remove unneeded packed attributes) breaks the zd1211rw driver on ARM."

Signed-off-by: John W. Linville 
Signed-off-by: Chris Wright

[PATCH] bcm43xx: Add error checking in bcm43xx_sprom_write()

2006-11-08T01:05:07+00:00

The Coverity checker noted that these "if (err)"'s couldn't ever be
true.

It seems the intention was to check the return values of the
bcm43xx_pci_write_config32()'s?

Signed-off-by: Adrian Bunk 
Signed-off-by: Larry Finger 
Signed-off-by: Michael Buesch 
Signed-off-by: John W. Linville

[PATCH] bcm43xx: Drain TX status before starting IRQs

2006-11-08T01:05:06+00:00

Drain the Microcode TX-status-FIFO before we enable IRQs.
This is required, because the FIFO may still have entries left
from a previous run. Those would immediately fire after enabling
IRQs and would lead to an oops in the DMA TXstatus handling code.

Signed-off-by: Michael Buesch 
Signed-off-by: Larry Finger 
Signed-off-by: John W. Linville

[PATCH] bcm43xx: fix unexpected LED control values in BCM4303 sprom

2006-11-01T03:15:41+00:00

The bcm43xx driver uses 4 locations in the devices sprom to determine
the behavior of the leds. Certain defaults are assigned if all bits are
set in those locations. On at least one BCM4303 chip, the sprom contains
values other than the default, which executes an assertion placed in the
default case of a following switch statement. This patch makes the leds
on the above mentioned interface behave correctly. In addition, it limits
the number of logged messages to 20 for the case of unexpected values in
the sprom locations.

Signed-off-by: Larry Finger 
Signed-off-by: John W. Linville

[PATCH] bcm43xx: Fix low-traffic netdev watchdog TX timeouts

2006-11-01T03:15:40+00:00

This fixes a netdev watchdog timeout problem.
The software needs to call netif_tx_disable before running the
hardware calibration code. The problem condition can be shown by the
following timegraph.

|---5secs - ~10 jiffies time---|---|OOPS
^                              ^
last real TX                   periodic work stops netif

At OOPS, the following happens:
The watchdog timer triggers, because the timeout of 5secs
is over. The watchdog first checks for stopped TX.
_Usually_ TX is only stopped from the TX handler to indicate
a full TX queue. But this is different. We need to stop TX here,
regardless of the TX queue state. So the watchdog recognizes
the stopped device and assumes it is stopped due to full
TX queues (Which is a _wrong_ assumption in this case). It then
tests how far the last TX has been in the past. If it's more than
5secs (which is the case for low or no traffic), it will fire
a TX timeout.

Signed-off-by: Michael Buesch 
Signed-off-by: Larry Finger 
Signed-off-by: John W. Linville

[PATCH] hostap_plx: fix CIS verification

2006-11-01T03:15:39+00:00

The length of the manfid CIS should be at least 4, and it's normally 4.
It's incorrect to require it to be at least 5.  This breaks support for
most (if not all) cards.

The right place to ensure that we don't access beyond the CIS buffer is
to strengthen another check.  Make sure that the next tuple begins at
least at the CIS buffer end (in which case we stop processing) or
before that.

Reported by ph35sm@free.fr

Signed-off-by: Pavel Roskin 
Signed-off-by: John W. Linville