Re: [PATCH 3/3] ath10k: implement mesh support

2015-09-09 Thread Kalle Valo
Bob Copeland writes: > Add support for mesh to ath10k. We simply use an AP virtual interface > in the firmware in order to enable beaconing without TSF adoption, and > use the raw (802.11) transmit mode. > > Due to firmware limitations, the firmware must operate in raw >

[PATCH 2/4] staging: wilc1000: delete wilc_memory.c and wilc_memory.h

2015-09-09 Thread Tony Cho
From: Glen Lee The macro WILC_MALLOC is not used in the driver anymore, so just delete files. Signed-off-by: Glen Lee Signed-off-by: Tony Cho --- drivers/staging/wilc1000/Makefile | 2 +-

[PATCH 4/4] staging: wilc1000: remove unused PLAT_RK3026_TCHIP

2015-09-09 Thread Tony Cho
From: Leo Kim This patch removes the preprocessor definition, PLAT_RK3026_TCHIP which is not used anymore. Signed-off-by: Leo Kim Signed-off-by: Tony Cho --- drivers/staging/wilc1000/wilc_wlan.c | 24 1 file

[PATCH 3/4] staging: wilc1000: delete wilc_oswrapper.h and wilc_platform.h

2015-09-09 Thread Tony Cho
From: Glen Lee wilc1000 driver runs on Linux. No need to have oswrapper or platform dependent files. Before delete two header files, move two structures in wilc_platform.h to wilc_msgqueue.h where it is used. Include linux header files where is needs since wilc_platform is

[PATCH] ath10k: add ATH10K_FW_FEATURE_RAW_MODE_SUPPORT to ath10k_core_fw_feature_str[]

2015-09-09 Thread Kalle Valo
This was missed in the original commit adding the flag and ath10k only printed "bit10": ath10k_pci :02:00.0: qca988x hw2.0 (0x4100016c, 0x043202ff) fw 10.2.4.70.6-2 api 3 htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1 features no-p2p,bit10 Also add a build test to

Re: [PATCH 4/5] staging: wilc1000: wilc_msgqueue.c: use kmalloc with GFP_ATOMIC

2015-09-09 Thread Sudip Mukherjee
On Tue, Sep 08, 2015 at 12:36:38AM +0900, Chaehyun Lim wrote: > This patch use kmalloc with GFP_ATOMIC instead of WILC_MALLOC. > It is inside the spin lock region. > > Signed-off-by: Chaehyun Lim > --- Its not related to your patch, but while seeing your patch I thought

[PATCH 1/4] staging: wilc1000: remove kmalloc wrapper

2015-09-09 Thread Tony Cho
From: Glen Lee Call kmalloc directly. No need to wrap kmalloc. Only one function, wilc_mq_send which use WILC_MALLOC, can be running in interrupt context or process context. In this case, We call in_interrupt to decide the flag, GFP_ATOMIC or GFP_KERNEL, for kmalloc properly.

Re: [PATCH 3/3] ath10k: implement mesh support

2015-09-09 Thread Kalle Valo
Kalle Valo writes: > Bob Copeland writes: > >> Add support for mesh to ath10k. We simply use an AP virtual interface >> in the firmware in order to enable beaconing without TSF adoption, and >> use the raw (802.11) transmit mode. >> >> Due to

[PATCHv2] mac80211: Copy tx'ed beacons to monitor mode

2015-09-09 Thread Helmut Schaa
When debugging wireless powersave issues on the AP side it's quite helpful to see our own beacons that are transmitted by the hardware/driver. However, this is not that easy since beacons don't pass through the regular TX queues. Preferably drivers would call ieee80211_tx_status also for tx'ed

Re: [PATCH] ath10k: Fix DMA alloc failure for target requested memory chunks

2015-09-09 Thread Kalle Valo
Vasanthakumar Thiagarajan writes: > During long hours of stress testing like AP interface up/down along > with continuous ping flood from a station doing connect/disconnect, > it is observed that the system is not able to allocate DMA consistent > memory of size >

Re: [PATCH 2/2] ath10k: fix mu-mimo rx status reporting

2015-09-09 Thread Kalle Valo
Michal Kazior writes: > MU-MIMO Rx involves different interpretation of > the VHT-SIG-A compared to SU-MIMO. > > The incorrect interpretation led ath10k to report > VHT MCS values greater than 9 which subsequently > prompted mac80211 to drop such frames. This >

Re: [PATCH] ath10k: Drop probe responses when too many are queued

2015-09-09 Thread Kalle Valo
Vivek Natarajan writes: > In a noisy environment, when multiple interfaces are created, > the management tx descriptors are fully occupied by the probe > responses from all the interfaces. This prevents a new station > from a successful association. > > Fix this by

Re: [PATCH 3/3] ath10k: implement mesh support

2015-09-09 Thread Bob Copeland
On Wed, Sep 09, 2015 at 10:57:30AM +0300, Kalle Valo wrote: > I did a quick smoke test and saw the splat below. It's this warning from > cfg80211: > > /* >* Don't advertise an unsupported type >* in a combination. >

Re: [PATCH 1/2] ath10k: fix beamformee VHT STS capability

2015-09-09 Thread Kalle Valo
Bartosz Markowski writes: > The VHT STS CAP shall be reported by firmware to host, like in case of > QCA99x0. For QCA6174 hw family this isn't set for some reason. > So for this particular chips, let's assume it has the ability to > support VHT NDP in up to 4 STSs

Re: [PATCH v2 0/1] rtl8xxxu (mac80211) driver for rtl8188[cr]u/rtl8192cu/rtl8723au

2015-09-09 Thread Bruno Randolf
On 09/08/2015 10:01 PM, Jes Sorensen wrote: > I do not fully agree on this. In my testing I found rtl8192cu rather > unstable, to the point of not being usable. It would lock up for me > after a short while. I have seen this happen with mulitple different > adapters. I suspect this is the reason

Re: [PATCH v2] ath: use PRI value given by spec for fixed PRI

2015-09-09 Thread Kalle Valo
Peter Oh writes: > PRI value is used as divider when DFS detector analyzes candidate > radar pulses. > If PRI deviation is big from its origin PRI, DFS detector could miss > valid radar reports since HW often misses detecting radar pulses and > causes long interval value

Re: [PATCH] ath10k: invalid mcs reported in rx descriptor

2015-09-09 Thread Kalle Valo
writes: > From: Manikanta Pubbisetty > > Sometimes hardware reports invalid mcs index in rx descriptor > when operating in VHT80 mode and all packets with invalid mcs > will be eventually dropped in mac80211. This issue is observerd during >

[PATCH] ath9k: Add support for OCB mode

2015-09-09 Thread Jan Kaisrlik
The patch adds support for "outside the context of a BSS"(OCB) mode to ath9k driver and extends debugfs files by OCB ralated information. This patch was tested on AR9380-AL1A cards. Signed-off-by: Jan Kaisrlik Cc: Michal Sojka ---

Re: iwlwifi: FW error in SYNC CMD MAC_CONTEXT_CMD

2015-09-09 Thread Andreas Reis
Hi, > seems that your system is trying to connect to two different APs forth and back Yes, this is a major network with multiple APs for each of its SSIDs always available. Unlike my single AP home network, unsurprisingly. > whether you have more than wpa_supplicant instance running I

Re: [PATCH 1/1] New driver: rtl8723au (mac80211)

2015-09-09 Thread Jes Sorensen
Larry Finger writes: > On 09/07/2015 01:43 PM, Jes Sorensen wrote: >> Kalle Valo writes: >>> Hi, >>> >>> replying to an old thread first. >>> >>> Jes Sorensen writes: >>> Kalle Valo writes:

Re: [PATCH] ath9k: Add support for OCB mode

2015-09-09 Thread Felix Fietkau
On 2015-09-09 14:55, Jan Kaisrlik wrote: > The patch adds support for "outside the context of a BSS"(OCB) mode > to ath9k driver and extends debugfs files by OCB ralated information. > > This patch was tested on AR9380-AL1A cards. > > Signed-off-by: Jan Kaisrlik > Cc:

Re: [PATCH 3/4] staging: wilc1000: delete wilc_oswrapper.h and wilc_platform.h

2015-09-09 Thread Tony Cho
Hi Greg, I want to make sure one thing before moving further. Are you saying the errorsupport.h file as the os wrapper remaining in the oswrapper.h file? If not, can you let me know what you point out as remaining os wrapper in the oswrapper.h file? If yes, I have been already replacing all of

Re: [PATCH 1/4] staging: wilc1000: remove kmalloc wrapper

2015-09-09 Thread Tony Cho
On 2015년 09월 10일 03:17, Greg KH wrote: On Wed, Sep 09, 2015 at 04:08:10PM +0900, Tony Cho wrote: From: Glen Lee Call kmalloc directly. No need to wrap kmalloc. Only one function, wilc_mq_send which use WILC_MALLOC, can be running in interrupt context or process context.

Re: [PATCH 3/4] staging: wilc1000: delete wilc_oswrapper.h and wilc_platform.h

2015-09-09 Thread Greg KH
On Thu, Sep 10, 2015 at 11:08:25AM +0900, Tony Cho wrote: > Hi Greg, > > I want to make sure one thing before moving further. Are you saying > the errorsupport.h file as the os wrapper remaining in the oswrapper.h > file? If not, can you let me know what you point out as remaining os > wrapper

[PATCH] staging: wilc1000: remove BROKEN status

2015-09-09 Thread Tony Cho
This patch removes BROKEN status from the Kconfig. Signed-off-by: Tony Cho --- drivers/staging/wilc1000/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/wilc1000/Kconfig b/drivers/staging/wilc1000/Kconfig index 51bbf46..59ccecc 100644 ---

[PATCH v2 1/2] staging: wilc1000: remove kmalloc wrapper

2015-09-09 Thread Tony Cho
From: Glen Lee This patch calls kmalloc() directly. No need to wrap kmalloc(). All is not holding a spin lock or in interrupt context. So use GFP_KERNEL flag for kmalloc. Signed-off-by: Glen Lee Signed-off-by: Tony Cho ---

[PATCH v2 2/2] staging: wilc1000: delete wilc_memory.c and wilc_memory.h

2015-09-09 Thread Tony Cho
From: Glen Lee The macro WILC_MALLOC is not used in the driver anymore, so just delete files. Signed-off-by: Glen Lee Signed-off-by: Tony Cho --- drivers/staging/wilc1000/Makefile | 2 +-

Re: [PATCH 3/3] ath10k: implement mesh support

2015-09-09 Thread Kalle Valo
Bob Copeland writes: > On Wed, Sep 09, 2015 at 12:10:38PM +0300, Kalle Valo wrote: >> > I did a quick smoke test and saw the splat below. It's this warning from >> > cfg80211: >> > >> >/* >> > * Don't advertise an unsupported type >>

[PATCH] ath: fix incorrect PPB on JAPAN chirp radar

2015-09-09 Thread Peter Oh
The number of pulses per burst on Japan chirp radar is between 1 and 3. The previous value, 20, is representing number of bursts, but since current DFS detector is using pulse detection other than bursts, use the pulse number for correct radar detection. Also using the highest number helps to

[PATCH] net/mac80211/rate.c: fix wrong sizeof()

2015-09-09 Thread Sergei Trofimovich
From: Sergei Trofimovich Noticed by gcc-5.2.0: net/mac80211/rate.c: In function 'rate_control_cap_mask': net/mac80211/rate.c:719:25: warning: 'sizeof' on array function parameter 'mcs_mask' will return size of 'u8 * {aka unsigned char *}' [-Wsizeof-array-argument]

[PATCH v3 3/3] ath10k: implement mesh support

2015-09-09 Thread Bob Copeland
Add support for mesh to ath10k. We simply use an AP virtual interface in the firmware in order to enable beaconing without TSF adoption, and use the raw (802.11) transmit mode. Due to firmware limitations, the firmware must operate in raw (non-native 802.11) mode. As this is configured at

[PATCH v3 1/3] ath10k: enable monitor when OTHER_BSS requested

2015-09-09 Thread Bob Copeland
By default, ath10k restricts received frames to those matching BSSID. When other BSS frames are requested (e.g. in mesh mode), add an internal monitor device so those frames are not filtered. Signed-off-by: Bob Copeland --- drivers/net/wireless/ath/ath10k/mac.c | 1 + 1

[PATCH v3 2/3] ath10k: check for encryption before adding MIC_LEN

2015-09-09 Thread Bob Copeland
In the case of raw mode without nohwcrypt parameter, we should still make sure the frame is protected before adding MIC_LEN to avoid skb_under_panic errors. Signed-off-by: Bob Copeland --- drivers/net/wireless/ath/ath10k/htt_tx.c | 3 ++- 1 file changed, 2 insertions(+), 1

Ath10K issue

2015-09-09 Thread Cedric VONCKEN
I'm using compat-wireless 2015-03-09 from openwrt. At the power up, these equipments worked in AP mode and several sta can do an association. Randomly it is not possible to make association to several AP. If I look the log file I see cyclically these error

Re: [PATCH 3/3] ath10k: implement mesh support

2015-09-09 Thread Bob Copeland
On Wed, Sep 09, 2015 at 12:10:38PM +0300, Kalle Valo wrote: > > I did a quick smoke test and saw the splat below. It's this warning from > > cfg80211: > > > > /* > > * Don't advertise an unsupported type > > * in a combination. > >

[PATCH v2] ath: use PRI value given by spec for fixed PRI

2015-09-09 Thread Peter Oh
PRI value is used as divider when DFS detector analyzes candidate radar pulses. If PRI deviation is big from its origin PRI, DFS detector could miss valid radar reports since HW often misses detecting radar pulses and causes long interval value of pulses. For instance from practical results, if

Re:

2015-09-09 Thread Oleg Kostyuchenko
Hi Arend, I am still experiencing the issue Sebastien initially described (no wlan0 device, "SDIO drive strength" warnings etc) on a Thinkpad Tablet 10 for the latest kernel release, 4.2. Doesn't the 4.2 kernel include the required fix? Thanks, Oleg -- To unsubscribe from this list: send the

Re: [PATCH 1/4] staging: wilc1000: remove kmalloc wrapper

2015-09-09 Thread Greg KH
On Wed, Sep 09, 2015 at 04:08:10PM +0900, Tony Cho wrote: > From: Glen Lee > > Call kmalloc directly. No need to wrap kmalloc. > Only one function, wilc_mq_send which use WILC_MALLOC, can be running in > interrupt context or process context. In this case, We call in_interrupt

Re: [PATCH 1/5] staging: wilc1000: define undefined operation mode

2015-09-09 Thread Greg KH
On Tue, Sep 08, 2015 at 05:07:59PM +0900, Tony Cho wrote: > From: Johnny Kim > > This patch adds new define, IDLE_MODE to change comparison statement which > is wrong due to typecasting to null. > > Signed-off-by: Johnny Kim > Signed-off-by: Tony Cho

Re: [PATCH 3/4] staging: wilc1000: delete wilc_oswrapper.h and wilc_platform.h

2015-09-09 Thread Greg KH
On Wed, Sep 09, 2015 at 04:08:12PM +0900, Tony Cho wrote: > From: Glen Lee > > wilc1000 driver runs on Linux. No need to have oswrapper or platform > dependent files. > Before delete two header files, move two structures in wilc_platform.h to > wilc_msgqueue.h where it is