From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Question on setting tx-power in ath10k.
Date: Wed, 25 Feb 2015 13:15:53 -0800 [thread overview]
Message-ID: <54EE3B89.6070803@candelatech.com> (raw)
In-Reply-To: <CAJ-VmoncKPbb+D0Z0N9ntov71B-UX8AT2pOyvCgcH1tYAsu+kA@mail.gmail.com>
On 02/25/2015 11:55 AM, Adrian Chadd wrote:
> Yeah I remember this stuff. ath9k did the same thing too; it subtracts
> TX power based on 2-chain and 3-chain; assuming that the max transmit
> power in the EEPROM is actually the 3-chain value so it can get the
> per-chain transmit power.
>
> Thing is, whenever I actually looked at the output on a spectrum
> analyser, the target power differed from what the card was rated at by
> exactly 3 and 5 dBm respectively. Grr.
>
> In FreeBSD I look at the number of configured chains for that TX
> attempt and set the TX power cap appropriately per-packet. Grr.
We have a spectrum analyzer now, but I'm not sure if I can even force
the NIC to run at a specific HT or VHT rate, so not so sure how to
test the changes properly.
Either way, even if I adjust this as I am trying to do now
(on a per-rate basis based on number of chains that rate uses)
the min/max power restraints stay in place, so it should still
be fine as far as regulations are concerned.
Thanks for the info.
Ben
>
>
> -adrian
>
> On 25 February 2015 at 10:24, Ben Greear <greearb@candelatech.com> wrote:
>> I have added some debugging in my CT firmware based on 10.1.467, and I have noticed
>> that anything below 5db is treated as zero by the firmware. This is due primarily to
>> subtracting a fixed amount based on the NIC's configured chainmask.
>>
>> I am guessing this is not entirely correct, since at /b rates, for instance, we
>> will be transmitting on only a single chain, so it does not matter how many
>> chains the hardware has?
>>
>> Anyone have any insight on how this stuff is *supposed* to work?
>>
>> If you have access to firmware source, plz contact me off the mailing list
>> and I can provide more details about the code that looks broken.
>>
>> Thanks,
>> Ben
>>
>> --
>> 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
>
--
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:[~2015-02-25 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 18:24 Question on setting tx-power in ath10k Ben Greear
2015-02-25 19:55 ` Adrian Chadd
2015-02-25 21:15 ` Ben Greear [this message]
2015-02-25 23:02 ` Ben Greear
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=54EE3B89.6070803@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
/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