Add support for WOW disconnect.
Signed-off-by: Janusz Dziedzic
---
drivers/net/wireless/ath/ath10k/core.c| 1 +
drivers/net/wireless/ath/ath10k/core.h| 7 ++
drivers/net/wireless/ath/ath10k/mac.c | 113 ---
drivers/net/wireless/ath/ath10k/wmi-ops.h | 70 +
Add support for WOW magic packet and patterns.
Signed-off-by: Janusz Dziedzic
---
drivers/net/wireless/ath/ath10k/core.h| 1 +
drivers/net/wireless/ath/ath10k/mac.c | 45 ++-
drivers/net/wireless/ath/ath10k/wmi-ops.h | 45 +++
drivers/net/wireless/ath/ath10k/wmi-tlv.
On Thu, Feb 19, 2015 at 5:03 PM, wrote:
> On Fri, 20 Feb 2015 01:53:44 +0100, "Luis R. Rodriguez" said:
>> Wider community:
>>
>> anyone aware of any *need* in the kernel to know whether one is indoor or
>> not on a device running Linux other than wifi? Clearly it should be something
>> that migh
On Fri, 20 Feb 2015 01:53:44 +0100, "Luis R. Rodriguez" said:
> Wider community:
>
> anyone aware of any *need* in the kernel to know whether one is indoor or
> not on a device running Linux other than wifi? Clearly it should be something
> that might be of interest to at least other RF devices, so
Wider community:
anyone aware of any *need* in the kernel to know whether one is indoor or
not on a device running Linux other than wifi? Clearly it should be something
that might be of interest to at least other RF devices, so that is at least
one possibilty to consider already, but what else?
O
Hi Linux-Wireless!
I've noticed that this issue has come up here a few times on this list.
I was really hoping my searching would lead me to a fix, but it
hasn't...so I'm asking for help.
This started happening when I moved into an apartment complex that has
lots of wifi access points. I d
When using the wext compatibility code in cfg80211, part of the IEs
can be truncated if the passed user buffer is large enough for the
BSS but not large enough for all of the IEs. This can cause an EAP
network to show up as a PSK network.
These changes allow the scan to always return -E2BIG in th
On 01/29/2015 03:22 PM, Johannes Berg wrote:
> > What you mean is "with the wext (compatibility) code in cfg80211".
Comment fixed in the v2 of the patch (coming shortly).
> > Either way, I *strongly* recommend against using this in the first
> > place. There's an upper bound of 64k (I think) on
On Fri, Feb 20, 2015 at 1:00 AM, Krishna Chaitanya
wrote:
> Hi Johannes,
>
> The BW tracking feature in mac80211 is causing connection problems and
> operating mode/bw problems when switching b/w modes and bw's in AP.
>
> For Eg. Initially if AP is operating in VHT-80MHz, and then we changed
> in
Hi Johannes,
The BW tracking feature in mac80211 is causing connection problems and
operating mode/bw problems when switching b/w modes and bw's in AP.
For Eg. Initially if AP is operating in VHT-80MHz, and then we changed
in to HT-40MHz, mac80211 cannot handle it because the VHT capability
is mi
On 02/19/2015 03:53 PM, Mário Lopes wrote:
Hi everyone.
When using frame injection over monitor interface, with handmade packet
with Radiotap header + QoS + Data, at sender I capture the packet with
tcpdump and it is equal to the one I sent.
Although, at receiver station, the packet is diferen
On 02/19/2015 11:37 AM, Mike Turner wrote:
Sorry,
I know personal replies aren't liked, however couldn't see how to send a reply
to your reply to my original post. (if you can tell me how to do that then I
will in future)
Anyway, I had already checked the send_beacon_frame() call and it gets ca
Allow user to configure the duty cycle upto 100%. Since thermal
mitigation algorithm is running in user space, remove the driver
level limitation and let the user to control the temperature.
Signed-off-by: Rajkumar Manoharan
---
drivers/net/wireless/ath/ath10k/thermal.h | 2 +-
1 file changed, 1
Duty cycle is nothing but percentage of one period in which a
signal is active. But it is wrongly interpreted as ratio of quiet
duration. So fix the quiet duration to the remaining percentage
of duty cycle (active ratio).
Signed-off-by: Rajkumar Manoharan
---
drivers/net/wireless/ath/ath10k/ther
Add device tree binding documentation for TI's wl18xx
wlan chip.
Signed-off-by: Eliad Peller
---
v3:
* make the bindings device-specific (wl18xx) (Arnd, Mark)
* split bindings and driver changes (Arnd)
* make interrupt-parent optional (Arnd)
* make unit-address same as reg (Mark)
.../device
When running with device-tree, we no longer have a board file
that can set up the platform data for wlcore.
Allow this data to be passed from DT.
For now, parse only the irq used. Other (optional) properties
can be added later on.
Signed-off-by: Ido Yariv
Signed-off-by: Eliad Peller
---
driver
Hi everyone.
When using frame injection over monitor interface, with handmade
packet with Radiotap header + QoS + Data, at sender I capture the
packet with tcpdump and it is equal to the one I sent.
Although, at receiver station, the packet is diferent, FCS was
recalculated or forced to act
Hi Larry,
On 02/18/2015 09:24 PM, Larry Finger wrote:
> On 02/18/2015 01:51 PM, Jon Hunter wrote:
>> When using the rtl8192cu in AP mode a few devices (an android phone,
>> iphone and ipad) were unable to associate, where as the laptops I tried
>> could. Using wireshark to sniff the wlan traffic,
This fix is specific to ath10K driver + 10.x firmware combinations. This has
been tested extensively, didn't observe the mentioned issue.
Thanks,
Senthil J
-Original Message-
From: Ben Greear [mailto:gree...@candelatech.com]
Sent: Thursday, February 19, 2015 1:53 AM
To: Salakava Jegadee
On Thu, Feb 19, 2015 at 12:51 PM, Vladimir Kondratiev
wrote:
>
> I am looking for ideas how can one process AMSDU in the software, without
> copying data.
> Current implementation like ieee80211_amsdu_to_8023s() do copy packet data.
>
> Assume I got in the driver, MPDU that is AMSDU containing se
I am looking for ideas how can one process AMSDU in the software, without
copying data.
Current implementation like ieee80211_amsdu_to_8023s() do copy packet data.
Assume I got in the driver, MPDU that is AMSDU containing several MSDU's.
It is in the single memory buffer that was allocated for DM
On 2015-02-10 11:34, Yuwei Zheng wrote:
> The ath9k_hif_usb_rx_cb function excute on the interrupt context, and
> ath9k_rx_tasklet excute
> on the soft irq context. In other words, the ath9k_hif_usb_rx_cb have more
> chance to excute than
> ath9k_rx_tasklet. So in the worst condition, the rx.r
22 matches
Mail list logo
