emented such that it only applies to managed
mode and only when the peer identified is the currently connected BSSID.
> On May 27, 2017, at 3:30 PM, Norik Dzhandzhapanyan
> wrote:
>
> Is there an enhanced or conflicting patch pending?
>
>
> On 05/27/2017 10:56 AM, Mich
The submitted code also doesn't appear to handle RSSI per-peer which would be
needed for any use when configured as an access point.
> On May 27, 2017, at 12:39 PM, Adrian Chadd wrote:
>
> On 27 May 2017 at 09:07, Ben Greear wrote:
>> At low encoding rates, especially if it switches to a singl
Symmetry is still broken on firmware crash (at least with 6174).
ath10k_pci_hif_stop gets called twice, once from the driver restart (warm
restart) and once from ieee80211 start (cold restart), resulting in
napi_synchrionize/napi_disable getting called twice and sticking the driver in
an infini
8F0 not 0x004019F0.
> On Apr 27, 2016, at 2:42 AM, Michal Kazior wrote:
>
> On 26 April 2016 at 21:52, Michael Ney wrote:
>
> Firmware can get confused sometimes, especially when it comes to monitor vdev.
>
> Perhaps you should try latest backports or generate one yourse
attributes, so it's definitely on
RX. All other frame types work fine.
Thanks,
Michael
> On Apr 26, 2016, at 2:08 AM, Michal Kazior wrote:
>
> On 25 April 2016 at 22:35, Michael Ney wrote:
>> Hello,
>>
>> I ran into a crash with the QCA6174 firmware and I was h
Hello,
I ran into a crash with the QCA6174 firmware and I was hoping someone knew a
solution to it or could pass it on to Qualcomm Atheros to be resolved.
The hardware version is QCA6174 HW 2.1
The firmware version I am using is SW_RM.1.1.1-00157-QCARMSWPZ-1 (the same
version available for dow
Also, several vendors are advertising QCA9980 and QCA9984 based access points
with 256QAM support in 2.4GHz, such as the TP-Link AD7200 and the Netgear
R7800, both of which advertise 800mbps 4-stream 2.4GHz capabilities.
> On Apr 21, 2016, at 4:09 PM, Sebastian Gottschall
> wrote:
>
> Am 21.
Check the rx_ppdu_start structure in rx_desc.h. The per-antenna values are
populated by the firmware into the rx descripter (verified), which is parsed in
the function "ath10k_htt_rx_h_signal" in htt_rx.c. You would need to implement
something similar to the method in the "ath9k_cmn_process_rssi
Per-antenna rssi is provided by ath10k firmware, but is not currently processed
by the driver; the driver only reports the combined rssi (rssi_comb field). You
can look at the rx_ppdu_start structure in rx_desc.h to see the rssi data
available. I have verified that the pri20_mhz appears to repor
