'commit 418ca5992e2f (ath10k: Make target cpu address to
CE address conversion chip specific)' mask 0x7fff is added
by mistake instead of 0x7ff. Fix this regression.
Signed-off-by: Vasanthakumar Thiagarajan vthia...@qti.qualcomm.com
---
drivers/net/wireless/ath/ath10k/pci.c | 2 +-
1 file
On Fri, Jul 3, 2015 at 4:08 AM, Zefir Kurtisi zefir.kurt...@neratec.com wrote:
On 07/02/2015 07:44 AM, Wei Zhong wrote:
commit 2fef4cad8a1bd9cbbf178e59a1b3ca672b057095
Author: Wei Zhong wzh...@google.com
Date: Wed Jul 1 22:39:09 2015 -0700
wireless-regdb: update CA rules for 5600
On 07/03/2015 04:20 PM, Wei Zhong wrote:
On Fri, Jul 3, 2015 at 4:08 AM, Zefir Kurtisi zefir.kurt...@neratec.com
wrote:
On 07/02/2015 07:44 AM, Wei Zhong wrote:
commit 2fef4cad8a1bd9cbbf178e59a1b3ca672b057095
Author: Wei Zhong wzh...@google.com
Date: Wed Jul 1 22:39:09 2015 -0700
commit a521ee983d312db7 ath10k: Add new reg_address/mask to hw register
table commit has broken the QCA61x4 support, by providing wrong
fw_indicator_address, which shall be 0x0003a028 instead of 0x9028.
User experience was a failing boot up sequence (crashing device during
initialization)
[
Am 03.07.2015 um 12:53 schrieb Kalle Valo:
Oleksij Rempel li...@rempel-privat.de writes:
Any updates here?
What do you mean? If you are asking why the patch isn't applied it's
because merge window is still open. I'll start applying patches after
net-next is open again.
Ouch.. i was in my
On Fri, 2015-07-03 at 18:51 +0200, Zefir Kurtisi wrote:
Folks,
I have difficulties using iw for a specific use case or fail to
understand the documentation correctly.
My platform is a recent OpenWRT, running ath9k.
First use case is scanning for a given ssid in managed mode.
Folks,
I have difficulties using iw for a specific use case or fail to understand the
documentation correctly.
My platform is a recent OpenWRT, running ath9k.
First use case is scanning for a given ssid in managed mode. According do iw's
documentation (and the attribute description in
2015-07-03 18:59 GMT+09:00 Bruno Randolf b...@thinktube.com:
On 07/03/2015 10:34 AM, Richard Palethorpe wrote:
Hello Taehee,
I have been experimenting with MESH mode on kernel 4.0.7. It is
sending beacons out, but is unable to establish a connection.
I have two rtl8192cu based dongles
According to 802.11-2012 13.3.1, a mesh STA should assign an AID
upon receipt of a mesh peering open frame rather than using the link
id of the peer. Using the peer link id has two potential issues:
it may not be unique among the peers, and by its nature it is random,
so the TIM may not compress
Instead of using peer link id for AID, generate a new
AID when creating mesh STAs in the kernel peering manager.
This enables smaller TIM elements and more closely follows
the standard, and it also enables mesh to work on drivers
that require a valid AID when the STA is inserted (ath10k
firmware
Move mesh_plink_frame_tx() above the first caller to remove
the forward declaration.
Signed-off-by: Bob Copeland m...@bobcopeland.com
---
net/mac80211/mesh_plink.c | 109 ++
1 file changed, 52 insertions(+), 57 deletions(-)
diff --git
This patchset corrects the use of peer link id as a stand-in for the
association ID, which is at odds with the standard. Using an incremental
AID generated on the local sta whenever a peer is added enables smaller
TIM elements, and removes one possible source of ambiguity when plids
collide.
From: Miaoqing Pan miaoq...@qca.qualcomm.com
We measured the ADC-based entropy in 3 ways, Shannon entropy,
collision entropy, and directly measured min-entropy. Entropy is
in bits per 16 bit value,
---
Shannon | collision | min
---
12.00
Hi John,
From: John W. Linville [mailto:linvi...@tuxdriver.com]
Sent: Saturday, June 27, 2015 1:00 AM
To: linux-wireless@vger.kernel.org
Cc: Amitkumar Karwar; Nishant Sarmukadam; Kalle Valo; John W. Linville
Subject: [PATCH] mwifiex: fix leak of gen_ie storage on exit from
On Fri, 2015-07-03 at 15:29 +0800, miaoq...@qti.qualcomm.com wrote:
+config ATH9K_HWRNG
+ bool Random number generator support
+ depends on ATH9K (HW_RANDOM = y || HW_RANDOM = ATH9K)
+ default n
you don't need to state 'default n'
+void ath9k_rng_unregister(struct ath_softc
From: Miaoqing Pan miaoq...@qca.qualcomm.com
We measured the ADC-based entropy in 3 ways, Shannon entropy,
collision entropy, and directly measured min-entropy. Entropy is
in bits per 16 bit value,
---
Shannon | collision | min
---
12.00
It is observed that during cold reset pcie access right
after a write operation to SOC_GLOBAL_RESET_ADDRESS causes
Data Bus Error and system hard lockup. The reason
for bus error is that pcie needs some time to get
back to stable state for any transaction during cold reset. Add
delay of 20 msecs
Hello Taehee,
I have been experimenting with MESH mode on kernel 4.0.7. It is
sending beacons out, but is unable to establish a connection.
I have two rtl8192cu based dongles connected to identical VMs and am
using the following commands to set up the mesh:
iw dev wls160u2 set type mesh
ip addr
Hi Reyad,
From: Reyad Attiyat [mailto:reyad.atti...@gmail.com]
Sent: Monday, June 29, 2015 6:38 AM
To: Amitkumar Karwar; pat...@marvell.com; kv...@codeaurora.org;
bz...@marvell.com
Cc: linux-wireless@vger.kernel.org; net...@vger.kernel.org; linux-
ker...@vger.kernel.org; Reyad Attiyat
+/* Bit definitio for MACREG_REG_A2H_INTERRUPT_CAUSE (A2HRIC) */
typo
+/* Bit definitio for MACREG_REG_H2A_INTERRUPT_CAUSE (H2ARIC) */
same here
+struct mwl_chip_info {
+ char *part_name;
+ char *fw_image;
+};
const char *?
+struct mwl_tx_hndl {
+ struct sk_buff
On 07/03/2015 10:34 AM, Richard Palethorpe wrote:
Hello Taehee,
I have been experimenting with MESH mode on kernel 4.0.7. It is
sending beacons out, but is unable to establish a connection.
I have two rtl8192cu based dongles connected to identical VMs and am
using the following commands
Oleksij Rempel li...@rempel-privat.de writes:
Any updates here?
What do you mean? If you are asking why the patch isn't applied it's
because merge window is still open. I'll start applying patches after
net-next is open again.
--
Kalle Valo
--
To unsubscribe from this list: send the line
On 07/02/2015 07:44 AM, Wei Zhong wrote:
commit 2fef4cad8a1bd9cbbf178e59a1b3ca672b057095
Author: Wei Zhong wzh...@google.com
Date: Wed Jul 1 22:39:09 2015 -0700
wireless-regdb: update CA rules for 5600 - 5650 mHz
Related regulation:
23 matches
Mail list logo
