On Sun 2014-11-02 13:25:45, Stanislaw Gruszka wrote:
On Tue, Oct 28, 2014 at 11:20:15PM +0100, Pavel Machek wrote:
It can be checked by iw dev wlan0 get power_save .
So it seems I have power save on. I guess someone enabled it for me :-).
root@duo:~# iwconfig wlan0
wlan0 IEEE
On Sun, 2014-11-09 at 13:10 -0500, Mathy Vanhoef wrote:
From: Mathy Vanhoef vanho...@gmail.com
Unlink the submitted URB in brcmf_usb_dl_cmd if the request timed out. This
assures the URB is never submitted twice, preventing a driver crash.
Hi,
I am afrad this patch is no good. The diagnosis
From: Andrei Otcheretianski andrei.otcheretian...@intel.com
The spec requires to decrement the CSA counters based on TBTT,
regardless if the beacon was actually transmitted. Previously, the fw
would send beacon notifications only for successfully transmitted
beacons. This behavior resulted in
From: Luciano Coelho luciano.coe...@intel.com
Add an absent time event when pre_channel_switch is called and use the
time event started indication to set the disable_tx bit instead of
doing it in unassign_vif(). This is done so that the firmware queues
are stopped before the actual switch takes
From: Luciano Coelho luciano.coe...@intel.com
Disable PS when pre_channel_switch is called and add the
post_channel_switch operation to re-enable PS when the channel switch
is completed.
Signed-off-by: Luciano Coelho luciano.coe...@intel.com
---
drivers/net/wireless/iwlwifi/mvm/mac80211.c | 28
From: Luciano Coelho luciano.coe...@intel.com
We only need the csa_vif in AP/GO modes, and assigning for other
interfaces may cause problems, because csa_vif is never cleared. To
prevent this, only assign the value if the iftype is
NL80211_IFTYPE_AP. Use a switch to do this, even though, for
From: Luciano Coelho luciano.coe...@intel.com
Hi,
These patches finalize the CSA implementation for iwlmvm. These are
the remaining patches that were still pending in our internal tree.
After this, I believe we are aligned.
This series depends on the mac80211/cfg80211 series I sent to Johannes
From: Luciano Coelho luciano.coe...@intel.com
We have code to recover and go back to the original channel context if
something fails in the middle of switch_vif_chanctx, but we return the
error code of the recover calls instead of the original code, so if
the recovery succeeds, we will return 0
From: Luciano Coelho luciano.coe...@intel.com
A new callback has been added to prepare the device for a channel
switch. Use the new callback instead of the old channel_switch_beacon
operation.
This makes it possible to remove the channel_switch_beacon operation
from mac80211.
Signed-off-by:
From: Luciano Coelho luciano.coe...@intel.com
Now that all CSA flows are using the switch_vif_chanctx op, we can
rely on the switching_chanctx boolean that is passed to the
__iwl_mvm_assign_vif_chanctx() and __iwl_mvm_unassign_vif_chanctx()
functions to decide whether the context switch flows
From: Johannes Berg johannes.b...@intel.com
Radiotap vendor namespace data might still be useful, but we
reverted it because it used too much space in the RX status.
Put it back, but address the space problem by using a single
bit only and putting everything else into the skb-data.
From: Luciano Coelho luciano.coe...@intel.com
Add support to reassign vif in switch_vif_chanctx. This is similar to
the existing CHANCTX_SWMODE_SWAP_CONTEXTS mode, but doesn't delete the
old context nor creates a new one, doing to switch between two
existing contexts.
Signed-off-by: Luciano
From: Luciano Coelho luciano.coe...@intel.com
Currently we only support the CHANCTX_SWMODE_SWAP_CONTEXTS mode, but
we need to support other modes as well. Spin a new function off in
order to make it easier to support other modes.
Signed-off-by: Luciano Coelho luciano.coe...@intel.com
---
On Sun, Nov 9, 2014 at 9:50 PM, Arend van Spriel ar...@broadcom.com wrote:
On 11/09/14 17:50, Arik Nemtsov wrote:
Introduce commands to initiate and cancel TDLS channel-switching. Once
TDLS channel-switching is started, the lower level driver is responsible
for continually initiating
On Fri, 2014-11-07 at 15:28 +0200, Luca Coelho wrote:
From: Luciano Coelho luciano.coe...@intel.com
Hi,
It seems that I made a couple of mistakes when publishing our CSA
patches to the mainline. These two patches fix these problems.
Applied.
johannes
--
To unsubscribe from this list:
On Fri, 2014-11-07 at 14:31 +0200, Luca Coelho wrote:
From: Luciano Coelho luciano.coe...@intel.com
This is a rework of the channel switch started notification that I
sent a long time ago. According to the review, I removed the failure
notification. Additionally, some other small changes
From: Luciano Coelho luciano.coe...@intel.com
Instead of using a hardcoded number of TUs before beacon 0 as the time
to start the absence and actual channel switch, calculate it in
relation to the beacon interval. We use 10 TUs + beacon interval
before beacon 0 to target a bit before beacon 1.
From: Luciano Coelho luciano.coe...@intel.com
Now that mac80211 waits for the first beacon on the new channel before
calling post_channel_switch, the reconfiguration of the firmware
should be done in the post_channel_switch operation instead of when
assigning the vif to the new context.
From: Luciano Coelho luciano.coe...@intel.com
We need to call ieee80211_chswitch_done() ourselves just when the
absence TE started, so we perform the actual context switch early
enough. To do so, add a dummy channel_switch op, which will cause
mac80211 to skip the countdown timer and allow us to
From: Luciano Coelho luciano.coe...@intel.com
If setting the CSA time event fails, we must clear the TE data,
otherwise we'll try to remove it when, for instance, a disconnection
occurs, causing a SYSASSERT.
Signed-off-by: Luciano Coelho luciano.coe...@intel.com
---
From: Luciano Coelho luciano.coe...@intel.com
After a channel switch, transmission on the new channel is only
started once we see a beacon on it. Thus, beacon filtering needs to
be disabled during channel switch so that mac80211 receives this
beacon and finishes the process.
Signed-off-by:
From: Andrei Otcheretianski andrei.otcheretian...@intel.com
Since it's too complicated for the fw to insert a DS Parameter Set
element in the middle of the frame, it was decided that it should be
done by the host. The fw will only parse the frame and update the
current channel field.
From: Luciano Coelho luciano.coe...@intel.com
When another vif is also running during a channel switch, we need to
use a session protection when we move to the new channel, so that we
don't miss the beacons. Without this, sometimes the other vif
repeatedly gets time exactly when we should be
On Mon, 2014-11-10 at 10:10 +0100, Johannes Berg wrote:
From: Johannes Berg johannes.b...@intel.com
Radiotap vendor namespace data might still be useful, but we
reverted it because it used too much space in the RX status.
Put it back, but address the space problem by using a single
bit only
On Fri, 2014-11-07 at 10:21 +0200, Patrik Flykt wrote:
-error:
- nlmsg_free(skb);
- return NULL;
+ return 0;
}
-static void hswim_mcast_new_radio(int id, struct genl_info *info,
+static void hwsim_mcast_new_radio(int id, struct genl_info *info,
On Fri, 2014-11-07 at 10:22 +0200, Patrik Flykt wrote:
+static int hwsim_dump_radio_nl(struct sk_buff *skb,
+struct netlink_callback *cb)
+{
+ struct mac80211_hwsim_data *data = NULL;
+
+ spin_lock_bh(hwsim_radio_lock);
+
+ list_for_each_entry(data,
On Thu, 2014-10-23 at 09:37 +0300, Arik Nemtsov wrote:
Allow setting bandwidth related regulatory flags. These flags are mapped
to the corresponding channel flags in the specified range.
Make sure the new flags are consulted when calculating the maximum
bandwidth allowed by a regulatory-rule.
Hello Hernan and all the others;
Sergey Ryazanov ryazanov.s.a@... writes:
Cc linux-wireless since Rostislav Lisovy just working on adding
802.11p to the stack.
2014-11-07 16:49 GMT+03:00 Hernán Maximiliano González Calderón
hernan.gonzalez.calderon@...:
Hello everyone,
I am still
Rostislav Lisovy lisovy@... writes:
The questions that are still unanswered (and will definitely require
more effort to answer) are the 802.11p standard interpretation
regarding the OCB mode / 5.9GHz usage limitation. More specific --
Is the 5.9GHz limited for ITS (Intelligent transportation
Hi John,
One more for 3.18, if possible.
johannes
The following changes since commit b8fff407a180286aa683d543d878d98d9fc57b13:
mac80211: fix use-after-free in defragmentation (2014-11-03 14:28:50 +0100)
are available in the git repository at:
On Mon, 2014-11-10 at 11:30 +0100, Uwe Brauer wrote:
On Fri, Nov 7, 2014 at 4:58 PM, Uwe Brauer o...@mat.ucm.es wrote:
you problem is that you didn't compile the kernel with wireless
extensions. This interface is deprecated, but I don't remember if it
was the case for 3.7.
Hi,
These patches finalize the CSA implementation for iwlmvm. These are
the remaining patches that were still pending in our internal tree.
After this, I believe we are aligned.
Thanks Luca!
This series depends on the mac80211/cfg80211 series I sent to Johannes
last Friday
On 11/10/2014 06:18 AM, Arend van Spriel wrote:
On 09-11-14 19:10, Mathy Vanhoef wrote:
From: Mathy Vanhoef vanho...@gmail.com
Unlink the submitted URB in brcmf_usb_dl_cmd if the request timed out. This
assures the URB is never submitted twice, preventing a driver crash.
Hi Mathy,
What
Resending in plain text mode...
Hi Kalle,
I have a custom built board with an AR6003 WiFi chip running
linux-3.10.40 and hostapd 2.2 that I'm trying to use as an access
point.
My configuration file for hostapd is:
interface=wlan0
driver=nl80211
ssid=testssid
channel=1
own_ip_addr=**
On 11/06/2014 04:47 PM, Ben Greear wrote:
On 11/06/2014 11:57 AM, Ben Greear wrote:
I have uploaded the latest CT version of the ath10k firmware.
http://www.candelatech.com/ath10k.php
This firmware fixes bugs in raw-tx mode, though probably only
non-encrypted frames can be sent in this
While preparing an ad-hoc start command, the capability info bitmap is
needlessly set from the command, and then the ESS bit cleared.
Change to set the bitmap directly without reference to the command.
Signed-off-by: James Cameron qu...@laptop.org
---
drivers/net/wireless/mwifiex/join.c | 4
Hi John,
This is a pull request for 3.18. More details below.
Please pull - thanks!
The following changes since commit 31b8b343e019e0a0c57ca9c13520a87f9cab884b:
iwlwifi: fix RFkill while calibrating (2014-11-03 15:29:17 +0200)
are available in the git repository at:
From: Liad Kaufman liad.kauf...@intel.com
The length counting previously done had an error in it, causing
the length down the data dumping function to be shorter than it
should be, causing the end of the data to get truncated off and
lost.
Cc: sta...@vger.kernel.org [3.17+]
Fixes: 67c65f2cf710
For offloading 4 way handshake to driver , currently we don't have WIPHY
capability flag to communicate same to supplicant.
I have added the flag NL80211_ATTR_4WAY_KEY_HANDSHAKE and rest of the code for
the same.
Tested on x86 linux machine
Signed-off-by: Gautam kumar shukla
From: Miaoqing Pan miaoq...@qca.qualcomm.com
For AR9340, the correct values for SLP32 registers are present
in the initvals, so overriding them is not needed.
Signed-off-by: Miaoqing Pan miaoq...@qca.qualcomm.com
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
From: Sujith Manoharan c_man...@qca.qualcomm.com
Various fixes for -next.
Miaoqing Pan (3):
ath9k: disable overriding AR9340 SLP32 registers
ath9k: Use new QCA953x initvals
ath9k: Fix high tx power in multi-chain mode
Sujith Manoharan (3):
ath9k: Update QCA953x initvals
ath9k: Fix LED
From: Miaoqing Pan miaoq...@qca.qualcomm.com
For multi-chain chips, if the thermometer is switched off for a chain
which can be disabled by software(e.g tx_chainmask=0x1), the measured tx
power is about 5dB higher than target power.
Set thermometer on for all chains to fix this issue.
From: Miaoqing Pan miaoq...@qca.qualcomm.com
This patch updates the initvals for QCA953x v1.1 and v2.0
Signed-off-by: Miaoqing Pan miaoq...@qca.qualcomm.com
Signed-off-by: Sujith Manoharan c_man...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/ar9003_hw.c | 51
43 matches
Mail list logo
