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

bcm43xx: Fix problem with >1 GB RAM

2007-03-13T18:26:46+00:00

Some versions of the bcm43xx chips only support 30-bit DMA, which means
that the descriptors and buffers must be in the first 1 GB of RAM. On
the i386 and x86_64 architectures with more than 1 GB RAM, an incorrect
assignment may occur. This patch ensures that the various DMA addresses
are within the capability of the chip. Testing has been limited to x86_64
as no one has an i386 system with more than 1 GB RAM.

Signed-off-by: Larry Finger 
Signed-off-by: John W. Linville 
Cc: Chuck Ebbert 
Signed-off-by: Greg Kroah-Hartman

bcm43xx: Fix assertion failures in interrupt handler

2007-03-09T18:50:24+00:00

In the bcm43xx interrupt handler, sanity checks are wrongly done before the
verification that the interrupt is for the bcm43xx.

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

bcm43xx: fix for 4309

2007-03-09T18:50:23+00:00

BCM4309 devices aren't working properly as A PHYs aren't supported yet, but
we probe 802.11a cores anyway. This fixes it, while still allowing for A PHY code
to be developed in the future.

Signed-off-by: Stefano Brivio 
Cc: Michael Buesch 
Signed-off-by: Greg Kroah-Hartman

bcm43xx: Fix for oops on ampdu status

2007-03-09T18:50:18+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-03-09T18:50:18+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

prism54: correct assignment of DOT1XENABLE in WE-19 codepaths

2007-03-09T18:50:17+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

[PATCH] bcm43xx: Fix failure to deliver PCI-E interrupts

2007-01-18T09:29:23+00:00

The PCI-E modifications to bcm43xx do not set up the interrupt vector
correctly. Tested with BCM4311 (PCI-E) on x86_64 and BCM4306 (PCI) on i386.

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

[PATCH] PCMCIA: fix drivers broken by recent cleanup

2007-01-12T02:24:39+00:00

Setting .ConfigBase and .Present is now done at the pcmcia core.

The driver cleanup missed a few places where the driver did set .Present
to PRESENT_OPTION and later to the values from the CIS.  Setting to
PRESENT_OPTION now overrides the values from the CIS.  So just remove
those lines.

Signed-off-by: Daniel Ritz 
Signed-off-by: Dominik Brodowski 
Signed-off-by: Linus Torvalds

[PATCH] ipw2100: Fix dropping fragmented small packet problem

2007-01-03T01:56:26+00:00

The rx_data.header struct is ieee80211_hdr_4addr. If a wireless frame uses
ieee80211_hdr_3addr header and is less than 6 bytes, it will be discarded.
This is not likely going to happen for normal packets (since there is TCP, IP
headers). But if fragmentation is used, there will be such small trailing
packets. And they will be lost for ever.

Signed-off-by: Zhu Yi 
Signed-off-by: John W. Linville

[PATCH] zd1211rw: Call ieee80211_rx in tasklet

2006-12-19T21:09:59+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