[PATCH] Per chain RSSI reporting

Norik Dzhandzhapanyan norikd at ethertronics.com
Sat May 27 12:31:14 PDT 2017

Is there an enhanced or conflicting patch pending?

On 05/27/2017 10:56 AM, Michael Ney wrote:
> 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 <adrian at freebsd.org> wrote:
>> On 27 May 2017 at 09:07, Ben Greear <greearb at candelatech.com> wrote:
>>> At low encoding rates, especially if it switches to a single-chain encoding,
>>> maybe the on-air signal really is stronger?
>>> Have you verified in some other manner than the signals reported by ath10k
>>> are
>>> wrong?
>> Hiya,
>> So yeah, multipath, higher TX rates == weaker TX signal, TPC, etc are
>> all interesting to know about at the receiver. it's hard to separate
>> that out from the noise sometimes, but in some controlled deployments
>> its really obvious.
>> -adrian
>> _______________________________________________
>> ath10k mailing list
>> ath10k at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k

The contents of this transmission are Ethertronics Inc. Confidential and may contain proprietary or legally privileged information which may not be disclosed, copied or distributed without the express written consent of Ethertronics Inc. The information is intended to be for the use of the individual or entity named on this transmission. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this transmission in error, please notify us by telephone immediately so that we can arrange for the retrieval of the original documents at no cost to you. Alternatively, notify the sender by replying to this transmission and delete the message without disclosing it. Thank you

More information about the ath10k mailing list