- May 11, 2010
-
-
Reinette Chatre authored
When adding the broadcast station the link quality command is generated on demand, sent to device, and disappears. It is thus not available for later cases when we need to restore stations and need to send the link quality command afterwards. Now, when first adding the broadcast station, also generate its link quality command to always be available for later restoring. Also fix an issue when adding local stations where the "in progress" state is never cleared. Reported-by:
Johannes Berg <johannes.berg@intel.com> Signed-off-by:
Reinette Chatre <reinette.chatre@intel.com>
-
Shanyu Zhao authored
Dump the firmware version and build number in case of firmware SW error. This would help firmware engineer analyze the error log. Requested-by:
Jay Sternberg <jay.e.sternberg@intel.com> Signed-off-by:
Shanyu Zhao <shanyu.zhao@intel.com> Signed-off-by:
-
Wey-Yi Guy authored
Multiple error condition require fw/rf reset, driver should check all the possible errors as long as the error checking functions for the devices are available. Reported-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
-
Wey-Yi Guy authored
wifi/wimax co-exist command is part of _agn device configuration sequence; move it to iwl-agn-ucode.c which is more appropriate place for the function. Signed-off-by:
-
Wey-Yi Guy authored
Return -EAGAIN when request tx power information and uCode is not ready; so it will not confuse with tx power information not available. Signed-off-by:
-
Wey-Yi Guy authored
sensitivity calibration and chain noise calibration are not available for all the devices; use .cfg to configure the availability of those calibration functions Signed-off-by:
-
Wey-Yi Guy authored
Instead of checking device type for enable/disable continuous ucode trace function; put it in .cfg for better control and more flexibilities. Signed-off-by:
-
Wey-Yi Guy authored
Instead of checking device type for enable/disable tx power control, move it to .cfg for better control and more flexibilities. Signed-off-by:
-
Johannes Berg authored
The iw_mode will always follow the only vif we have, but using the vif directly seems easier. Signed-off-by:
-
Wey-Yi Guy authored
The "chain_tx_power" debugfs function is to display the tx power per chain based. Name it "tx_power" is misleading. Signed-off-by:
-
Wey-Yi Guy authored
For the devices do not have power save support, remove the power save control related debugfs files. Signed-off-by:
-
Abhijeet Kolekar authored
Port following patch to 3945. "commit 90c4162ff59a3281b6d2f7206740be6217bd6758 Author: Johannes Berg <johannes.berg@intel.com> Date: Wed Apr 7 00:21:36 2010 -0700 iwlwifi: fix scan races" Signed-off-by:Abhijeet Kolekar <abhijeet.kolekar@intel.com> Signed-off-by:
-
Shanyu Zhao authored
Rename the current 6000 series Gen2 devices to Gen2a. Rename the ucode name prefix to iwlwifi-6000g2a. Also corrected the device IDs for Gen2a series devices. Signed-off-by:
-
Reinette Chatre authored
Conflicts: drivers/net/wireless/iwlwifi/iwl-dev.h
-
Johannes Berg authored
When we kick off a firmware loading process, and then unbind from the pci device right away, we get into trouble. Avoid that by waiting for the firmware loading to finish (whether successfully or not) before the unbind in iwl_pci_remove. Signed-off-by:
-
Randy Dunlap authored
When CONFIG_NET is disabled, the attempt to build wext-priv.c fails with: net/wireless/wext-priv.c: In function 'ioctl_private_call': net/wireless/wext-priv.c:207: error: implicit declaration of function 'call_commit_handler' Signed-off-by:
Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Xose Vazquez Perez authored
s/X/x Signed-off-by:
Xose Vazquez Perez <xose.vazquez@gmail.com> Acked-by:
Ivo van Doorn <IvDoorn@gmail.com> Signed-off-by:
-
Gertjan van Wingerde authored
With a little bit of restructuring it isn't necessary to have special cases in rt2x00queue_write_tx_descriptor for writing the descriptor for beacons. Simply split off the kicking of the TX queue to a separate function with is only called for non-beacons. Signed-off-by:
Gertjan van Wingerde <gwingerde@gmail.com> Acked-by:
-
Gertjan van Wingerde authored
According to the Ralink vendor driver for rt2800 we don't need a full TXD for a beacon but just a TXWI in front of the actual beacon. Fix the rt2800pci and rt2800usb beaconing code accordingly. Signed-off-by:
-
Gertjan van Wingerde authored
Preparation to fix rt2800 beaconing. Signed-off-by:
-
Gertjan van Wingerde authored
All of the driver's kick_tx_queue callback functions treat the TX queue for beacons in a special manner. Clean this up by integrating the kicking of the beacon queue into the write_beacon callback function, and let the generic code no longer call the kick_tx_queue callback function when updating the beacon. Signed-off-by:
-
Gertjan van Wingerde authored
RXWI processing is exactly the same for rt2800pci and rt2800usb, so make it common code. Signed-off-by:
-
Gertjan van Wingerde authored
TXWI writing is exactly the same for rt2800pci and rt2800usb, so make it common code. Signed-off-by:
-
Gertjan van Wingerde authored
We should simply follow what the hardware told us it has done. Signed-off-by:
-
Gertjan van Wingerde authored
Remove unused RXD_DESC_SIZE define and remove duplicated RXWI definitions from rt2800.h. Signed-off-by:
-
Gertjan van Wingerde authored
We should take the stripping of the IV into account for the txdesc->length field. Signed-off-by:
Pavel Roskin <proski@gnu.org> Signed-off-by:
-
Dan Carpenter authored
There are several places that use > ARRAY_SIZE() instead of >= ARRAY_SIZE(). Signed-off-by:
Dan Carpenter <error27@gmail.com> Acked-by:
Bob Copeland <me@bobcopeland.com> Acked-by:
Bruno Randolf <br1@einfach.org> Signed-off-by:
-
Dan Carpenter authored
I changed "> ATH9K_HTC_MAX_TID" to ">= ATH9K_HTC_MAX_TID" to avoid a potential overflow. Signed-off-by:
Sujith <Sujith.Manoharan@atheros.com> Signed-off-by:
-
Dan Carpenter authored
This is a stray null dereference. We initialize "ista" properly later on. Signed-off-by:
-
Dan Carpenter authored
This mutex_unlock() has been here from the initial commit, but as nearly as I can tell, there isn't a reason for it. Signed-off-by:
-
Luis R. Rodriguez authored
Cc: Paul Shaw <paul.shaw@atheros.com> Cc: Don Breslin <don.breslin@atheros.com> Signed-off-by:
Luis R. Rodriguez <lrodriguez@atheros.com> Signed-off-by:
-
John W. Linville authored
From the original report: "I had problems to get my rtl8185 PCI card running on Sparc64: I always got an error about "No suitable DMA available" followed by an error that no device could be detected. When comparing the rtl8180 driver to others I noticed that others are mostly using DMA_BIT_MASK so I changed the custom mask to DMA_BIT_MASK(32) which fixed my issue." Reported-by:
Tiziano Müller <tm@dev-zero.ch> Acked-by:
David S. Miller <davem@davemloft.net> Signed-off-by:
-
- May 08, 2010
-
-
Helmut Schaa authored
rt2800 devices use a different enumeration to specify what IFS values should be used on frame transmission compared to the other rt2x00 devices. Hence, create a new enum called txop that contains the valid values. Furthermore use the appropriate txop values as found in the ralink drivers: - TXOP_BACKOFF for management frames - TXOP_SIFS for subsequent fragments in a burst - TXOP_HTTXOP for all data frames Signed-off-by:
Helmut Schaa <helmut.schaa@googlemail.com> Acked-by:
-
Juuso Oikarinen authored
Currently, we configure a 128ms hang over period for the PSM entry (the firmware will remain active for 128ms after sending the null func for PSM and getting an ack for it.) This is a huge power consumption issue, and appears unnecessary. So, configure the value to 1 ms. Signed-off-by:
Juuso Oikarinen <juuso.oikarinen@nokia.com> Reviewed-by:
Janne Ylalehto <janne.ylalehto@nokia.com> Signed-off-by:
Luciano Coelho <luciano.coelho@nokia.com> Signed-off-by:
-
Teemu Paasikivi authored
Incresed the timeout value for command complete event waiting from 100 ms to 750 ms. In some rare cases it can take about 600 ms before complete event for join command is received. This is most propably caused by the firmware being busy with scanning related activities. Signed-off-by:
Teemu Paasikivi <ext-teemu.3.paasikivi@nokia.com> Reviewed-by:
-
Juuso Oikarinen authored
This patch changes the way JOIN's are performed, and channel numbers updated. The reason for this is that the firmware JOIN command clears WPA(2) key material, and if done while associated to a WPA(2) secured AP, will render the data-path unusable. While the channel is not usually changed while associated (and currently we could not even support something like that), after performing a scan operation while associated, mac80211 will re-set the current channel to the driver. This caused our problem. Also, the mac80211 is assuming that the driver channel configuration remains persistent over periods of IDLE. Therefore remove channel resetting to zero from the unjoin function. Signed-off-by:
-
Juuso Oikarinen authored
Reading single registers did not pay attention to data endianness. This patch fix that. Signed-off-by:
-
Juuso Oikarinen authored
This patch reads the HW PG version (along with a ROM-version, embedded in the same value) from the wl1271 hardware and publishes the value in a sysfs -file. Signed-off-by:
-
Sujith authored
Switch LED off/on when handling CONF_CHANGE_IDLE. Not doing this would leave the radio LED on even though the chip would be in full sleep mode. Signed-off-by:
-
Luis R. Rodriguez authored
Generated using the new shiny intivals-tool [1]: initvals -w -f ar9003 > ar9003_initvals.h The respective checksums are: 0x000000005a76829d ar9300_2p0_radio_postamble 0x000000009d90cb74 ar9300Modes_lowest_ob_db_tx_gain_table_2p0 0x00000000e0bc2c84 ar9300Modes_fast_clock_2p0 0x00000000852fca34 ar9300_2p0_radio_core 0x0000000000000000 ar9300Common_rx_gain_table_merlin_2p0 0x0000000078658fb5 ar9300_2p0_mac_postamble 0x0000000023235333 ar9300_2p0_soc_postamble 0x0000000054d41904 ar9200_merlin_2p0_radio_core 0x00000000618455d4 ar9300_2p0_baseband_postamble 0x000000009aa590a4 ar9300_2p0_baseband_core 0x000000004783d946 ar9300Modes_high_power_tx_gain_table_2p0 0x000000006681db44 ar9300Modes_high_ob_db_tx_gain_table_2p0 0x000000001f318700 ar9300Common_rx_gain_table_2p0 0x000000009990cb74 ar9300Modes_low_ob_db_tx_gain_table_2p0 0x00000000c9d66d40 ar9300_2p0_mac_core 0x0000000039139500 ar9300Common_wo_xlna_rx_gain_table_2p0 0x00000000a0c54980 ar9300_2p0_soc_preamble 0x00000000292e2544 ar9300PciePhy_pll_on_clkreq_disable_L1_2p0 0x000000002d3e2544 ar9300PciePhy_clkreq_enable_L1_2p0 0x00000000293e2544 ar9300PciePhy_clkreq_disable_L1_2p0 [1] http://wireless.kernel.org/en/users/Drivers/ath9k_hw/initvals-tool Cc: Tom Hammel <thammel@atheros.com> Cc: Enis Akay <Enis.Akay@Atheros.com> Signed-off-by:
-
