kernel/linux.git/drivers/net/wireless, branch linux-2.6.18.y

bcm43xx: Fix for oops on ampdu status

2007-02-23T23:49:51+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-23T23:49:51+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] bcm43xx: Drain TX status before starting IRQs

2006-12-02T00:12:36+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. Cc: "John W. Linville" Signed-off-by: Michael Buesch Signed-off-by: Larry Finger Signed-off-by: Chris Wright

[PATCH] bcm43xx: fix watchdog timeouts.

2006-11-04T01:33:46+00:00

This fixes a netdev watchdog timeout problem. The problem is caused by a needed netif_tx_disable in the hardware calibration code and 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. Acked-by: John W. Linville Signed-off-by: Michael Buesch Signed-off-by: Larry Finger Signed-off-by: Greg Kroah-Hartman Signed-off-by: Chris Wright

bcm43xx: fix regressions in 2.6.18

2006-10-13T20:23:28+00:00

The bcm43xx code in 2.6.18 has a serious problems not found in 2.6.17, due to a change in the locking mechanism introduced to reduce latency. The following patch fixes the problems in locking, reduces the latency associated with the periodic work tasklet, and contains code needed for those cards that use 64-bit DMA. Signed-off-by: Larry Finger Signed-off-by: Greg Kroah-Hartman

zd1211rw: ZD1211B ASIC/FWT, not jointly decoder

2006-10-13T20:23:21+00:00

The vendor driver chooses this value based on an ifndef ASIC, and ASIC is never defined. Signed-off-by: Daniel Drake Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman

[PATCH] zd1211rw: Fix of signal strength and quality measurement

2006-09-11T20:11:08+00:00

Caused by a documentation issue I mixed up fields of the zd_status structure. This patch fixes it and improves also the average computation, which is now using only measurements of packets sent by the access point. Signed-off-by: Ulrich Kunitz Signed-off-by: Daniel Drake Signed-off-by: John W. Linville

[STRIP]: Fix neighbour table refcount leak.

2006-08-30T04:22:19+00:00

Found by inspection. The STRIP driver does neigh_lookup() but never releases. This driver shouldn't being doing gratuitous arp anyway. Untested, obviously, because of lack of hardware. Signed-off-by: Stephen Hemminger Signed-off-by: David S. Miller

[PATCH] hostap: Restore antenna selection settings after port reset

2006-08-23T18:20:37+00:00

Intersil firmware 1.7.4 (and possibly others) loses the antenna selection settings when the port is reset. Signed-off-by: David Acker Signed-off-by: Pavel Roskin Signed-off-by: John W. Linville

[PATCH] spectrum_cs: Fix incorrect use of pcmcia_dev_present()

2006-08-23T18:20:37+00:00

This bug was introduced during the PCMCIA API conversion and broke spectrum_cs completely. Tracked down by Fredrik Tolf Signed-off-by: Pavel Roskin Signed-off-by: John W. Linville