From: Ben Greear <greearb@candelatech.com>
To: Norik Dzhandzhapanyan <norikd@ethertronics.com>,
Adrian Chadd <adrian@freebsd.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] Per chain RSSI reporting
Date: Sat, 27 May 2017 14:38:30 -0700 [thread overview]
Message-ID: <50e245a7-60ad-39f1-920e-e8edf5d9a5ab@candelatech.com> (raw)
In-Reply-To: <8e314337-a1f0-5ed4-aa90-3f1a0e2d09fc@ethertronics.com>
On 05/27/2017 12:25 PM, Norik Dzhandzhapanyan wrote:
> We see this inconsistent/incorrect reporting in our RF chamber.
How different are the values, and did you sniff with a third-party device
to see if it sees the same spikes in RSSI?
Thanks,
Ben
>
> Norik
>
> On 05/27/2017 09:39 AM, Adrian Chadd wrote:
>> On 27 May 2017 at 09:07, Ben Greear <greearb@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
>>
>>
>
>
> 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
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-05-27 21:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 22:49 [PATCH] Per chain RSSI reporting Norik Dzhandzhapanyan
2017-05-27 1:12 ` Adrian Chadd
2017-05-27 2:09 ` Norik Dzhandzhapanyan
2017-05-27 8:30 ` Norik Dzhandzhapanyan
2017-05-27 16:07 ` Ben Greear
2017-05-27 16:39 ` Adrian Chadd
2017-05-27 17:56 ` Michael Ney
2017-05-27 19:30 ` Norik Dzhandzhapanyan
2017-05-27 22:10 ` Michael Ney
2017-05-28 1:22 ` Norik Dzhandzhapanyan
2017-05-27 19:31 ` Norik Dzhandzhapanyan
2017-05-27 19:25 ` Norik Dzhandzhapanyan
2017-05-27 21:38 ` Ben Greear [this message]
[not found] ` <SN1PR08MB13736CC61B1D00ED2968CF5CB0FD0@SN1PR08MB1373.namprd08.prod.outlook.com>
2017-05-27 21:49 ` Ben Greear
2017-05-30 13:23 ` Matthias May
2017-05-31 13:05 ` Kalle Valo
2017-05-31 12:53 ` Kalle Valo
2017-05-31 12:52 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50e245a7-60ad-39f1-920e-e8edf5d9a5ab@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=norikd@ethertronics.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox