* Compat-wireless release for 2010-07-01 is baked
From: Compat-wireless cronjob account @ 2010-07-01 19:02 UTC (permalink / raw)
To: linux-wireless
>From git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
85e0e99..a348d8b history -> origin/history
+ 7a6353a...fb4cbff master -> origin/master (forced update)
* [new tag] next-20100701 -> next-20100701
cat: /var/opt/compat/compat-wireless-2.6/compat_version: No such file or directory
cat: compat_base_tree: No such file or directory
cat: compat_base_tree_version: No such file or directory
cat: compat_version: No such file or directory
cat: /var/opt/compat/compat-wireless-2.6/compat_version: No such file or directory
scripts/Makefile.clean:17: /var/opt/compat/compat-wireless-2.6/drivers/net/wireless/hostap/Makefile: No such file or directory
make[4]: *** No rule to make target `/var/opt/compat/compat-wireless-2.6/drivers/net/wireless/hostap/Makefile'. Stop.
make[3]: *** [/var/opt/compat/compat-wireless-2.6/drivers/net/wireless/hostap] Error 2
make[2]: *** [/var/opt/compat/compat-wireless-2.6/drivers/net/wireless] Error 2
make[1]: *** [_clean_/var/opt/compat/compat-wireless-2.6] Error 2
make: *** [clean] Error 2
/usr/bin/sha1sum: *.tar.bz2: No such file or directory
compat-wireless code metrics
494454 - Total upstream lines of code being pulled
^ permalink raw reply
* pull request: wireless-next-2.6 2010-07-01
From: John W. Linville @ 2010-07-01 18:15 UTC (permalink / raw)
To: davem; +Cc: linux-wireless, netdev, linux-kernel
David,
Two weeks since the last request, plenty of new stuff intended for
2.6.36...
Included are the usual bunch of driver updates, including a big
dump from the rt2x00 team. This also includes cfg80211 support
for libertas, a flurry of (mostly trivial) stuff from me, and a
wireless-2.6 pull to resolve some patch dependencies.
Please let me know if there are problems!
Thanks,
John
---
The following changes since commit ea812ca1b06113597adcd8e70c0f84a413d97544:
Alexander Duyck (1):
x86: Align skb w/ start of cacheline on newer core 2/Xeon Arch
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git master
Bruno Randolf (1):
ath5k: fix antenna div gc for <= AR5K_SREV_PHY_2413
Daniel Halperin (1):
iwlwifi: update LQ for bcast station on channel change
Felix Fietkau (3):
ath9k: fix retry count for A-MPDU rate control status reports
mac80211: fix the for_each_sta_info macro
ath9k: fix TSF after reset on AR913x
Gertjan van Wingerde (10):
mac80211: Fix compile warning in scan.c.
rt2x00: Fix frame dumping for USB devices.
rt2x00: Move filling of TX URB to rt2x00usb_kick_tx_entry function.
rt2x00: Merge PCI and USB versions of write_tx_data into single function.
rt2x00: Move common txdone handling to rt2x00lib_txdone.
rt2x00: Rename driver write_tx_datadesc callback function.
rt2x00: Split of TXWI writing to write_tx_data callback in rt2800usb.
eeprom_93cx6: Add support for 93c86 EEPROMs.
rt2x00: Correctly detect 93C86 EEPROMs in rt2800pci.
rt2x00: Align rt2800 EEPROM validation to Ralink vendor driver.
Helmut Schaa (6):
rt2x00: Implement tx mpdu aggregation
rt2x00: Fix beacon updates in rt2800pci
rt2x00: Fix beacon updates in rt61pci
rt2x00: Disable link tuning in AP mode
rt2x00: fix beacon reset on rt2800
mac82011: Allow selection of minstrel_ht as default rc algorithm
Ivo van Doorn (7):
rt2x00: Write the BSSID to register when interface is added
rt2x00: Remove unneeded variable
rt2x00: Enable multiBSS in rt2800
rt2x00: Fix IEEE80211_HT_CAP_RX_STBC assignment
rt2x00: Fix antenna initialization
rt2x00: Always set BBP_CSR_CFG_BBP_RW_MODE to 1
rt2x00: Fix compile warning when debug disabled
Jay Sternberg (1):
iwlwifi: display ucode SW Error in hex
Johannes Berg (7):
mac80211_hwsim: fix fake_hw_scan
mac80211: fix sw scan bracketing
iwlagn: use mutex for aggregation
iwlwifi: use sync commands for keys
iwlwifi: return ucode errors from station management
iwlwifi: fix multicast
iwlwifi: read rfkill during resume
John W. Linville (14):
libertas: mark lbs_ret_802_11d_domain_info static
ath9k: declare MODULE_FIRMWARE for ath9k_htc
rtl8180: mark rtl8180_beacon_work static
mac80211: don't shadow mgmt variable in ieee80211_rx_h_action
minstrel_ht: make *idx unsigned in minstrel_downgrade_rate
wireless: mark reg_mutex as static
minstrel_ht: move minstrel_mcs_groups declaration to header file
mac80211: avoid scheduling while atomic in mesh_rx_plink_frame
mac80211: use netif_receive_skb in ieee80211_rx callpath
mac80211: use netif_receive_skb in ieee80211_tx_status callpath
mac80211: remove unnecessary check in ieee80211_dump_survey
mac80211: add basic tracing to drv_get_survey
ath9k: remove unused function ath9k_hw_keyisvalid
ath9k: make ath9k_hw_keysetmac static
Justin P. Mattock (2):
wireless:hostap_main.c warning: variable 'iface' set but not used
wireless:hostap_ap.c Fix warning: variable 'fc' set but not used
Juuso Oikarinen (3):
mac80211: Add interface for driver to temporarily disable dynamic ps
cfg80211/mac80211: Update set_tx_power to use mBm instead of dBm units
nl80211: Add option to adjust transmit power
Kiran Divekar (3):
Libertas: cfg80211 support
Libertas: fix WARN_ON issues in cfg80211 support
Libertas: Added 11d support using cfg80211
Larry Finger (1):
b43: Clarify logged message after fatal DMA error and switch to PIO mode
Luis R. Rodriguez (5):
ath9k_hw: fix ASPM setting for AR9003
ath9k_hw: move LowPower array writes to ar9003_hw_configpcipowersave()
ath9k_hw: add pcieSerDesWrite to disable SERDES ASPM tweaks
ath9k_hw: dynamically choose the SERDES array for low power
ath9k_hw: add an extra delay when reseting AR_RTC_RESET
Magnus Damm (1):
b43: Add SDIO_DEVICE() for EW-CG1102GC
Ondrej Zary (1):
rt2500usb: fallback to SW encryption for TKIP+AES
Reinette Chatre (2):
Merge branch 'wireless-2.6' into wireless-next-2.6
iwlagn: reduce severity of disconnected antennas warning
Sebastian Smolorz (2):
at76c50x-usb: Move function at76_join() several lines up
at76c50x-usb: Extract bssid from authentication frame
Sujith (2):
ath9k_htc: Update supported product list
ath9k_htc: Add LED support for AR7010
Uwe Kleine-König (2):
cfg80211: move cfg80211_exit to .exit.text
wireless: move regulatory_init to .init.text
Vasanthakumar Thiagarajan (4):
ath9k: Fix bug in starting ani
ath9k: Fix bug in paprd
ath9k: Remove unused paprd_txok
ath9k: Wakeup the chip in an appropriate place in ath_paprd_calibrate()
Vivek Natarajan (1):
ath9k: Add a module parameter to disable led blinking.
Wey-Yi Guy (11):
iwlwifi: move agn specific rx related code to iwl-agn-rx.c
iwlwifi: move _agn statistics related structure
iwlwifi: move calibration from iwlcore to iwlagn
iwlwifi: code cleanup to remove un-necessary "goto"
iwlwifi: remove non-exist reference
iwlwifi: set TX_CMD_FLAG_PROT_REQUIRE_MSK in tx_flag
iwlwifi: name change from signal protection flag
iwlwifi: enable DC calibration based on config parameter
iwlwifi: add a mechanism to disable plcp error checking
iwlwifi: turn on RTS/CTS after aggregation become operational
iwlwifi: add disable rf calibration support for 6000g2a and 6000g2b
Documentation/networking/README.ipw2200 | 2 +-
drivers/net/b44.c | 144 +-
drivers/net/wireless/at76c50x-usb.c | 108 +-
drivers/net/wireless/at76c50x-usb.h | 1 +
drivers/net/wireless/ath/ath5k/Makefile | 1 +
drivers/net/wireless/ath/ath5k/ani.c | 20 +-
drivers/net/wireless/ath/ath5k/ath5k.h | 19 +-
drivers/net/wireless/ath/ath5k/attach.c | 2 -
drivers/net/wireless/ath/ath5k/base.c | 373 ++--
drivers/net/wireless/ath/ath5k/caps.c | 7 -
drivers/net/wireless/ath/ath5k/debug.c | 79 +-
drivers/net/wireless/ath/ath5k/debug.h | 9 +-
drivers/net/wireless/ath/ath5k/desc.c | 152 +-
drivers/net/wireless/ath/ath5k/desc.h | 310 ++--
drivers/net/wireless/ath/ath5k/dma.c | 13 -
drivers/net/wireless/ath/ath5k/eeprom.c | 3 +-
drivers/net/wireless/ath/ath5k/gpio.c | 7 -
drivers/net/wireless/ath/ath5k/pcu.c | 24 -
drivers/net/wireless/ath/ath5k/phy.c | 82 +-
drivers/net/wireless/ath/ath5k/qcu.c | 9 -
drivers/net/wireless/ath/ath5k/reset.c | 64 +-
drivers/net/wireless/ath/ath5k/sysfs.c | 116 +
drivers/net/wireless/ath/ath9k/Makefile | 3 +-
drivers/net/wireless/ath/ath9k/ani.c | 743 ++++++-
drivers/net/wireless/ath/ath9k/ani.h | 78 +-
drivers/net/wireless/ath/ath9k/ar5008_phy.c | 372 +++-
drivers/net/wireless/ath/ath9k/ar9002_hw.c | 118 +-
drivers/net/wireless/ath/ath9k/ar9002_initvals.h | 6 +-
drivers/net/wireless/ath/ath9k/ar9002_phy.h | 7 +
.../{ar9003_initvals.h => ar9003_2p0_initvals.h} | 254 ++--
.../{ar9003_initvals.h => ar9003_2p2_initvals.h} | 433 ++--
drivers/net/wireless/ath/ath9k/ar9003_calib.c | 10 +-
drivers/net/wireless/ath/ath9k/ar9003_eeprom.c | 13 +-
drivers/net/wireless/ath/ath9k/ar9003_eeprom.h | 4 +-
drivers/net/wireless/ath/ath9k/ar9003_hw.c | 185 ++-
drivers/net/wireless/ath/ath9k/ar9003_mac.c | 13 +
drivers/net/wireless/ath/ath9k/ar9003_mac.h | 5 +
drivers/net/wireless/ath/ath9k/ar9003_paprd.c | 714 ++++++
drivers/net/wireless/ath/ath9k/ar9003_phy.c | 513 ++++-
drivers/net/wireless/ath/ath9k/ar9003_phy.h | 298 ++-
drivers/net/wireless/ath/ath9k/ath9k.h | 89 +-
drivers/net/wireless/ath/ath9k/beacon.c | 3 +-
drivers/net/wireless/ath/ath9k/common.c | 314 +---
drivers/net/wireless/ath/ath9k/common.h | 77 +-
drivers/net/wireless/ath/ath9k/debug.c | 68 +-
drivers/net/wireless/ath/ath9k/debug.h | 2 +
drivers/net/wireless/ath/ath9k/eeprom.c | 29 +
drivers/net/wireless/ath/ath9k/eeprom.h | 5 +-
drivers/net/wireless/ath/ath9k/eeprom_4k.c | 1 +
drivers/net/wireless/ath/ath9k/eeprom_9287.c | 618 +++---
drivers/net/wireless/ath/ath9k/eeprom_def.c | 1 +
drivers/net/wireless/ath/ath9k/gpio.c | 9 +-
drivers/net/wireless/ath/ath9k/hif_usb.c | 71 +-
drivers/net/wireless/ath/ath9k/hif_usb.h | 2 +
drivers/net/wireless/ath/ath9k/htc.h | 38 +-
drivers/net/wireless/ath/ath9k/htc_drv_beacon.c | 23 +
drivers/net/wireless/ath/ath9k/htc_drv_init.c | 163 +-
drivers/net/wireless/ath/ath9k/htc_drv_main.c | 493 +++--
drivers/net/wireless/ath/ath9k/htc_drv_txrx.c | 86 +-
drivers/net/wireless/ath/ath9k/htc_hst.c | 3 +-
drivers/net/wireless/ath/ath9k/hw-ops.h | 16 +
drivers/net/wireless/ath/ath9k/hw.c | 304 ++--
drivers/net/wireless/ath/ath9k/hw.h | 100 +-
drivers/net/wireless/ath/ath9k/init.c | 58 +-
drivers/net/wireless/ath/ath9k/mac.c | 14 +-
drivers/net/wireless/ath/ath9k/mac.h | 13 +-
drivers/net/wireless/ath/ath9k/main.c | 427 ++---
drivers/net/wireless/ath/ath9k/pci.c | 1 +
drivers/net/wireless/ath/ath9k/rc.c | 184 +-
drivers/net/wireless/ath/ath9k/recv.c | 296 +++-
drivers/net/wireless/ath/ath9k/reg.h | 90 +-
drivers/net/wireless/ath/ath9k/virtual.c | 2 +-
drivers/net/wireless/ath/ath9k/wmi.c | 3 -
drivers/net/wireless/ath/ath9k/xmit.c | 161 +-
drivers/net/wireless/b43/dma.c | 69 +-
drivers/net/wireless/b43/main.c | 2 +-
drivers/net/wireless/b43/sdio.c | 1 +
drivers/net/wireless/b43legacy/dma.c | 49 +-
drivers/net/wireless/hostap/hostap_ap.c | 3 +-
drivers/net/wireless/hostap/hostap_main.c | 2 -
drivers/net/wireless/ipw2x00/ipw2100.c | 18 +-
drivers/net/wireless/ipw2x00/ipw2200.c | 7 +-
drivers/net/wireless/iwlwifi/Kconfig | 6 +-
drivers/net/wireless/iwlwifi/Makefile | 4 +-
drivers/net/wireless/iwlwifi/iwl-1000.c | 5 +
drivers/net/wireless/iwlwifi/iwl-3945-debugfs.c | 28 +-
drivers/net/wireless/iwlwifi/iwl-3945.c | 208 +--
drivers/net/wireless/iwlwifi/iwl-4965.c | 96 +-
drivers/net/wireless/iwlwifi/iwl-5000.c | 67 +-
drivers/net/wireless/iwlwifi/iwl-6000.c | 487 +++--
.../iwlwifi/{iwl-calib.c => iwl-agn-calib.c} | 26 +-
drivers/net/wireless/iwlwifi/iwl-agn-debugfs.c | 91 +-
drivers/net/wireless/iwlwifi/iwl-agn-hcmd.c | 32 +-
drivers/net/wireless/iwlwifi/iwl-agn-lib.c | 233 +--
drivers/net/wireless/iwlwifi/iwl-agn-rs.c | 20 +-
drivers/net/wireless/iwlwifi/iwl-agn-rx.c | 284 +++
drivers/net/wireless/iwlwifi/iwl-agn-tx.c | 82 +-
drivers/net/wireless/iwlwifi/iwl-agn-ucode.c | 123 +
drivers/net/wireless/iwlwifi/iwl-agn.c | 392 +++-
drivers/net/wireless/iwlwifi/iwl-agn.h | 44 +
drivers/net/wireless/iwlwifi/iwl-commands.h | 35 +-
drivers/net/wireless/iwlwifi/iwl-core.c | 288 +--
drivers/net/wireless/iwlwifi/iwl-core.h | 35 +-
drivers/net/wireless/iwlwifi/iwl-debugfs.c | 92 +-
drivers/net/wireless/iwlwifi/iwl-dev.h | 95 +-
drivers/net/wireless/iwlwifi/iwl-eeprom.c | 3 +
drivers/net/wireless/iwlwifi/iwl-helpers.h | 27 +
drivers/net/wireless/iwlwifi/iwl-rx.c | 242 +--
drivers/net/wireless/iwlwifi/iwl-scan.c | 49 +-
drivers/net/wireless/iwlwifi/iwl-sta.c | 164 +-
drivers/net/wireless/iwlwifi/iwl-sta.h | 32 +-
drivers/net/wireless/iwlwifi/iwl-tx.c | 33 +-
drivers/net/wireless/iwlwifi/iwl3945-base.c | 138 +-
drivers/net/wireless/iwmc3200wifi/cfg80211.c | 12 +-
drivers/net/wireless/iwmc3200wifi/hal.c | 2 +-
drivers/net/wireless/iwmc3200wifi/rx.c | 4 +-
drivers/net/wireless/libertas/Makefile | 3 -
drivers/net/wireless/libertas/assoc.c | 2264 -------------------
drivers/net/wireless/libertas/assoc.h | 155 --
drivers/net/wireless/libertas/cfg.c | 2038 +++++++++++++++++-
drivers/net/wireless/libertas/cfg.h | 21 +-
drivers/net/wireless/libertas/cmd.c | 124 +-
drivers/net/wireless/libertas/cmdresp.c | 111 +-
drivers/net/wireless/libertas/debugfs.c | 54 +-
drivers/net/wireless/libertas/decl.h | 10 +-
drivers/net/wireless/libertas/dev.h | 68 +-
drivers/net/wireless/libertas/ethtool.c | 29 +-
drivers/net/wireless/libertas/host.h | 28 +-
drivers/net/wireless/libertas/if_sdio.c | 58 +
drivers/net/wireless/libertas/if_usb.c | 12 +-
drivers/net/wireless/libertas/main.c | 305 +--
drivers/net/wireless/libertas/mesh.c | 6 +-
drivers/net/wireless/libertas/mesh.h | 5 -
drivers/net/wireless/libertas/rx.c | 121 +-
drivers/net/wireless/libertas/scan.c | 1354 -----------
drivers/net/wireless/libertas/scan.h | 63 -
drivers/net/wireless/libertas/tx.c | 12 +-
drivers/net/wireless/libertas/wext.c | 2353 --------------------
drivers/net/wireless/libertas/wext.h | 17 -
drivers/net/wireless/libertas_tf/if_usb.c | 5 +-
drivers/net/wireless/mac80211_hwsim.c | 5 +
drivers/net/wireless/mwl8k.c | 12 +-
drivers/net/wireless/orinoco/hermes_dld.c | 2 +-
drivers/net/wireless/orinoco/orinoco_usb.c | 4 +-
drivers/net/wireless/orinoco/wext.c | 4 +-
drivers/net/wireless/p54/eeprom.c | 4 +-
drivers/net/wireless/p54/p54spi.c | 5 +-
drivers/net/wireless/p54/p54usb.c | 6 +-
drivers/net/wireless/prism54/isl_ioctl.c | 11 +-
drivers/net/wireless/rndis_wlan.c | 56 +-
drivers/net/wireless/rt2x00/rt2400pci.c | 16 +-
drivers/net/wireless/rt2x00/rt2500pci.c | 16 +-
drivers/net/wireless/rt2x00/rt2500usb.c | 40 +-
drivers/net/wireless/rt2x00/rt2800.h | 57 +-
drivers/net/wireless/rt2x00/rt2800lib.c | 314 ++-
drivers/net/wireless/rt2x00/rt2800lib.h | 13 +-
drivers/net/wireless/rt2x00/rt2800pci.c | 151 +-
drivers/net/wireless/rt2x00/rt2800pci.h | 19 -
drivers/net/wireless/rt2x00/rt2800usb.c | 119 +-
drivers/net/wireless/rt2x00/rt2800usb.h | 37 -
drivers/net/wireless/rt2x00/rt2x00.h | 44 +-
drivers/net/wireless/rt2x00/rt2x00config.c | 12 +-
drivers/net/wireless/rt2x00/rt2x00debug.c | 1 +
drivers/net/wireless/rt2x00/rt2x00dev.c | 43 +-
drivers/net/wireless/rt2x00/rt2x00dump.h | 7 +-
drivers/net/wireless/rt2x00/rt2x00ht.c | 47 +-
drivers/net/wireless/rt2x00/rt2x00lib.h | 26 +-
drivers/net/wireless/rt2x00/rt2x00link.c | 8 +-
drivers/net/wireless/rt2x00/rt2x00mac.c | 10 +-
drivers/net/wireless/rt2x00/rt2x00pci.c | 33 +-
drivers/net/wireless/rt2x00/rt2x00pci.h | 10 -
drivers/net/wireless/rt2x00/rt2x00queue.c | 86 +-
drivers/net/wireless/rt2x00/rt2x00queue.h | 9 +-
drivers/net/wireless/rt2x00/rt2x00usb.c | 68 +-
drivers/net/wireless/rt2x00/rt2x00usb.h | 29 -
drivers/net/wireless/rt2x00/rt61pci.c | 62 +-
drivers/net/wireless/rt2x00/rt73usb.c | 52 +-
drivers/net/wireless/rtl818x/rtl8180_dev.c | 2 +-
drivers/net/wireless/wl12xx/Kconfig | 4 +-
drivers/net/wireless/wl12xx/wl1251_main.c | 4 +-
drivers/net/wireless/wl12xx/wl1251_sdio.c | 40 +-
drivers/net/wireless/wl12xx/wl1271.h | 31 +-
drivers/net/wireless/wl12xx/wl1271_cmd.c | 41 +-
drivers/net/wireless/wl12xx/wl1271_cmd.h | 28 +-
drivers/net/wireless/wl12xx/wl1271_event.c | 10 +-
drivers/net/wireless/wl12xx/wl1271_ini.h | 123 +
drivers/net/wireless/wl12xx/wl1271_main.c | 95 +-
drivers/net/wireless/wl12xx/wl1271_sdio.c | 2 +-
drivers/net/wireless/wl12xx/wl1271_testmode.c | 11 +-
drivers/net/wireless/wl12xx/wl1271_tx.c | 36 +-
drivers/net/wireless/wl12xx/wl1271_tx.h | 1 +
drivers/net/wireless/zd1211rw/zd_mac.c | 5 +-
drivers/net/wireless/zd1211rw/zd_mac.h | 3 +-
drivers/net/wireless/zd1211rw/zd_usb.c | 2 +-
drivers/ssb/driver_chipcommon.c | 25 +
drivers/ssb/driver_chipcommon_pmu.c | 17 +-
drivers/ssb/main.c | 76 +-
drivers/ssb/pci.c | 15 +-
include/linux/eeprom_93cx6.h | 1 +
include/linux/nl80211.h | 24 +-
include/linux/ssb/ssb.h | 159 +--
include/net/cfg80211.h | 137 +-
include/net/mac80211.h | 120 +-
net/mac80211/Kconfig | 8 +
net/mac80211/Makefile | 4 +
net/mac80211/agg-rx.c | 123 +-
net/mac80211/agg-tx.c | 554 +++--
net/mac80211/cfg.c | 100 +-
net/mac80211/debugfs.c | 154 +-
net/mac80211/debugfs_key.c | 2 +-
net/mac80211/debugfs_sta.c | 65 +-
net/mac80211/driver-ops.h | 102 +-
net/mac80211/driver-trace.h | 210 +-
net/mac80211/ht.c | 50 +-
net/mac80211/ibss.c | 109 +-
net/mac80211/ieee80211_i.h | 73 +-
net/mac80211/iface.c | 188 ++-
net/mac80211/key.c | 290 +--
net/mac80211/key.h | 30 +-
net/mac80211/main.c | 116 +-
net/mac80211/mesh.c | 73 +-
net/mac80211/mesh.h | 2 -
net/mac80211/mesh_hwmp.c | 4 +-
net/mac80211/mesh_pathtbl.c | 4 +-
net/mac80211/mesh_plink.c | 42 +-
net/mac80211/mlme.c | 239 +--
net/mac80211/pm.c | 18 +-
net/mac80211/rate.h | 13 +
net/mac80211/rc80211_minstrel_ht.c | 825 +++++++
net/mac80211/rc80211_minstrel_ht.h | 130 ++
net/mac80211/rc80211_minstrel_ht_debugfs.c | 118 +
net/mac80211/rx.c | 193 +-
net/mac80211/scan.c | 6 +-
net/mac80211/sta_info.c | 22 +-
net/mac80211/sta_info.h | 113 +-
net/mac80211/status.c | 6 +-
net/mac80211/tx.c | 93 +-
net/mac80211/util.c | 31 +-
net/mac80211/work.c | 2 +-
net/mac80211/wpa.c | 8 +-
net/wireless/chan.c | 5 +-
net/wireless/core.c | 2 +-
net/wireless/core.h | 1 +
net/wireless/mlme.c | 8 +-
net/wireless/nl80211.c | 89 +-
net/wireless/reg.c | 6 +-
net/wireless/reg.h | 2 +-
net/wireless/wext-compat.c | 10 +-
248 files changed, 14685 insertions(+), 13932 deletions(-)
create mode 100644 drivers/net/wireless/ath/ath5k/sysfs.c
copy drivers/net/wireless/ath/ath9k/{ar9003_initvals.h => ar9003_2p0_initvals.h} (87%)
rename drivers/net/wireless/ath/ath9k/{ar9003_initvals.h => ar9003_2p2_initvals.h} (78%)
create mode 100644 drivers/net/wireless/ath/ath9k/ar9003_paprd.c
rename drivers/net/wireless/iwlwifi/{iwl-calib.c => iwl-agn-calib.c} (98%)
create mode 100644 drivers/net/wireless/iwlwifi/iwl-agn-rx.c
delete mode 100644 drivers/net/wireless/libertas/assoc.c
delete mode 100644 drivers/net/wireless/libertas/assoc.h
delete mode 100644 drivers/net/wireless/libertas/scan.c
delete mode 100644 drivers/net/wireless/libertas/scan.h
delete mode 100644 drivers/net/wireless/libertas/wext.c
delete mode 100644 drivers/net/wireless/libertas/wext.h
create mode 100644 drivers/net/wireless/wl12xx/wl1271_ini.h
create mode 100644 net/mac80211/rc80211_minstrel_ht.c
create mode 100644 net/mac80211/rc80211_minstrel_ht.h
create mode 100644 net/mac80211/rc80211_minstrel_ht_debugfs.c
Omnibus patch available here:
http://www.kernel.org/pub/linux/kernel/people/linville/wireless-next-2.6-2010-07-01.patch.bz2
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* [PATCH 2.6.34] mac80211: Fix auth retries if AP sends temporary deauth
From: Paul Stewart @ 2010-07-01 17:21 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless, Michael Wu, Jiri Benc, John W. Linville
This bypasses destruction of BSS state if a temporary DEAUTH packet is
received while performing an AUTH. This will allow the retry mechanism
(which runs regardless of this patch) to succeed, since we do not remove
the BSS state which is required to complete authentication on the client
side in cfg80211_send_rx_auth().
The specific case handled here is "Previous authentication no longer
valid", which is usually generated by an AP if the AP still has saved
state of the STA being authenticated. Usually a retry will be successful.
Signed-off-by: Paul Stewart <pstew@google.com>
---
net/mac80211/work.c | 21 ++++++++++++++++++++-
1 files changed, 20 insertions(+), 1 deletions(-)
diff --git a/net/mac80211/work.c b/net/mac80211/work.c
index 15e1ba9..800929e 100644
--- a/net/mac80211/work.c
+++ b/net/mac80211/work.c
@@ -1006,7 +1006,7 @@ ieee80211_rx_result
ieee80211_work_rx_mgmt(struct ieee80211_sub_if_data *sdata,
struct ieee80211_local *local = sdata->local;
struct ieee80211_mgmt *mgmt;
struct ieee80211_work *wk;
- u16 fc;
+ u16 fc, reason_code;
if (skb->len < 24)
return RX_DROP_MONITOR;
@@ -1030,6 +1030,25 @@ ieee80211_rx_result
ieee80211_work_rx_mgmt(struct ieee80211_sub_if_data *sdata,
skb_queue_tail(&local->work_skb_queue, skb);
ieee80211_queue_work(&local->hw, &local->work_work);
return RX_QUEUED;
+ case IEEE80211_STYPE_DEAUTH:
+ /*
+ * If we get sent a DEAUTH while we are
+ * actively trying to authenticate to this
+ * station, we shoot ourselves in the foot if
+ * we fall through using RX_CONTINUE and allow
+ * the bss context to disappear
+ * (ieee80211_sta_rx_mgmt()). This is
+ * especially true if the reason for the
+ * DEAUTH was a negative but temporary direct
+ * response to an AUTH attempt. Let the retry
+ * mechanism run its course instead.
+ */
+ reason_code = le16_to_cpu(mgmt->u.deauth.reason_code);
+ if (wk->type == IEEE80211_WORK_AUTH &&
+ reason_code == WLAN_REASON_PREV_AUTH_NOT_VALID) {
+ return RX_DROP_MONITOR;
+ }
+ break;
}
}
^ permalink raw reply related
* ath: Fix uninitialized variable warnings [v2]
From: Prarit Bhargava @ 2010-07-01 16:09 UTC (permalink / raw)
To: linux-wireless, ath9k-devel, linville, proski; +Cc: Prarit Bhargava
Fix 'make CONFIG_DEBUG_SECTION_MISMATCH=y' warning:
drivers/net/wireless/mwl8k.c: In function 'mwl8k_bss_info_changed_sta':
drivers/net/wireless/mwl8k.c:3404: warning: 'ap_legacy_rates' may be used uninitialized in this function
drivers/net/wireless/ath/ath9k/eeprom_4k.c: In function 'ath9k_hw_get_4k_gain_boundaries_pdadcs.clone.1':
drivers/net/wireless/ath/ath9k/eeprom_4k.c:310: warning: 'minPwrT4' may be used uninitialized in this function
drivers/net/wireless/ath/ath9k/eeprom_def.c: In function 'ath9k_hw_get_def_gain_boundaries_pdadcs.clone.0':
drivers/net/wireless/ath/ath9k/eeprom_def.c:677: warning: 'minPwrT4' may be used uninitialized in this function
drivers/net/wireless/ath/ath9k/eeprom_9287.c: In function 'ath9k_hw_get_AR9287_gain_boundaries_pdadcs':
drivers/net/wireless/ath/ath9k/eeprom_9287.c:301: warning: 'minPwrT4' may be used uninitialized in this function
Pavel pointed out that tMinCalPower or pMinCalPower isn't used anywhere, so
the simplest way to fix these warnings is to get rid of the code.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
diff --git a/drivers/net/wireless/ath/ath9k/eeprom_4k.c b/drivers/net/wireless/ath/ath9k/eeprom_4k.c
index 41a77d1..393f8c5 100644
--- a/drivers/net/wireless/ath/ath9k/eeprom_4k.c
+++ b/drivers/net/wireless/ath/ath9k/eeprom_4k.c
@@ -222,7 +222,7 @@ static void ath9k_hw_get_4k_gain_boundaries_pdadcs(struct ath_hw *ah,
struct ath9k_channel *chan,
struct cal_data_per_freq_4k *pRawDataSet,
u8 *bChans, u16 availPiers,
- u16 tPdGainOverlap, int16_t *pMinCalPower,
+ u16 tPdGainOverlap,
u16 *pPdGainBoundaries, u8 *pPDADCValues,
u16 numXpdGains)
{
@@ -307,8 +307,6 @@ static void ath9k_hw_get_4k_gain_boundaries_pdadcs(struct ath_hw *ah,
}
}
- *pMinCalPower = (int16_t)(minPwrT4[0] / 2);
-
k = 0;
for (i = 0; i < numXpdGains; i++) {
@@ -398,7 +396,6 @@ static void ath9k_hw_set_4k_power_cal_table(struct ath_hw *ah,
static u8 pdadcValues[AR5416_NUM_PDADC_VALUES];
u16 gainBoundaries[AR5416_EEP4K_PD_GAINS_IN_MASK];
u16 numPiers, i, j;
- int16_t tMinCalPower;
u16 numXpdGain, xpdMask;
u16 xpdGainValues[AR5416_EEP4K_NUM_PD_GAINS] = { 0, 0 };
u32 reg32, regOffset, regChainOffset;
@@ -451,7 +448,7 @@ static void ath9k_hw_set_4k_power_cal_table(struct ath_hw *ah,
ath9k_hw_get_4k_gain_boundaries_pdadcs(ah, chan,
pRawDataset, pCalBChans,
numPiers, pdGainOverlap_t2,
- &tMinCalPower, gainBoundaries,
+ gainBoundaries,
pdadcValues, numXpdGain);
ENABLE_REGWRITE_BUFFER(ah);
diff --git a/drivers/net/wireless/ath/ath9k/eeprom_9287.c b/drivers/net/wireless/ath/ath9k/eeprom_9287.c
index b471db5..6d6b1c5 100644
--- a/drivers/net/wireless/ath/ath9k/eeprom_9287.c
+++ b/drivers/net/wireless/ath/ath9k/eeprom_9287.c
@@ -219,7 +219,7 @@ static void ath9k_hw_get_AR9287_gain_boundaries_pdadcs(struct ath_hw *ah,
struct ath9k_channel *chan,
struct cal_data_per_freq_ar9287 *pRawDataSet,
u8 *bChans, u16 availPiers,
- u16 tPdGainOverlap, int16_t *pMinCalPower,
+ u16 tPdGainOverlap,
u16 *pPdGainBoundaries, u8 *pPDADCValues,
u16 numXpdGains)
{
@@ -298,7 +298,6 @@ static void ath9k_hw_get_AR9287_gain_boundaries_pdadcs(struct ath_hw *ah,
}
}
}
- *pMinCalPower = (int16_t)(minPwrT4[0] / 2);
k = 0;
for (i = 0; i < numXpdGains; i++) {
@@ -448,7 +447,6 @@ static void ath9k_hw_set_AR9287_power_cal_table(struct ath_hw *ah,
u8 pdadcValues[AR9287_NUM_PDADC_VALUES];
u16 gainBoundaries[AR9287_PD_GAINS_IN_MASK];
u16 numPiers = 0, i, j;
- int16_t tMinCalPower;
u16 numXpdGain, xpdMask;
u16 xpdGainValues[AR9287_NUM_PD_GAINS] = {0, 0, 0, 0};
u32 reg32, regOffset, regChainOffset;
@@ -514,7 +512,7 @@ static void ath9k_hw_set_AR9287_power_cal_table(struct ath_hw *ah,
ah, chan, pRawDataset,
pCalBChans, numPiers,
pdGainOverlap_t2,
- &tMinCalPower, gainBoundaries,
+ gainBoundaries,
pdadcValues, numXpdGain);
}
diff --git a/drivers/net/wireless/ath/ath9k/eeprom_def.c b/drivers/net/wireless/ath/ath9k/eeprom_def.c
index 7e1ed78..6ff2742 100644
--- a/drivers/net/wireless/ath/ath9k/eeprom_def.c
+++ b/drivers/net/wireless/ath/ath9k/eeprom_def.c
@@ -593,7 +593,7 @@ static void ath9k_hw_get_def_gain_boundaries_pdadcs(struct ath_hw *ah,
struct ath9k_channel *chan,
struct cal_data_per_freq *pRawDataSet,
u8 *bChans, u16 availPiers,
- u16 tPdGainOverlap, int16_t *pMinCalPower,
+ u16 tPdGainOverlap,
u16 *pPdGainBoundaries, u8 *pPDADCValues,
u16 numXpdGains)
{
@@ -674,8 +674,6 @@ static void ath9k_hw_get_def_gain_boundaries_pdadcs(struct ath_hw *ah,
}
}
- *pMinCalPower = (int16_t)(minPwrT4[0] / 2);
-
k = 0;
for (i = 0; i < numXpdGains; i++) {
@@ -837,7 +835,7 @@ static void ath9k_hw_set_def_power_cal_table(struct ath_hw *ah,
static u8 pdadcValues[AR5416_NUM_PDADC_VALUES];
u16 gainBoundaries[AR5416_PD_GAINS_IN_MASK];
u16 numPiers, i, j;
- int16_t tMinCalPower, diff = 0;
+ int16_t diff = 0;
u16 numXpdGain, xpdMask;
u16 xpdGainValues[AR5416_NUM_PD_GAINS] = { 0, 0, 0, 0 };
u32 reg32, regOffset, regChainOffset;
@@ -922,7 +920,6 @@ static void ath9k_hw_set_def_power_cal_table(struct ath_hw *ah,
chan, pRawDataset,
pCalBChans, numPiers,
pdGainOverlap_t2,
- &tMinCalPower,
gainBoundaries,
pdadcValues,
numXpdGain);
^ permalink raw reply related
* Re: rfkill failure in 2.6.35-rc3+
From: reinette chatre @ 2010-07-01 15:59 UTC (permalink / raw)
To: Andrew Lutomirski; +Cc: linux-wireless@vger.kernel.org, ilw@linux.intel.com
In-Reply-To: <AANLkTikqJzkFFtmOowq-OzzDFSC9_1SFuAfT4UGZBhqW@mail.gmail.com>
On Wed, 2010-06-30 at 19:59 -0700, Andrew Lutomirski wrote:
> I just toggled rfkill on and back off on my X200s (WiFi Link 5350, rev
> 0x24) and the link didn't come up. Toggling rfkill again didn't fix
> it, but rmmod + modprobe did.
>
> dmesg said:
>
> [13629.424869] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
> [13629.432761] iwlagn 0000:03:00.0: Not sending command - RF KILL
> [13629.432771] iwlagn 0000:03:00.0: Error sending REPLY_RXON:
> enqueue_hcmd failed: -5
> [13629.432778] iwlagn 0000:03:00.0: Error setting new RXON (-5)
> [13631.268646] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
> [13631.311232] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [13675.710821] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
> [13675.713438] iwlagn 0000:03:00.0: Not sending command - RF KILL
> [13675.713448] iwlagn 0000:03:00.0: Error sending REPLY_RXON:
> enqueue_hcmd failed: -5
> [13675.713455] iwlagn 0000:03:00.0: Error setting new RXON (-5)
> [13683.090789] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
> [13683.145267] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> This is 2.6.35-rc3+ with firmware 8.24.2.12. I've never seen this before.
Recently we have seen a few issues with rfkill state changes not being
seen by the driver. In all cases it was "resolved" by unloading (or not
loading from the beginning via blacklisting) of the platform driver. Can
you try that?
Reinette
^ permalink raw reply
* iwlwifi and 802.11s
From: Iuri Diniz @ 2010-07-01 15:29 UTC (permalink / raw)
To: linux-wireless
Is possible to add mesh support to iwlwifi (I have a intel wireless
4965AGN hardware) ?
if so, where can I get start?
is this information
http://linuxwireless.org/en/developers/Documentation/mac80211/API
sufficient?
thanks in advance.
--
Iuri Diniz
http://iuridiniz.com [Sou um agitador, não um advogado]
http://blog.igdium.com [Linux on Limbo]
^ permalink raw reply
* [PATCH] minstrel_ht: fix check for downgrading of top2 rate
From: tom.leiming @ 2010-07-01 15:19 UTC (permalink / raw)
To: nbd; +Cc: linux-wireless, linville, Ming Lei
From: Ming Lei <tom.leiming@gmail.com>
The check should be against current top2 rate, instead of
current top rate.
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
---
net/mac80211/rc80211_minstrel_ht.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/mac80211/rc80211_minstrel_ht.c b/net/mac80211/rc80211_minstrel_ht.c
index 8fba6f4..b5ace24 100644
--- a/net/mac80211/rc80211_minstrel_ht.c
+++ b/net/mac80211/rc80211_minstrel_ht.c
@@ -443,8 +443,8 @@ minstrel_ht_tx_status(void *priv, struct ieee80211_supported_band *sband,
minstrel_downgrade_rate(mi, &mi->max_tp_rate, true);
rate2 = minstrel_get_ratestats(mi, mi->max_tp_rate2);
- if (rate->attempts > 30 &&
- MINSTREL_FRAC(rate->success, rate->attempts) <
+ if (rate2->attempts > 30 &&
+ MINSTREL_FRAC(rate2->success, rate2->attempts) <
MINSTREL_FRAC(20, 100))
minstrel_downgrade_rate(mi, &mi->max_tp_rate2, false);
--
1.6.2.5
^ permalink raw reply related
* [PATCH] minstrel_ht: fix updating rate with best probability
From: tom.leiming @ 2010-07-01 15:18 UTC (permalink / raw)
To: nbd; +Cc: linux-wireless, linville, Ming Lei
From: Ming Lei <tom.leiming@gmail.com>
The throughput should be considered when updating rate
with best probability.
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
---
net/mac80211/rc80211_minstrel_ht.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/net/mac80211/rc80211_minstrel_ht.c b/net/mac80211/rc80211_minstrel_ht.c
index 52c8503..8fba6f4 100644
--- a/net/mac80211/rc80211_minstrel_ht.c
+++ b/net/mac80211/rc80211_minstrel_ht.c
@@ -240,6 +240,7 @@ minstrel_ht_update_stats(struct minstrel_priv *mp, struct minstrel_ht_sta *mi)
MINSTREL_FRAC(3, 4)) || mr->probability > cur_prob) {
mg->max_prob_rate = index;
cur_prob = mr->probability;
+ cur_prob_tp = mr->cur_tp;
}
if (mr->cur_tp > cur_tp) {
@@ -275,6 +276,7 @@ minstrel_ht_update_stats(struct minstrel_priv *mp, struct minstrel_ht_sta *mi)
minstrel_mcs_groups[group].streams == 1) {
mi->max_prob_rate = mg->max_prob_rate;
cur_prob = mr->cur_prob;
+ cur_prob_tp = mr->cur_tp;
}
mr = minstrel_get_ratestats(mi, mg->max_tp_rate);
--
1.6.2.5
^ permalink raw reply related
* Re: [PATCH 1/2] mac80211: Dont allow to wake up netif tx queues while on off channel
From: Vasanthakumar Thiagarajan @ 2010-07-01 9:34 UTC (permalink / raw)
To: johannes; +Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
In-Reply-To: <20100630104715.GA2192@vasanth-laptop>
On Wed, Jun 30, 2010 at 04:17:15PM +0530, Vasanth Thiagarajan wrote:
> On Wed, Jun 30, 2010 at 03:47:06PM +0530, Johannes Berg wrote:
> > On Wed, 2010-06-30 at 03:15 -0700, Vasanthakumar Thiagarajan wrote:
> > > Drivers are not supposed to call ieee80211_wake_queue() while operating
> > > on off channel during sw scanning, but there is no clear way for
> > > the driver to know that it is operating on off channel during scanning.
> > > There are cases (unavailablity/availability of tx buffers in ath9k, for
> > > example) where driver needs to stop/restart tx queues during background
> > > scanning state, this might result in waking up the corresponding netif
> > > tx queue when the device is on off channel which is not desired. This
> > > patches fixes this by checking SCAN_OFF_CHANNEL bit in scanning before
> > > restarting the tx queue.
> > >
> > > Signed-off-by: Vasanthakumar Thiagarajan <vasanth@atheros.com>
> > > ---
> > > net/mac80211/util.c | 3 ++-
> > > 1 files changed, 2 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/net/mac80211/util.c b/net/mac80211/util.c
> > > index a54cf14..1938a67 100644
> > > --- a/net/mac80211/util.c
> > > +++ b/net/mac80211/util.c
> > > @@ -277,7 +277,8 @@ static void __ieee80211_wake_queue(struct ieee80211_hw *hw, int queue,
> > >
> > > __clear_bit(reason, &local->queue_stop_reasons[queue]);
> > >
> > > - if (local->queue_stop_reasons[queue] != 0)
> > > + if ((local->queue_stop_reasons[queue] != 0) ||
> > > + test_bit(SCAN_OFF_CHANNEL, &local->scanning))
> > > /* someone still has this queue stopped */
> > > return;
> >
> > That doesn't seem to make sense, since we treat driver and scan stop
> > status separately via wake_queue_by_reason()
>
> I dont know if I explained the issue properly. The issue here is
> waking up the queues by driver during scan, particularly when
> operating on off channel. With ath9k, there is a possibility that
> ieee80211_wake_queue() can be called while moving from operational
> channel (during channel set in driver). In this case driver still
> needs to be allowed to clear the bit in queue_stop_reasons[] but
> not wake up the tx queue.
The actual issue here is
- ath9k does a ieee80211_stop_queue() upon detecting the shortage
in tx buffer.
- by the time it wakes up the queue, network manager issues a
background scanning. tx buffers become available again by
draining the driver's tx queues while configuring the hw with
a non-operational channel. As driver can not really clear its
queue stop request by calling ieee80211_wake_queue() during
off channel, the stopped queue would remain stopped by driver
for ever.
My patch makes ieee80211_wake_queue() callable any time by driver.
This would just clear the driver's stop req bit in queue_stop_reasons[]
when on non-operational channel so that the frames coming from that
queue would be passed to driver when the interface is put back on
operational channel. The commit description in that patch is
misleading. If you are ok with this fix, I will resend the patch
with proper commit message. I could not even come up with a decent
workaround in ath9k as there is no clean way for driver to know
if it is moving in/out of operational channel.
This issue is easily seen with ath9k from latest wireless-testing and
NM. With a simple iperf traffic, tx from mac80211 to driver would stop
with in 20 secs.
Vasanth
^ permalink raw reply
* Re: [PATCH] ath9k: fix TSF after reset on AR913x
From: Felix Fietkau @ 2010-07-01 7:51 UTC (permalink / raw)
To: Johannes Berg
Cc: Björn Smedman, Pavel Roskin, linux-wireless,
Luis R. Rodriguez, John W. Linville
In-Reply-To: <1277966396.3788.0.camel@jlt3.sipsolutions.net>
On 2010-07-01 8:39 AM, Johannes Berg wrote:
> On Thu, 2010-07-01 at 02:47 +0200, Felix Fietkau wrote:
>
>> No, the TSF value at this point is not accurate. It differs
>> semi-randomly by a few orders of magnitude from the time measured by the
>> CPU timer. The value I put in above is just an approximation, but since
>> making it completely accurate is impossible, I figured this is good
>> enough, especially since the value will most likely not deviate much
>> from what I've measured here.
>
> Are you sure it doesn't depend on CPU speed as well since the driver is
> involved here? Or DMA speed?
Yes, it depends on CPU speed, but there's not a lot of variation
possible, because this only affects one, maybe two different SoC types
with similar CPU speed, and a large part of the delay is probably
constant because of udelay calls.
As I said, being precise here is impossible anyway, this is only a
workaround for a hw issue, and this simple approximation should not
cause any problems for anything. Even if the AP's TSF jumps by a few
microseconds, the clients will catch on to that pretty quickly.
- Felix
^ permalink raw reply
* Re: wl1271 firmware
From: Pazzo Da Legare @ 2010-07-01 7:36 UTC (permalink / raw)
To: Levi, Shahar; +Cc: linux-wireless@vger.kernel.org
In-Reply-To: <AC090B9732AB2B4DB7FF476E907FE660010673660C@dnce02.ent.ti.com>
Hi Shahar,
Thank you for your help!
pz
2010/6/30 Levi, Shahar <shahar_levi@ti.com>:
> Hi pz,
> I am checking the way to access the FW and NVS file of wl1271.
> Let me find more details on that and get back to you.
> Regards,
> Shahar
> -----Original Message-----
> From: linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-owner@vger.kernel.org] On Behalf Of Pazzo Da Legare
> Sent: Wednesday, June 30, 2010 2:27 PM
> To: linux-wireless@vger.kernel.org
> Subject: wl1271 firmware
>
> Hi all,
>
> I'm looking for wl1271 firmwares. I found wl1271-fw.bin but I cannot
> find wl1271-nvs.bin needed to use the wl1271's driver.
> Could you please indicate where I can get it?
>
> Thank in advance,
>
> pz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply
* Setting multicast rate
From: Dennis Borgmann @ 2010-07-01 7:24 UTC (permalink / raw)
To: linux-wireless, ath5k-devel
Hello linux-wireless list!
Hello ath5k-devel list!
I am asking in these lists, because I think, this is a feature request,
which should go - of course - directly to the developers.
Do you plan to introduce an option for setting the multicast rate? My
question is especially about ath5k. In madwifi, there was an iwpriv so
set this rate.
Kind regards,
Dennis
^ permalink raw reply
* Re: [PATCH] ath9k: fix TSF after reset on AR913x
From: Johannes Berg @ 2010-07-01 6:39 UTC (permalink / raw)
To: Felix Fietkau
Cc: Björn Smedman, Pavel Roskin, linux-wireless,
Luis R. Rodriguez, John W. Linville
In-Reply-To: <4C2BE5A8.9030003@openwrt.org>
On Thu, 2010-07-01 at 02:47 +0200, Felix Fietkau wrote:
> No, the TSF value at this point is not accurate. It differs
> semi-randomly by a few orders of magnitude from the time measured by the
> CPU timer. The value I put in above is just an approximation, but since
> making it completely accurate is impossible, I figured this is good
> enough, especially since the value will most likely not deviate much
> from what I've measured here.
Are you sure it doesn't depend on CPU speed as well since the driver is
involved here? Or DMA speed?
johannes
^ permalink raw reply
* Re: issues while attempting ath9k_htc to work with ubuntu 10.04, device TL-WN721N
From: c0rrupt @ 2010-06-30 21:59 UTC (permalink / raw)
To: linux-wireless
In-Reply-To: <4C1078D4.3070604@yatharthgupta.com>
Yatharth <y <at> yatharthgupta.com> writes:
********
Yeah I have same problem on Ubuntu 10.04. make install, everything ok no errors,
restart PC and I have same error messages as you. Any one have solution?
^ permalink raw reply
* rfkill failure in 2.6.35-rc3+
From: Andrew Lutomirski @ 2010-07-01 2:59 UTC (permalink / raw)
To: linux-wireless, ilw
I just toggled rfkill on and back off on my X200s (WiFi Link 5350, rev
0x24) and the link didn't come up. Toggling rfkill again didn't fix
it, but rmmod + modprobe did.
dmesg said:
[13629.424869] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
[13629.432761] iwlagn 0000:03:00.0: Not sending command - RF KILL
[13629.432771] iwlagn 0000:03:00.0: Error sending REPLY_RXON:
enqueue_hcmd failed: -5
[13629.432778] iwlagn 0000:03:00.0: Error setting new RXON (-5)
[13631.268646] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
[13631.311232] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[13675.710821] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
[13675.713438] iwlagn 0000:03:00.0: Not sending command - RF KILL
[13675.713448] iwlagn 0000:03:00.0: Error sending REPLY_RXON:
enqueue_hcmd failed: -5
[13675.713455] iwlagn 0000:03:00.0: Error setting new RXON (-5)
[13683.090789] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
[13683.145267] ADDRCONF(NETDEV_UP): wlan0: link is not ready
This is 2.6.35-rc3+ with firmware 8.24.2.12. I've never seen this before.
^ permalink raw reply
* Re: [PATCH] ath9k: fix TSF after reset on AR913x
From: Felix Fietkau @ 2010-07-01 0:47 UTC (permalink / raw)
To: Björn Smedman
Cc: Pavel Roskin, linux-wireless, Luis R. Rodriguez, John W. Linville
In-Reply-To: <AANLkTim8NrVZfcJGi4NK_OhXBxEY0Lw9fdg1bcbzDU0X@mail.gmail.com>
On 2010-07-01 12:38 AM, Björn Smedman wrote:
> On Thu, Jul 1, 2010 at 12:02 AM, Pavel Roskin <proski@gnu.org> wrote:
>> On Wed, 2010-06-30 at 02:07 +0200, Felix Fietkau wrote:
>>> + if (AR_SREV_9100(ah) && (ath9k_hw_gettsf64(ah) < tsf)) {
>>> + tsf += 1500;
>>
>> Why 1500? Is it a magic number? It is a result of some measurement?
>> Can we have a define for it, please?
>
> Does the TSF always start counting from zero when the chip is reset?
> In that case maybe the "magic number" can be replaced with the return
> value from ath9k_hw_gettsf64() (which we call anyway).
No, the TSF value at this point is not accurate. It differs
semi-randomly by a few orders of magnitude from the time measured by the
CPU timer. The value I put in above is just an approximation, but since
making it completely accurate is impossible, I figured this is good
enough, especially since the value will most likely not deviate much
from what I've measured here.
- Felix
^ permalink raw reply
* Re: [PATCH] ath9k: fix TSF after reset on AR913x
From: Felix Fietkau @ 2010-07-01 0:45 UTC (permalink / raw)
To: Pavel Roskin
Cc: linux-wireless, Luis R. Rodriguez, John W. Linville,
Björn Smedman
In-Reply-To: <1277935351.17170.1.camel@mj>
On 2010-07-01 12:02 AM, Pavel Roskin wrote:
> On Wed, 2010-06-30 at 02:07 +0200, Felix Fietkau wrote:
>> + if (AR_SREV_9100(ah) && (ath9k_hw_gettsf64(ah) < tsf)) {
>> + tsf += 1500;
>
> Why 1500? Is it a magic number? It is a result of some measurement?
> Can we have a define for it, please?
The comment right above already explains it. This is the 'offset based
on measured time difference'
- Felix
^ permalink raw reply
* Re: intel 5100/iwlagn bug in 2.6.35-rc2 during large file transfer
From: reinette chatre @ 2010-06-30 23:32 UTC (permalink / raw)
To: Richard Farina; +Cc: linux-wireless@vger.kernel.org
In-Reply-To: <4C296F44.9050000@gmail.com>
On Mon, 2010-06-28 at 20:57 -0700, Richard Farina wrote:
> [ 3091.463559] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 21 free buffers remaining.
> [ 3091.534626] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 0 free buffers remaining.
> [ 3593.179843] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 1 free buffers remaining.
> [ 3593.307837] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 26 free buffers remaining.
> [ 4091.542698] net_ratelimit: 34 callbacks suppressed
> [ 4091.542702] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 25 free buffers remaining.
> [ 4091.542724] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 3 free buffers remaining.
> [ 4091.555285] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 26 free buffers remaining.
> [ 4091.555305] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 0 free buffers remaining.
> [ 4258.724351] net_ratelimit: 2073 callbacks suppressed
> [ 4258.724372] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 0 free buffers remaining.
> [ 4258.753286] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 31 free buffers remaining.
> [ 4258.753309] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 2 free buffers remaining.
> [ 4258.774133] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 28 free buffers remaining.
> [ 5165.260524] net_ratelimit: 21 callbacks suppressed
> [ 5166.400305] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 4 free buffers remaining.
> [ 5167.126059] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 13 free buffers remaining.
> [ 5454.561708] net_ratelimit: 4 callbacks suppressed
> [ 5455.245019] iwlagn 0000:02:00.0: Failed to alloc_pages with
> GFP_ATOMIC. Only 1 free buffers remaining.
>
>
> I'd certainly list it as improved as it hardly freezes and those aren't
> kernel oops.
Some good news is always welcome.
> However it should be noted that this test didn't seem to
> have nearly the same speed as the previous test (which may well be due
> to my internet connection or any number of things having nothing to do
> with this patch). Point is, I'd definately like to get a faster test it
> to see if it explodes.
I do not like the idea that this is making your connection slower
though ... this could be because we are not more likely to attempt
memory allocation when there is still a large number of buffers left ...
so we do memory allocation more (too?) often.
> Assuming it doesn't, how can I help you find out
> why it keeps running out of buffers? I'm guessing this isn't expected
> behavior...
Well, the good news seems to be that your system is not running out of
memory completely ... it is just that the memory available to atomic
allocations is not enough to satisfy all requests. This really sounds
like https://bugzilla.kernel.org/show_bug.cgi?id=14141 , which has
unfortunately not been resolved yet.
Since the patch below appears to be the one making your system
slower ... could you modify the patch to set RX_LOW_WATERMARK to 64? I
know it is what we had before, but hopefully that together with the the
other changes in this patch will help to make system faster as well as
less noisy.
Thank you
Reinette
> Thanks,
> Rick Farina
>
> > >From 65c459c35332c7039cc84a980e6e04118ba81c04 Mon Sep 17 00:00:00 2001
> > From: Reinette Chatre <reinette.chatre@intel.com>
> > Date: Thu, 24 Jun 2010 10:48:59 -0700
> > Subject: [PATCH] increase low watermark
> >
> > ---
> > drivers/net/wireless/iwlwifi/iwl-agn-lib.c | 5 +++--
> > drivers/net/wireless/iwlwifi/iwl-fh.h | 2 +-
> > 2 files changed, 4 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/net/wireless/iwlwifi/iwl-agn-lib.c b/drivers/net/wireless/iwlwifi/iwl-agn-lib.c
> > index 0f292a2..2815ee7 100644
> > --- a/drivers/net/wireless/iwlwifi/iwl-agn-lib.c
> > +++ b/drivers/net/wireless/iwlwifi/iwl-agn-lib.c
> > @@ -613,7 +613,8 @@ void iwlagn_rx_allocate(struct iwl_priv *priv, gfp_t priority)
> > }
> > spin_unlock_irqrestore(&rxq->lock, flags);
> >
> > - if (rxq->free_count > RX_LOW_WATERMARK)
> > + if ((priority == GFP_ATOMIC) ||
> > + (rxq->free_count > RX_LOW_WATERMARK / 4))
> > gfp_mask |= __GFP_NOWARN;
> >
> > if (priv->hw_params.rx_page_order > 0)
> > @@ -627,7 +628,7 @@ void iwlagn_rx_allocate(struct iwl_priv *priv, gfp_t priority)
> > "order: %d\n",
> > priv->hw_params.rx_page_order);
> >
> > - if ((rxq->free_count <= RX_LOW_WATERMARK) &&
> > + if ((rxq->free_count <= RX_LOW_WATERMARK / 4) &&
> > net_ratelimit())
> > IWL_CRIT(priv, "Failed to alloc_pages with %s. Only %u free buffers remaining.\n",
> > priority == GFP_ATOMIC ? "GFP_ATOMIC" : "GFP_KERNEL",
> > diff --git a/drivers/net/wireless/iwlwifi/iwl-fh.h b/drivers/net/wireless/iwlwifi/iwl-fh.h
> > index 113c366..431bc58 100644
> > --- a/drivers/net/wireless/iwlwifi/iwl-fh.h
> > +++ b/drivers/net/wireless/iwlwifi/iwl-fh.h
> > @@ -426,7 +426,7 @@
> > * RX related structures and functions
> > */
> > #define RX_FREE_BUFFERS 64
> > -#define RX_LOW_WATERMARK 8
> > +#define RX_LOW_WATERMARK 128
> >
> > /* Size of one Rx buffer in host DRAM */
> > #define IWL_RX_BUF_SIZE_3K (3 * 1000) /* 3945 only */
> >
>
^ permalink raw reply
* Re: [PATCH] ath9k: fix TSF after reset on AR913x
From: Björn Smedman @ 2010-06-30 22:38 UTC (permalink / raw)
To: Pavel Roskin
Cc: Felix Fietkau, linux-wireless, Luis R. Rodriguez,
John W. Linville
In-Reply-To: <1277935351.17170.1.camel@mj>
On Thu, Jul 1, 2010 at 12:02 AM, Pavel Roskin <proski@gnu.org> wrote:
> On Wed, 2010-06-30 at 02:07 +0200, Felix Fietkau wrote:
>> + if (AR_SREV_9100(ah) && (ath9k_hw_gettsf64(ah) < tsf)) {
>> + tsf += 1500;
>
> Why 1500? Is it a magic number? It is a result of some measurement?
> Can we have a define for it, please?
Does the TSF always start counting from zero when the chip is reset?
In that case maybe the "magic number" can be replaced with the return
value from ath9k_hw_gettsf64() (which we call anyway).
/Björn
^ permalink raw reply
* Re: Problem with firmware load on ipw2200
From: Dan Williams @ 2010-06-30 22:23 UTC (permalink / raw)
To: John W. Linville; +Cc: Larry Finger, wireless
In-Reply-To: <20100629134930.GC5296@tuxdriver.com>
On Tue, 2010-06-29 at 09:49 -0400, John W. Linville wrote:
> On Tue, Jun 29, 2010 at 08:37:21AM -0500, Larry Finger wrote:
> > I'm trying to help an ipw2200 user on the openSUSE Wireless Forum and I'm
> > stuck. The system is failing to load the firmware with error -2 (File or
> > directory not found). The difficulty is that the required files are
> > present with the correct permissions.
> >
> > What system component might be missing and/or borked to get this symptom?
>
> selinux?
Or udev; basically whatever firmware helper is registered with the
kernel for firmware request handling. Which these days I thought was
udev on most distros.
Dan
^ permalink raw reply
* Re: [PATCH] ath9k: fix TSF after reset on AR913x
From: Pavel Roskin @ 2010-06-30 22:02 UTC (permalink / raw)
To: Felix Fietkau
Cc: linux-wireless, Luis R. Rodriguez, John W. Linville,
Björn Smedman
In-Reply-To: <4C2A8AD4.8070504@openwrt.org>
On Wed, 2010-06-30 at 02:07 +0200, Felix Fietkau wrote:
> + if (AR_SREV_9100(ah) && (ath9k_hw_gettsf64(ah) < tsf)) {
> + tsf += 1500;
Why 1500? Is it a magic number? It is a result of some measurement?
Can we have a define for it, please?
--
Regards,
Pavel Roskin
^ permalink raw reply
* Re: Compat-wireless release for 2010-06-30 is baked
From: Pavel Roskin @ 2010-06-30 19:27 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: linux-wireless
In-Reply-To: <20100630190300.056B742E2B@repository3.orbit-lab.org>
On Wed, 2010-06-30 at 15:02 -0400, Compat-wireless cronjob account
wrote:
> From git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
> 4570588..85e0e99 history -> origin/history
> + 1b72384...7a6353a master -> origin/master (forced update)
> 5904b3b..984bc96 stable -> origin/stable
> * [new tag] next-20100630 -> next-20100630
> cat: /var/opt/compat/compat-wireless-2.6/compat_version: No such file or directory
> cat: compat_base_tree: No such file or directory
Luis, could you please check what is going on? There was another
announcement with error messages. Then there was a truncated message.
Now the errors are back.
I'm not sure such messages should be posted to the list. It would be
more useful to send then to those who can do something in the build
system breaks.
--
Regards,
Pavel Roskin
^ permalink raw reply
* Re: pull request: wireless-2.6 2010-06-30
From: Johannes Berg @ 2010-06-30 19:15 UTC (permalink / raw)
To: David Miller; +Cc: linville, linux-wireless, netdev, linux-kernel
In-Reply-To: <20100630.120551.170116973.davem@davemloft.net>
On Wed, 2010-06-30 at 12:05 -0700, David Miller wrote:
> > + /*
> > + * Receiving all multicast frames is always enabled by the
> > + * default flags setup in iwl_connection_init_rx_config()
> > + * since we currently do not support programming multicast
> > + * filters into the device.
> > + */
> > *total_flags &= FIF_OTHER_BSS | FIF_ALLMULTI | FIF_PROMISC_IN_BSS |
> > FIF_BCN_PRBRESP_PROMISC | FIF_CONTROL;
>
> Note that this is an amazingly serious limitation.
>
> This basically makes iwl chips unsuitable for use on networks where
> real multicast use is common.
Lots of wireless devices have this limitation unfortunately. I think we
-might- be able to have proper filters for iwl, but haven't found out
quite how yet unfortunately, if it's actually implemented properly on
the device and there's not just some fake API.
johannes
^ permalink raw reply
* Re: pull request: wireless-2.6 2010-06-30
From: David Miller @ 2010-06-30 19:05 UTC (permalink / raw)
To: linville; +Cc: linux-wireless, netdev, linux-kernel
In-Reply-To: <20100630185319.GA2618@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Wed, 30 Jun 2010 14:53:20 -0400
> Here are a few more fixes intended for 2.6.35. Included are a couple of
> small regression fixes for iwlwifi, one that causes connection stalls with
> 802.11n on some devices and another which could disable multicast traffic.
> Also included is an ath9k fix which avoids a null pointer dereference
> resulting from a timer leak.
>
> Please let me know if there are problems!
...
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git master
Pulled, thanks John.
> @@ -1329,6 +1328,12 @@ void iwl_configure_filter(struct ieee80211_hw *hw,
>
> mutex_unlock(&priv->mutex);
>
> + /*
> + * Receiving all multicast frames is always enabled by the
> + * default flags setup in iwl_connection_init_rx_config()
> + * since we currently do not support programming multicast
> + * filters into the device.
> + */
> *total_flags &= FIF_OTHER_BSS | FIF_ALLMULTI | FIF_PROMISC_IN_BSS |
> FIF_BCN_PRBRESP_PROMISC | FIF_CONTROL;
Note that this is an amazingly serious limitation.
This basically makes iwl chips unsuitable for use on networks where
real multicast use is common.
^ permalink raw reply
* Compat-wireless release for 2010-06-30 is baked
From: Compat-wireless cronjob account @ 2010-06-30 19:02 UTC (permalink / raw)
To: linux-wireless
>From git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
4570588..85e0e99 history -> origin/history
+ 1b72384...7a6353a master -> origin/master (forced update)
5904b3b..984bc96 stable -> origin/stable
* [new tag] next-20100630 -> next-20100630
cat: /var/opt/compat/compat-wireless-2.6/compat_version: No such file or directory
cat: compat_base_tree: No such file or directory
cat: compat_base_tree_version: No such file or directory
cat: compat_version: No such file or directory
cat: /var/opt/compat/compat-wireless-2.6/compat_version: No such file or directory
scripts/Makefile.clean:17: /var/opt/compat/compat-wireless-2.6/drivers/net/wireless/hostap/Makefile: No such file or directory
make[4]: *** No rule to make target `/var/opt/compat/compat-wireless-2.6/drivers/net/wireless/hostap/Makefile'. Stop.
make[3]: *** [/var/opt/compat/compat-wireless-2.6/drivers/net/wireless/hostap] Error 2
make[2]: *** [/var/opt/compat/compat-wireless-2.6/drivers/net/wireless] Error 2
make[1]: *** [_clean_/var/opt/compat/compat-wireless-2.6] Error 2
make: *** [clean] Error 2
compat-wireless code metrics
494378 - Total upstream lines of code being pulled
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox