- 14 Oct, 2011 24 commits
-
-
Wey-Yi Guy authored
Add IWL_DEBUG_MAC80211 debug for all mac80211 callback function Signed-off-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Wey-Yi Guy authored
Once enable rts/cts for aggregation queue, do not disable until the last aggregation queue closed. Signed-off-by:
-
Wey-Yi Guy authored
When detect wrong state on shutdown aggregation queue, show more information for debugging Signed-off-by:
-
Wey-Yi Guy authored
Modify comments on how to enable and change debug_level Signed-off-by:
-
Wey-Yi Guy authored
When in D3 state, use low retry limit for both data and rts Signed-off-by:
-
Wey-Yi Guy authored
When disable aggregation request come in on wrong agg state. ignore it Signed-off-by:
-
Emmanuel Grumbach authored
This one can be _very_ noisy. Signed-off-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
-
Emmanuel Grumbach authored
While inspecting the code, I saw that iwl_tx_queue_unmap modifies the read pointer of the Tx queue without taking any locks. This means that it can race with the reclaim flow. This can possibly lead to a DMA warning complaining that we unmap the same buffer twice. This is more a W/A than a fix since it is really weird to take sta_lock inside iwl_tx_queue_unmap, but it can help until we revamp the locking model in the transport layer. Signed-off-by:
-
Wey-Yi Guy authored
Add additional sku to 105 series Signed-off-by:
-
Wey-Yi Guy authored
Add additional sku to 6005 series of devices Signed-off-by:
-
Wey-Yi Guy authored
setup the rts rety limit for tx command Signed-off-by:
-
Wey-Yi Guy authored
No need to copy twice. Signed-off-by:
-
Johannes Berg authored
Occasionally, the device will send interrupts while it is resuming, at a point where we are not set up again to handle them. This causes the core IRQ handling to completely disable the IRQ, and then the driver won't work again until it is reloaded/rebound. To fix this issue disable the IRQ on suspend, this will cause us to only get interrupts again after we've setup everything on resume. Signed-off-by:
Johannes Berg <johannes.berg@intel.com> Signed-off-by:
-
Don Fry authored
A pointer to the bus structure is still in iwl_priv. Finish cleanup and remove it. Signed-off-by:
Don Fry <donald.h.fry@intel.com> Signed-off-by:
-
Emmanuel Grumbach authored
Not needed since driver split. Signed-off-by:
-
Johannes Berg authored
For some reason, WoWLAN doesn't always seem to be happy with more advanced LQ commands. Since we don't need them as we're not going to send a lot of data, simply program the station with the very simple default LQ command. Signed-off-by:
-
Johannes Berg authored
802.11 says: "Sequence numbers for QoS (+)Null frames may be set to any value." However, if we use the normal counters then peers will get confused with aggregation since there'll be holes in the sequence number sequence. To avoid that, don't assign sequence numbers to QoS Null frames. Signed-off-by:
-
Johannes Berg authored
Updating the beacon every time right after one was transmitted is pointless, most of the time we might not even have to update it. We will update it every time it changes, which includes from set_tim(), a callback iwlwifi didn't implement so far. This also reduces latency for clients, previously we would update the beacon right after the previous one was transmitted, and then a TIM change would only take effect after that again -- updating the beacon right after the TIM changes makes the TIM change go out to the air faster. Signed-off-by:
-
Wey-Yi Guy authored
For command queue testing, add "echo test" to debugfs Signed-off-by:
-
Wey-Yi Guy authored
check the RF KILL flag in queue stuck watch dog function Signed-off-by:
-
Wey-Yi Guy authored
When detect command queue stuck, instead of reload the firmware do the "echo" test to make sure it is really stuck before reload Signed-off-by:
-
Wey-Yi Guy authored
For error condition, STATUS_HCMD_ACTIVE already got clear before receive tx cmd complete, give warning Signed-off-by:
-
Wey-Yi Guy authored
Add "echo" host command for testing and drebugging to make sure uCode still responding Signed-off-by:
-
Wey-Yi Guy authored
When detect cmd queue time out, display the current read/write pointer Signed-off-by:
-
- 12 Oct, 2011 2 commits
-
-
Stephen Rothwell authored
Signed-off-by:
Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by:
-
Amitkumar Karwar authored
This patch supports 88W8766P chipset with a PCIe interface. The corresponding firmware image file is located at: "mrvl/pcie8766_uapsta.bin" Signed-off-by:
Amitkumar Karwar <akarwar@marvell.com> Signed-off-by:
Ramesh Radhakrishnan <rramesh@marvell.com> Signed-off-by:
Yogesh Ashok Powar <yogeshp@marvell.com> Signed-off-by:
Kiran Divekar <dkiran@marvell.com> Signed-off-by:
Bing Zhao <bzhao@marvell.com> Signed-off-by:
Frank Huang <frankh@marvell.com> Signed-off-by:
-
- 11 Oct, 2011 14 commits
-
-
Felix Fietkau authored
Prevents lots of broken frames from showing up on monitor interfaces by default. Signed-off-by:
Felix Fietkau <nbd@openwrt.org> Signed-off-by:
-
Felix Fietkau authored
The commit "ath9k_hw: Fix incorrect key_miss handling" changed the code to only report key miss errors if a MIC error wasn't reported. When checking the flags in that order in the MAC code, it might miss some real events, because the value of the MIC error flag is undefined under some conditions. The primary issue addressed by the previous commit is making sure that MIC errors are properly reported on the STA side. This can be fixed in a better way by adding a separate rx status flag for key miss and ignoring it for multicast frames. This fix slightly improves stability in AP mode on some older hardware, like AR9132. Signed-off-by:
-
Felix Fietkau authored
It was previously used for current_rd_ext Signed-off-by:
-
Felix Fietkau authored
It is unused since the previous dead code that was using it had been removed earlier. Signed-off-by:
-
Felix Fietkau authored
The code for handling various restrictions concerning regulatory limits, antenna gain, etc. is very convoluted and duplicated across various EEPROM parsing implementations, making it hard to review. This patch partially cleans up the mess by unifying regulatory limit handling in one function and simplifying handling of antenna gain. It also removes unused transmit power scaling arrays from the EEPROM code, which belonged to an unimplemented API that isn't supposed to be in the driver anyway. Signed-off-by:
-
Felix Fietkau authored
Signed-off-by:
-
Felix Fietkau authored
PHY errors relevant for ANI are always tracked by hardware counters, the bits that allow them to pass through the rx filter are independent of that. Enabling PHY errors in the rx filter often creates lots of useless DMA traffic and might be responsible for some of the rx dma stop failure warnings. Signed-off-by:
-
Rafał Miłecki authored
We don't want to report random quality info (new PHYs are affected). Signed-off-by:
Rafał Miłecki <zajec5@gmail.com> Signed-off-by:
-
Larry Finger authored
The current debug parameter is applied to rtlwifi, which means that all loaded drivers have the same level of debugging applied. In addition, the previous method requires a two-step load process to enable debugging. Signed-off-by:
Larry Finger <Larry.Finger@lwfinger.net> Signed-off-by:
-
Johannes Berg authored
This was another workaround for truesize "bugs". The reason we did this was that when we orphaned the SKB it wouldn't be truesize-checked later. Now that the check is gone (and we just charge the former smaller size to the socket) there's no longer a reason to orphan the skb here. Keep the skb charged to the socket until it is really freed (or orphaned in TX status). This helps flow control and allows us to get at the socket later for other purposes. Signed-off-by:
-
Johannes Berg authored
There's no need to adjust truesize. The history of this was that we always ran into skb_truesize_bug (via skb_truesize_check) which has since been removed in commit 92a0acce. skb_truesize_check() checked that truesize was bigger or equal to the actual allocation, which would trigger in mac80211 due to header adding. The check no longer exists and we shouldn't be messing with the truesize anwyay. Signed-off-by:
-
Johannes Berg authored
We can now move the radiotap header parsing into ieee80211_monitor_start_xmit(). This moves it out of the hotpath, and also helps the code since now the radiotap header will no longer be present in ieee80211_xmit() etc. which is easier to understand. Signed-off-by:
-
Johannes Berg authored
The purpose of this is two-fold: 1) by moving it out of tx_data.flags, we can in another patch move the radiotap parsing so it no longer is in the hotpath 2) if a device implements fragmentation but can optionally skip it, the radiotap request for not doing fragmentation may be honoured Signed-off-by: -
Johannes Berg authored
It's set, but never used, so kill it. Signed-off-by:
-
