[PATCH v2] ath10k: Convert wow pattern from 802.3 to 802.11

2018-04-11 Thread Wen Gong
When trying to set wow wakeup patterns it fails with this command: iw phyxx wowlan enable patterns offset xx+ IP address xx.xx.xx.xx The reason is that the wow pattern from upper layer is in 802.3 format for this case, it need to convert it to 802.11 format. The input offset parameter is used for

Re: [PATCH] ath10k: Convert wow pattern from 802.3 to 802.11

2018-04-11 Thread Wen Gong
Hi, I will move the convert graph from comments to code and send Patch V2. And new graph like this: /** + * Convert a 802.3 format to a 802.11 format. + * ++---+++ + * 802.3:  |dest mac(6B)|src mac(6B)|type(2B)| body...    | + * +---

[PATCH] ath10k:add support for multicast rate control

2018-04-11 Thread Pradeep Kumar Chitrapu
Issues wmi command to firmware when multicast rate change is received with the new BSS_CHANGED_MCAST_RATE flag. Signed-off-by: Pradeep Kumar Chitrapu --- drivers/net/wireless/ath/ath10k/mac.c | 25 - 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/drivers/ne

RE: [PATCH] ath10k: Convert wow pattern from 802.3 to 802.11

2018-04-11 Thread Wen Gong
Hi, I will move the convert graph from comments to code. And new graph like this: /** + * Convert a 802.3 format to a 802.11 format. + * ++---+++ + * 802.3: |dest mac(6B)|src mac(6B)|type(2B)| body...| + * ++-

Re: [PATCH] ath10k: Convert wow pattern from 802.3 to 802.11

2018-04-11 Thread Brian Norris
Hi, On Fri, Mar 30, 2018 at 11:18:19AM +0800, Wen Gong wrote: > When trying to set wow wakeup patterns it fails with this command: > > iw phyxx wowlan enable patterns offset xx+ IP address xx.xx.xx.xx > > The reason is that the wow pattern from upper layer is in 802.3 format > for this case, it

Re: Please add new board files for WLE1216V5-20 and another Compex NIC.

2018-04-11 Thread Tim Harvey
On Wed, Mar 21, 2018 at 2:59 PM, Ben Greear wrote: > Hello, > > It seems the upstream board-2.bin file for 9984 does not yet include support > for WLE1216V5-20 > (or possibly it does and OpenWRT grabs the wrong one?). > > I'm attaching the board file for this NIC and for another one which > I have