- 07 Mar, 2012 1 commit
-
-
Paul Stewart authored
mac80211 is lenient with respect to reception of corrupted beacons. Even if the frame is corrupted as a whole, the available IE elements are still passed back and accepted, sometimes replacing legitimate data. It is unknown to what extent this "feature" is made use of, but it is clear that in some cases, this is detrimental. One such case is reported in http://crosbug.com/26832 where an AP corrupts its beacons but not its probe responses. One approach would be to completely reject frames with invaid data (for example, if the last tag extends beyond the end of the enclosing PDU). The enclosed approach is much more conservative: we simply prevent later IEs from overwriting the state from previous ones. This approach hopes that there might be some salient data in the IE stream before the corruption, and seeks to at least prevent that data from being overwritten. This approach will fix the case above. Further, we flag element structures that contain data we think might be corrupted, so that as we fill the mac80211 BSS structure, we try not to replace data from an un-corrupted probe response with that of a corrupted beacon, for example. Short of any statistics gathering in the various forms of AP breakage, it's not possible to ascertain the side effects of more stringent discarding of data. Signed-off-by:
Paul Stewart <pstew@chromium.org> Cc: Sam Leffler <sleffler@chromium.org> Cc: Eliad Peller <eliad@wizery.com> Acked-by:
Johannes Berg <johannes@sipsolutions.net> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
- 06 Mar, 2012 39 commits
-
-
Samuel Ortiz authored
Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com> Signed-off-by:
-
Samuel Ortiz authored
Signed-off-by:
-
Samuel Ortiz authored
Signed-off-by:
-
Samuel Ortiz authored
The socket local pointer needs to be set to NULL when the adapter is removed or the MAC goes down. If the socket release code is called after such an event, the socket reference count still needs to be decreased in order for the socket to eventually be freed. Signed-off-by:
-
Samuel Ortiz authored
When calling nfc_dep_link_up, we implicitely are in initiator mode. Which means we also can provide the general bytes as a function argument, as all drivers will eventually request them. Signed-off-by:
-
Samuel Ortiz authored
We just don't do anything with it when parsing the general bytes. We handle it from the CONNECT reception code. Signed-off-by:
-
Samuel Ortiz authored
The parent socket (the bound one) could be freed before its children, so we should unlink the children without trying to reach it through the parent. Signed-off-by:
-
Samuel Ortiz authored
Signed-off-by:
-
Samuel Ortiz authored
The jewel ID is the NFCID1 for Topaz NFC tags. Signed-off-by:
-
Samuel Ortiz authored
sensf is the detection response for Felica NFC tags. Signed-off-by:
-
Samuel Ortiz authored
Based on the receiver MIU, we have to fragment the frame to be transmitted. Signed-off-by:
-
Samuel Ortiz authored
We use the maximum values for the LLCP Maximum Information Unit and Receive Window Size. Signed-off-by:
-
Samuel Ortiz authored
In order to acknowledge an I frame, we have to either queue pending local I frames or queue a receiver ready frame. Signed-off-by:
-
Samuel Ortiz authored
Signed-off-by:
-
Samuel Ortiz authored
Signed-off-by:
-
Samuel Ortiz authored
The polled target structure should be memset to 0 in order to avoid sel_res and sens_res garbage. Signed-off-by:
-
Samuel Ortiz authored
Signed-off-by:
-
Samuel Ortiz authored
Signed-off-by:
-
Samuel Ortiz authored
Signed-off-by:
-
Samuel Ortiz authored
This one will be called from the I frame command sending. Signed-off-by:
-
Samuel Ortiz authored
For user space to know if a device is up or down. Signed-off-by:
-
Samuel Ortiz authored
Signed-off-by:
-
Arend van Spriel authored
Wireless Broadcom chips can have either their SPROM data stored on either external SPROM or on-chip OTP memory. Both are accessed through the same register space. This patch adds support for the on-chip OTP memory. Tested with: BCM43224 OTP and SPROM BCM4331 SPROM BCM4313 OTP This patch is in response to linux-wireless thread [1]. [1] http://article.gmane.org/gmane.linux.kernel.wireless.general/85426Tested-by:
Saul St. John <saul.stjohn@gmail.com> Tested-by:
Rafal Milecki <zajec5@gmail.com> Tested-by:
Hauke Mehrtens <hauke@hauke-m.de> Cc: Larry Finger <Larry.Finger@lwfinger.net> Signed-off-by:
Arend van Spriel <arend@broadcom.com> Signed-off-by:
-
Arend van Spriel authored
When not SPROM is available a fallback mechanism is used. However, when that fails the code currently continues. This patch assures that the bcma_sprom_get() function aborts when that happens. Cc: Rafal Milecki <zajec5@gmail.com> Cc: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by:
-
Felix Fietkau authored
All other Atheros drivers run the AGC gain calibration and DC offset calibration only after reset. Running them periodically has caused stability issues on some (primarily AR2315/2413/5413/5414 based) devices, leading to messages such as: ath5k phy0: gain calibration timeout (2462MHz) ath5k phy0: calibration of channel 11 failed Related bug reports: https://dev.openwrt.org/ticket/10574 https://bugzilla.redhat.com/show_bug.cgi?id=795141Signed-off-by:
Felix Fietkau <nbd@openwrt.org> Acked-by:
Nick Kossifidis <mickflemm@gmail.com> Signed-off-by:
-
Felix Fietkau authored
Some calibration types interfere with tx activity, but the queue stop does not prevent that. In fact, some calibration types need tx activity to properly function, so stopping the queues for them is counterproductive. In some tests this patch has been shown to improve stability, especially in AP or ad-hoc mode. Signed-off-by:
-
Javier Cardona authored
Signed-off-by:
Javier Cardona <javier@cozybit.com> Reviewed-by:
-
Javier Cardona authored
Generate a tsf from internal kernel clock. Prepare the path for having different tsf offsets on each phy. This will be useful for testing mesh synchronization algorithms. Signed-off-by:
-
Thomas Pedersen authored
Airtime link metric estimation was broken in HT mesh, use cfg80211_calculate_bitrate to get the right rate value. Also factor out tx rate copying from sta_set_sinfo(). Signed-off-by:
Thomas Pedersen <thomas@cozybit.com> Reviewed-by:
-
Thomas Pedersen authored
Signed-off-by:
-
Johannes Berg authored
This doesn't belong into the op_mode, it has to be in the drv stop flow instead. Signed-off-by:
Johannes Berg <johannes.berg@intel.com> Signed-off-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
-
Johannes Berg authored
Firmware request is a base driver flow, it isn't related to any specific mode. Move the code related to it into the base driver file iwl-drv.c. Signed-off-by:
-
Johannes Berg authored
This is used from there, so should be in it. Signed-off-by:
-
Johannes Berg authored
This shouldn't be in the op_mode, as it will later be switchable at runtime. Signed-off-by:
-
Johannes Berg authored
My patch "iwlwifi: simplify auth/assoc flow" caused a serious throughput degradation due to me forgetting that there are HT settings in the station table. To restore throughput, set these parameters correctly when the sta moves to assoc state. This patch should probably be merged with the auth/assoc redesign patch for upstream. In that case, this paragraph should be added to the commit log as the third paragraph (before talking about RXON): However, as we only get the station HT data when the station moves into assoc state, we also need to program this into the device (and copy it into our database) then. Signed-off-by:
-
Johannes Berg authored
These are DVM specific, and shouldn't be in iwl-shared.h. Signed-off-by:
-
Johannes Berg authored
Only used in two places in the same file, no need to be in iwl-shared.h. Signed-off-by:
-
Johannes Berg authored
Currently, queue mapping is handled in the transport. This may change, but until then the code for it can be close to where it's used rather than in iwl-shared.h. Signed-off-by:
-
Johannes Berg authored
This is how the transport passes things up into higher layers, so it belongs to the transport API. Signed-off-by:
-
