On Tue, 2017-10-24 at 02:29 -0700, Kees Cook wrote:
> In preparation for unconditionally passing the struct timer_list
> pointer to
> all timer callbacks, switch to using the new timer_setup() and
> from_timer()
> to pass the timer pointer explicitly.
>
> The RCU lifetime on baid_data is unclear,
This patch converts the few remaining rules specified in mW to directly
equivalent rules in dBm, to improve consistency of the regdb.
Signed-off-by: Ryan Mounce
---
db.txt | 64
1 file changed, 32
Seems to work okay on mixed networks of 9882, 4019 and 9888.
On Tue, Oct 24, 2017 at 1:41 PM, Sebastian Gottschall
wrote:
> patch works. tested in sta and ap mode so far on 9984
>
> Am 24.10.2017 um 19:54 schrieb Kalle Valo:
>>
>> From: Vasanthakumar Thiagarajan
Summary: WARN_ON(iwl_mvm_is_dqa_supported(mvm)) in
iwl_mvm_rx_tx_cmd_single with v4.13, but code is since changed.
On Tue, Oct 24, 2017 at 09:56:31PM +0200, Mario Theodoridis wrote:
> Sorry for skipping the list one the last one.
Sorry, that was my fault. It was a private message you replied
On 10/24/2017 06:55 AM, Johannes Berg wrote:
On Tue, 2017-10-24 at 06:50 -0700, Ben Greear wrote:
We keep having this discussion. You need to fix this, it should be
really simple to fix this - just remove all checks for CONF_MONITOR
from ath10k and make it use WANT_MONITOR_VIF instead if it
Sorry for skipping the list one the last one.
On 19.10.2017 22:59, James Cameron wrote:
On Thu, Oct 19, 2017 at 08:56:46AM +0200, Mario Theodoridis wrote:
On 18/10/17 23:33, James Cameron wrote:
For your interest, kernel v4.4.93 in stable series just released has
changes in relevant
will test it and report success (or not)
Am 24.10.2017 um 19:54 schrieb Kalle Valo:
From: Vasanthakumar Thiagarajan
Rx data frames notified through HTT_T2H_MSG_TYPE_RX_IND and
HTT_T2H_MSG_TYPE_RX_FRAG_IND expect PN/TSC check to be done
on host (mac80211) rather than
That can't be the case here, since we see it break the mesh too (where
the clients are other QCA radios.)
We're now seeing very slow mesh peering with a 9882 leaf to a 4019
gateway, with the second version of this patch.
It took more than five minutes for one of the leaves to successfully
peer
From: Vasanthakumar Thiagarajan
Rx data frames notified through HTT_T2H_MSG_TYPE_RX_IND and
HTT_T2H_MSG_TYPE_RX_FRAG_IND expect PN/TSC check to be done
on host (mac80211) rather than firmware. Rebuild cipher header
in every received data frames (that are notified
On 10/23/2017 09:50 PM, Kalle Valo wrote:
Jasmine Strong writes:
That's what I saw. A bcom client was able to associate and not pass
any traffic. This is on all three of 9882, 9888 and 4019.
Thanks for the report, we'll investigate it. And I see that your email
was now
On Tue, 2017-10-24 at 06:50 -0700, Ben Greear wrote:
> > We keep having this discussion. You need to fix this, it should be
> > really simple to fix this - just remove all checks for CONF_MONITOR
> > from ath10k and make it use WANT_MONITOR_VIF instead if it doesn't
> > already.
>
> I don't
On 10/24/2017 06:38 AM, Johannes Berg wrote:
On Tue, 2017-10-24 at 06:36 -0700, Ben Greear wrote:
On 10/23/2017 10:54 PM, Johannes Berg wrote:
On Mon, 2017-10-23 at 13:59 -0700, Ben Greear wrote:
The CSI data has variable length [1] but it's fundamentally always tied
to a specific frame
On Tue, 2017-10-24 at 06:36 -0700, Ben Greear wrote:
>
> On 10/23/2017 10:54 PM, Johannes Berg wrote:
> > On Mon, 2017-10-23 at 13:59 -0700, Ben Greear wrote:
> >
> > > > The CSI data has variable length [1] but it's fundamentally always tied
> > > > to a specific frame and as such we've always
On 10/23/2017 10:54 PM, Johannes Berg wrote:
On Mon, 2017-10-23 at 13:59 -0700, Ben Greear wrote:
The CSI data has variable length [1] but it's fundamentally always tied
to a specific frame and as such we've always attached it to that frame
using a radiotap vendor namespace.
You can easily
Hey Linux wireless list,
A while ago I bought an ALFA Network AWUS036AC[0] which does not yet
seem to be supported in Linux mainline. I would like to get it supported.
The problem is that I have not that much experience doing software
development.
kind regards
txt.file
PS: Please keep me in CC
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Kalle Valo
Cc: Igor Mitsyanko
Cc: Avinash Patil
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Solomon Peachy
Cc: Kalle Valo
Cc:
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Kalle Valo
Cc: Stanislaw Gruszka
Cc:
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Simon Kelley
Cc: Kalle Valo
Cc:
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Kalle Valo
Cc: Amitkumar Karwar
Cc: Prameela
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Kalle Valo
Cc: linux-wireless@vger.kernel.org
Cc: net...@vger.kernel.org
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
The RCU lifetime on baid_data is unclear, so this adds a direct copy of the
rcu_ptr passed to the original
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Kalle Valo
Cc: Arvind Yadav
Cc: Ingo Molnar
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Kalle Valo
Cc: Larry Finger
Cc: Chaoming Li
Hi
The content of db.txt for Denmark (DK) is wrong. The 5GHz is from some
where between 2002-2006, and the 2.4GHz has never been correct.
Current content of db.txt:
--
country DK: DFS-ETSI
(2402 - 2482 @ 40), (20)
(5170 - 5250 @ 80), (20), AUTO-BW
From: Yingying Tang
This patchset is for Rome PCIE chip, it will not affect other hardware
Yingying Tang (5):
mac80211: Enable TDLS peer buffer STA feature
ath10k: Enable TDLS peer buffer STA feature
ath10k: Enable TDLS peer inactivity detection
ath10k: Avoid
From: Yingying Tang
Enable TDLS peer inactivity detetion feature.
QCA6174 firmware(version: WLAN.RM.4.4) support TDLS link inactivity detecting.
Set related parameters in TDLS WMI command to enable this feature.
Signed-off-by: Yingying Tang
From: Yingying Tang
Enable TDLS peer buffer STA feature.
QCA6174 firmware(version: WLAN.RM.4.4) support TDLS peer buffer STA,
it reports this capability through wmi service map in wmi service ready
event. Set related parameter in TDLS WMI command to enable this feature.
From: Yingying Tang
For WPA encryption, QCA6174 firmware(version: WLAN.RM.4.4) will unblock
data when M4 was sent successfully. For other encryption which didn't need
4-way handshake firmware will unblock the data when peer authorized. Since
TDLS is 3-way handshake host
From: Yingying Tang
Enable TDLS peer buffer STA feature.
Set extended capability bit to enable buffer STA when driver
support it.
Signed-off-by: Yingying Tang
---
include/net/mac80211.h |4
net/mac80211/debugfs.c |1 +
From: Yingying Tang
TDLS peer do not need WEP key. Setting WEP key will lead
to TDLS setup failure. Add fix to avoid setting WEP key
for TDLS peer.
Signed-off-by: Yingying Tang
---
drivers/net/wireless/ath/ath10k/mac.c |2 +-
1 file
31 matches
Mail list logo