It is okay to enable DFS for channel contexts
based drivers as long as no combination advertises
radar detection and multi-channel operation at the
same time.
Signed-off-by: Michal Kazior
---
I think this is enough for single-channel
chanctx-based drivers or am I missing something?
net/mac80211
On 29.09.2014 21:46, Dan Williams wrote:
> On Mon, 2014-09-29 at 11:29 +0200, poma wrote:
>> [platform/nm-platform.c:806] nm_platform_link_set_up(): link: setting up
>> 'wlp0s4f1u1' (4)
>> [platform/nm-linux-platform.c:2356] link_change_flags(): link: change 4:
>> flags set 'up' (1)
>> [platform/
I reliably get the following lockup when trying to set up a VPN tunnel
using L2TP over IPSEC:
[ 2214.970639] BUG: soft lockup - CPU#1 stuck for 22s! [pppd:9423]
[ 2214.970648] Modules linked in: l2tp_ppp l2tp_netlink l2tp_core pppoe pppox
ppp_generic slhc authenc cmac rmd160 crypto_null ip_vti i
From: Sujith Manoharan
When a full chip reset is done, all the queues
across all VIFs are stopped, but if MCC is enabled,
only the queues of the current context is awakened,
when we complete the reset.
This results in unfairness for the inactive context.
Since frames are queued internally in the
From: Sujith Manoharan
When we are attempting to switch to a new
channel context, the TX queues are flushed, but
the mac80211 queues are not stopped and traffic
can still come down to the driver.
This patch fixes it by stopping the queues
assigned to the current context/vif before
trying to flus
From: Sujith Manoharan
When draining of the TX queues fails, a
full HW reset is done. ath_reset() makes sure
that the queues in mac80211 are restarted,
so there is no need to wake them up again.
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/ath9k/main.c | 5 -
1 file changed
From: Sujith Manoharan
This can be used when the queues of a context
needs to be stopped.
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/ath9k/ath9k.h | 5 +
drivers/net/wireless/ath/ath9k/channel.c | 19 +++
2 files changed, 24 insertions(+)
diff --git a/
From: Sujith Manoharan
Change the ath9k_chanctx_wake_queues() API so
that we can pass the channel context that needs its
queues to be stopped.
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/ath9k/ath9k.h | 5 +++--
drivers/net/wireless/ath/ath9k/channel.c | 6 +++---
drivers/ne
From: Sujith Manoharan
ath9k_has_tx_pending() can be used to
check if there are pending frames instead
of having duplicate code.
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/ath9k/main.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/net/w
From: Sujith Manoharan
There is no need to check if the current
channel context has active ACs queued up
if the TX queue is not empty.
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/ath9k/main.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/net/w
From: Sujith Manoharan
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/ath9k/channel.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/net/wireless/ath/ath9k/channel.c
b/drivers/net/wireless/ath/ath9k/channel.c
index b93f83c..d088f06 100644
--- a/drivers/net/wir
From: Sujith Manoharan
Checking for the queue depth outside of
the TX queue lock is incorrect and in this
case, is not required since it is done inside
ath9k_has_pending_frames().
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/ath9k/main.c | 3 ---
1 file changed, 3 deletions(-)
From: Sujith Manoharan
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/Kconfig | 8 +
drivers/net/wireless/ath/Makefile | 4 +++
drivers/net/wireless/ath/ath.h| 1 +
drivers/net/wireless/ath/main.c | 3 ++
drivers/net/wireless/ath/trace.c | 20 +++
drivers/n
From: Sujith Manoharan
Pending MCC fixes, rebased over -rc7.
Sujith Manoharan (10):
ath: Add support for tracing
ath9k: Print RoC expiration
ath9k: Check pending frames properly
ath9k: Fix pending frame check
ath9k: Remove duplicate code
ath9k: Fix queue handling in flush()
ath9k:
On 10/01/2014 04:00 PM, Ben Greear wrote:
> I tried this on a 3.17.0-rc7+ kernel, but reported tx-rate stays at 54Mbps
>
> iw dev sta1 set bitrates legacy-5 24
>
> Driver is ath9k, but wpa_supplicant is configured to disable HT.
>
> I'm going to go dig into this, but if someone has any suggestio
I tried this on a 3.17.0-rc7+ kernel, but reported tx-rate stays at 54Mbps
iw dev sta1 set bitrates legacy-5 24
Driver is ath9k, but wpa_supplicant is configured to disable HT.
I'm going to go dig into this, but if someone has any suggestions,
please let me know.
Thanks,
Ben
--
Ben Greear
Ca
On 10/01/2014 12:56 PM, Arend van Spriel wrote:
>> diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
>> index 8a010bd..cf79707 100644
>> --- a/net/wireless/nl80211.c
>> +++ b/net/wireless/nl80211.c
>> @@ -2605,7 +2605,7 @@ static int nl80211_new_interface(struct sk_buff *skb,
>> struct
On 01-10-14 19:57, gree...@candelatech.com wrote:
> From: Ben Greear
>
> This is useful when creating virtual-stations, and probably
> APs and other devices as well. Keeps udev from mucking with
> things it shouldn't, since the default MAC is never seen
> by udev when specified on the cmd-line d
From: Ben Greear
This is useful when creating virtual-stations, and probably
APs and other devices as well. Keeps udev from mucking with
things it shouldn't, since the default MAC is never seen
by udev when specified on the cmd-line during creation.
Signed-off-by: Ben Greear
---
v2: Use is_v
On 10/01/2014 01:35 AM, Arend van Spriel wrote:
> On 09/30/14 20:43, gree...@candelatech.com wrote:
>> From: Ben Greear
>>
>> This is useful when creating virtual-stations, and probably
>> APs and other devices as well. Keeps udev from mucking with
>> things it shouldn't, since the default MAC is
On Wed, Oct 01, 2014 at 05:20:48PM +0300, Dan Carpenter wrote:
> Hello Mark A. Greer,
>
> The patch 1961843ceeca: "NFC: trf7970a: Handle timeout values of
> zero" from Sep 2, 2014, leads to the following static checker warning:
>
> drivers/nfc/trf7970a.c:897 trf7970a_irq()
> warn: pas
Hello Eyal Shapira,
This is a semi-automatic email about new static checker warnings.
The patch 1ebc8f2ef83d: "iwlwifi: mvm: rs: refactor to allow direct
rs updating" from Sep 14, 2014, leads to the following Smatch
complaint:
drivers/net/wireless/iwlwifi/mvm/rs.c:1228 iwl_mvm_rs_tx_status()
2014-09-30 21:20 GMT+04:00 John W. Linville :
> This patch does not seem to apply to wireless-next. What tree is it
> based upon?
>
> John
>
Its based on linux-mips. I thought that ath5k was not changed in
recent time and did not rebase patch on top of wireless-next.
John, could you delay patch
Hello Mark A. Greer,
The patch 1961843ceeca: "NFC: trf7970a: Handle timeout values of
zero" from Sep 2, 2014, leads to the following static checker warning:
drivers/nfc/trf7970a.c:897 trf7970a_irq()
warn: passing zero to 'ERR_PTR'
drivers/nfc/trf7970a.c
892
This patch adds SD8887 support to mwifiex.
SD8887 is Marvell's 1x1 11ac solution.
The corresponding firmware image file is located at:
"mrvl/sd8887_uapsta.bin"
Signed-off-by: Avinash Patil
Signed-off-by: Cathy Luo
Signed-off-by: Frank Huang
Signed-off-by: Nishant Sarmukadam
Signed-off-by: Ami
This patch adds some more defitions to card specific register structure
and removes static defines for these registers.
Signed-off-by: Avinash Patil
Signed-off-by: Cathy Luo
Signed-off-by: Amitkumar Karwar
---
drivers/net/wireless/mwifiex/sdio.c | 39 +---
drivers/net/wirel
Introduce manual FW recovery mode. It is activated if module parameter
@no_fw_recovery set to true. May be changed at runtime.
Recovery information provided by new "recovery" debugfs file. It prints:
mode = [auto|manual]
state = [idle|pending|running]
In manual mode, after FW error, recovery won
Introduce netdev IOCTLs, to be used by the debug tools.
Allows to read/write single dword value or
memory block, aligned to dword
Different address modes supported:
- BAR offset
- Firmware "linker" address
- target's AHB bus
Signed-off-by: Vladimir Kondratiev
---
MAINTAINERS
2 new features:
- IOCTL API for the card memory access,
- manual FW recovery, to allow FW dump and other debug
Vladimir Kondratiev (2):
wil6210: manual FW error recovery mode
wil6210: atomic I/O for the card memory
MAINTAINERS | 1 +
drivers/net/wireless/ath
From: Sujith Manoharan
MCC fixes. Please review.
Sujith Manoharan (5):
ath9k: Fix queue handling in flush()
ath9k: Pass context to ath9k_chanctx_wake_queues()
ath9k: Add ath9k_chanctx_stop_queues()
ath9k: Fix queue handling for channel contexts
ath9k: Fix flushing in MCC mode
drivers
From: Sujith Manoharan
Change the ath9k_chanctx_wake_queues() API so
that we can pass the channel context that needs its
queues to be stopped.
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/ath9k/ath9k.h | 5 +++--
drivers/net/wireless/ath/ath9k/channel.c | 6 +++---
drivers/ne
From: Sujith Manoharan
This can be used when the queues of a context
needs to be stopped.
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/ath9k/ath9k.h | 5 +
drivers/net/wireless/ath/ath9k/channel.c | 19 +++
2 files changed, 24 insertions(+)
diff --git a/
From: Sujith Manoharan
When a full chip reset is done, all the queues
across all VIFs are stopped, but if MCC is enabled,
only the queues of the current context is awakened,
when we complete the reset.
This results in unfairness for the inactive context.
Since frames are queued internally in the
From: Sujith Manoharan
When draining of the TX queues fails, a
full HW reset is done. ath_reset() makes sure
that the queues in mac80211 are restarted,
so there is no need to wake them up again.
Signed-off-by: Sujith Manoharan
---
drivers/net/wireless/ath/ath9k/main.c | 5 -
1 file changed
From: Sujith Manoharan
When we are attempting to switch to a new
channel context, the TX queues are flushed, but
the mac80211 queues are not stopped and traffic
can still come down to the driver.
This patch fixes it by stopping the queues
assigned to the current context/vif before
trying to flus
From: XYZ
Please ignore this patch
---
net/mac80211/rx.c | 10 --
1 files changed, 8 insertions(+), 2 deletions(-)
--
1.7.3.4
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at h
Dynamic power save timeout value is suppose to be configurable via
wext, but due to iwconfig bug is not possible to set using that tool.
Allow to configure PS timeout via nl80211 - add NL80211_ATTR_PS_TIMEOUT
attribute which become timeout stated in ms.
Signed-off-by: Stanislaw Gruszka
---
v1 ->
On Tue, Sep 30, 2014 at 11:45:57PM -0400, Mark Asselstine wrote:
> 'struct ieee80211_hw' contains 'extra_tx_headroom' which it defines as
> "headroom to reserve in each transmit skb for use by the driver". This
> value is properly setup during rt2x00lib_probe_hw() to account for all
> the rt2x00lib
On 09/30/14 20:43, gree...@candelatech.com wrote:
From: Ben Greear
This is useful when creating virtual-stations, and probably
APs and other devices as well. Keeps udev from mucking with
things it shouldn't, since the default MAC is never seen
by udev when specified on the cmd-line during creat
On 09/30/14 19:44, Ben Greear wrote:
On 09/04/2014 11:33 PM, Johannes Berg wrote:
On Thu, 2014-09-04 at 10:51 -0700, Ben Greear wrote:
I'm having issues with udev renaming newly created stations when I have
udev rules for wlanX, when wlanX is not already existing.
I think specifying MAC on sta
gree...@candelatech.com writes:
> From: Ben Greear
>
> This can allow more than 32 stations to be supported
> without over-running the bitmap.
>
> Signed-off-by: Ben Greear
Thanks, I have applied this patch.
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wire
Kalle Valo writes:
> From: Ben Greear
>
> kvalo: split into it's own patch, add debugfs file and add locking
>
> Signed-off-by: Ben Greear
> Signed-off-by: Kalle Valo
Thanks, both patches applied.
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
42 matches
Mail list logo
