- 10 Jul, 2009 40 commits
-
-
Bob Copeland authored
Enable the "Content" After Beacon queue and utilize it to send any buffered frames for power-saving clients. Signed-off-by:
Bob Copeland <me@bobcopeland.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Christian Lamparter authored
This patch removes some dead code: p54spi.c:115: warning: ‘p54spi_read16’ defined but not used and while we're at it, p54spi_registers_array is purged as well. Signed-off-by:
Christian Lamparter <chunkeey@web.de> Signed-off-by:
-
Christian Lamparter authored
This patch fixes all CHECK_ENDIAN complains: 1. p54/fwio.c:296:6: warning: restricted __le32 degrades to integer p54/fwio.c:296:6: warning: restricted __le32 degrades to integer 2. p54/p54spi.c:172:32: warning: incorrect type in initializer p54spi.c:172:32: expected restricted __le32 [usertype] buffer p54/p54spi.c:172:32: got unsigned int Signed-off-by: -
Samuel Ortiz authored
When connecting to an ESSID manually, we may not set the BSSID, and thus wdev->wext.connect.bssid will be NULL. wdev->current_bss is always updated when a connection is established so we should check it first. Signed-off-by:
Samuel Ortiz <samuel.ortiz@intel.com> Acked-by:
Johannes Berg <johannes@sipsolutions.net> Signed-off-by:
-
Ivo van Doorn authored
Remove the input_polldev from rt2x00 and replace it with the rfkill interface offered by the wiphy structure. This simplifies the entire rfkill handling in rt2x00 and allows us to remove the CONFIG_RT2X00_LIB_RFKILL option and always enables rfkill capabilities. Signed-off-by:
Ivo van Doorn <IvDoorn@gmail.com> Signed-off-by:
-
Johannes Berg authored
According to the documentation, the limit is 0x3f == 63, not 64. Signed-off-by:
-
Helmut Schaa authored
mac80211's software scan implementation uses a passive dwell time of (HZ / 5) which means we stay 200ms on each passive channel. Compared to iwlwifi's hw scan and the old ipw* drivers which use values around 120ms this is quite long. Reducing the passive dwell time from 200ms to 125ms should save us something around a second on cards capable of 11a and we should still be able to catch beacons from most access points (assuming a ~100ms beacon interval). Signed-off-by:
Helmut Schaa <helmut.schaa@googlemail.com> Signed-off-by:
-
Jiri Slaby authored
Don't allow users to open debugfs files, because it can cause oopses. When a user opens some file, driver unlinks it and frees the corresponding structure, we will dereference freed memory. Signed-off-by:
Jiri Slaby <jirislaby@gmail.com> Signed-off-by:
-
Jiri Slaby authored
Don't allow users to open debugfs files, because it can cause oopses. When a user opens some file, driver unlinks it and frees the corresponding structure, we will dereference freed memory. Signed-off-by:
-
Joe Perches authored
Signed-off-by:
Joe Perches <joe@perches.com> Signed-off-by:
-
Reinette Chatre authored
We want to see the buffer contents when the error occurs without needing to set any debug flags. Signed-off-by:
Reinette Chatre <reinette.chatre@intel.com> Signed-off-by:
-
Reinette Chatre authored
Signed-off-by:
-
Reinette Chatre authored
The register locking rework addressed the problem where nic access was obtained incorrectly when PS is enabled. Signed-off-by:
-
Zhu Yi authored
The patch removes B0 hardware support. Nobody is using it anyway. Signed-off-by:
Zhu Yi <yi.zhu@intel.com> Signed-off-by:
-
Zhu Yi authored
The patch simplifies calibration map by combining the init_calib_map and periodic_calib_map into one calib_map in struct iwm_conf. Now the initial calibration map is stored in the lower 16 bits of calib_map and the periodic calibration map is stored in the higher 16 bits. Signed-off-by:
-
Zhu Yi authored
The patch uses netif_rx_ni() over netif_rx() to post buffers to upper network code because it is always scheduled in a workqueue. The problem was first observed from a dynamic ticks warning: "NOHZ: local_softirq_pending ..." Signed-off-by: -
Joe Perches authored
Signed-off-by:
-
Senthil Balasubramanian authored
This patch fixes an issue when the TX and RX streams are different. Signed-off-by:
Senthil Balasubramanian <senthilkumar@atheros.com> Signed-off-by:
-
Senthil Balasubramanian authored
ANI calibration shouldn't be done when we are not on our home channel. This is already verified. However, it is racy. Fix this by proper spin locks. Signed-off-by:
-
Senthil Balasubramanian authored
ANI is not required when the STA is disconnected. So stop it and enable ANI for adhoc and monitor mode. Signed-off-by:
-
Senthil Balasubramanian authored
Remove unncessary STATION mode check in ath9k_bss_assoc_info() as it is called only for STATION mode. Signed-off-by:
-
Christian Lamparter authored
Modify the remaining p54 files to account for the new file organization. Signed-off-by:
Larry Finger <Larry.Finger@lwfinger.net> Signed-off-by:
-
Christian Lamparter authored
Copy the TX/RX code from p54common.c into a new file txrx.c Signed-off-by:
-
Christian Lamparter authored
Copy the mac80211 glue code from p54common.c into a new file main.c Signed-off-by:
-
Christian Lamparter authored
Copy the LMAC Interface specific definitions from p54common.h into a new file lmac.h Signed-off-by:
-
Christian Lamparter authored
Copy the LED code from p54common.c into a new file led.c Signed-off-by:
-
Christian Lamparter authored
Copy the firmware i/o code from p54common.c into a new file fwio.c Signed-off-by:
-
Christian Lamparter authored
Copy the eeprom code from p54common.h into a new file eeprom.h Signed-off-by:
-
Christian Lamparter authored
Copy the eeprom code from p54common.c into a new file eeprom.c Signed-off-by:
-
Roel Kluin authored
bufsize and remainder are unsigned. When negative they are wrapped and caught by the other test. Signed-off-by:
Roel Kluin <roel.kluin@gmail.com> Signed-off-by:
Pavel Roskin <proski@gnu.org> Signed-off-by:
-
Christian Lamparter authored
This patch slightly optimizes p54_rx_data's stack and code size. Signed-off-by:
-
Christian Lamparter authored
Andrey Yurovsky reported that the driver forwarded erroneously the parent device structure instead of the real thing, which of course led to some dodgy sysfs links (at least?). Signed-off-by:
-
Tomas Winkler authored
This patch unifies setup_rxon_timing funcions of AGN and 3945. HWs differ only in supported maximal beacon interval. This is reflected in hw_paras.max_beacon_itrvl Signed-off-by:
Tomas Winkler <tomas.winkler@intel.com> Signed-off-by:
-
Johannes Berg authored
When userspace requests only certain channels to be scanned, we currently ignore that request entirely. Signed-off-by:
-
Johannes Berg authored
There really is no reason to be assigning txq->swq_id all the time, once at aggregation setup is sufficient. Signed-off-by:
-
Tomas Winkler authored
Each HW supported by iwlwifi is capable of hardware crypto so drop this flag from hw_params structure. Signed-off-by:
-
Mohamed Abbas authored
Hardware may be ready for us to manage it without us trying to prepare it first. Check if this is the case. Signed-off-by:
Mohamed Abbas <mohamed.abbas@intel.com> Signed-off-by:
-
Luis R. Rodriguez authored
We were not differentiating quality between legacy and HT configurations. We change this to consider the differences. New theory for reporting quality: At a hardware RSSI of 45 you will be able to use MCS 7 reliably. At a hardware RSSI of 45 you will be able to use MCS 15 reliably. At a hardware RSSI of 35 you should be able use 54 Mbps reliably. MCS 7 is the highets MCS index usable by a 1-stream device. MCS 15 is the highest MCS index usable by a 2-stream device. All ath9k devices are either 1-stream or 2-stream. How many bars you see is derived from the qual reporting. A more elaborate scheme can be used here but it requires tables of SNR/throughput for each possible mode used. For the MCS table you can refer to the wireless wiki: http://wireless.kernel.org/en/developers/Documentation/ieee80211/802.11n This should fix this bug report: http://bugzilla.kernel.org/show_bug.cgi?id=13537 Cc: Janath.Peiris@atheros.com Cc: Matt.Smith@atheros.com Signed-off-by:
Luis R. Rodriguez <lrodriguez@atheros.com> Signed-off-by:
-
Andrey Yurovsky authored
The SDIO driver sets the surpriseremoved flag before calling lbs_remove_card. With IEEE PS enabled, lbs_remove_card must issue a command to exit IEEE PS mode, however with that flag set the command path is blocked and the card is never taken out of IEEE PS mode. This step is required to ensure that the driver can be reloaded. This patch moves the setting of surpriseremoved after lbs_remove_card is called. Tested with V9 firmware by ensuring that IEEE PS is disabled when the driver is removed. Reloading the driver is not fully tested due to a separate issue with module reload in the SDIO driver, however this patch at least leaves the card in a better state when we bring the driver down. Signed-off-by:
Andrey Yurovsky <andrey@cozybit.com> Acked-by:
Dan Williams <dcbw@redhat.com> Signed-off-by:
-
Andrey Yurovsky authored
The SPI driver does a couple of card cleanup steps in the wrong order on module removal. If IEEE PS is enabled, this results in the card being left in IEEE PS mode and subsequent failures to reload the module. The problem is that the surpriseremoved flag is set before calling lbs_remove_card, but that function needs to issue a command to exit IEEE PS mode (the flag blocks the command path). In addition, lbs_stop_card should be called first because it clears out any pending commands. Tested on a GSPI device with V9 firmware by confirming that we can reload the module with or without IEEE PS enabled. Also fix a warning from the wrong uint format in a printk. V2: use z modifier, thanks Sebastian. Signed-off-by:
-
