Any ideas on how to fix rssi?

Ben Greear greearb at candelatech.com
Thu May 15 07:17:09 PDT 2014


On 05/14/2014 10:07 PM, Janusz Dziedzic wrote:
> On 15 May 2014 02:07, Ben Greear <greearb at candelatech.com> wrote:
>> On 05/14/2014 04:22 PM, Ben Greear wrote:
>>> I'm seeing incorrect signal strength when running a rate-vs-range
>>> test through an attenuator.  Maybe the FIXME below is the reason?
>>>
>>> Any suggestions on what needs doing here?
>>
>> Actually, it wasn't (just?) this...the patch below makes the numbers look
>> good, but obviously there could be a better fix:
>>
>> diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c b/drivers/net/wireless/ath/ath10k/htt_rx.c
>> index ccbc363..f26f296 100644
>> --- a/drivers/net/wireless/ath/ath10k/htt_rx.c
>> +++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
>> @@ -1218,8 +1218,13 @@ static void ath10k_htt_rx_handler(struct ath10k_htt *htt,
>>         mpdu_ranges = htt_rx_ind_get_mpdu_ranges(rx);
>>
>>         /* Fill this once, while this is per-ppdu */
>> -       rx_status->signal  = ATH10K_DEFAULT_NOISE_FLOOR;
>> -       rx_status->signal += rx->ppdu.combined_rssi;
> 
> Seems you have old code without ath10k: fix rssi and rate reporting patch.

Yes, thanks for the suggestion.  I had patches on each side of that one,
but somehow I had missed it.  Will test with it today.

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com




More information about the ath10k mailing list