From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Enabling tx-power-per-vif in ath9k?
Date: Mon, 04 Mar 2013 14:44:28 -0800 [thread overview]
Message-ID: <513523CC.30506@candelatech.com> (raw)
In-Reply-To: <6E089F57-3AC7-4026-BA2E-19D7FA884479@net.t-labs.tu-berlin.de>
On 03/04/2013 02:42 PM, Thomas H?hn wrote:
> Hi Ben,
>>
>>> Any idea how feasible it is to do per-vif tx-power in ath9k? I think
>>> it would come down to putting the desired tx-power into each packet
>>> (as the VIF sends it towards the driver) and then changing the power
>>> as packets were transmitted in the NIC...
>> No need for 'changing the power as packets were transmitted', that would
>> be horribly messy and unreliable anyway. The hardware is capable of
>> proper per-packet TPC, configurable via the tx descriptor.
> I am currently shaping my transmit power control per link codebase for upstream. My current Minstrel changes are a
> prerequisite? so hopefully in the next weeks I can take the necessary clean up time.
> It enables power level settings per packet (in ath5k chips) and per mrr chain (in several ath9k chips).
>>
>>> The goal is to have multiple virtual APs, each with different tx-powers
>>> in order to roughly affect rx-signal quality for the stations that
>>> are scanning for APs?
> I think you can easily extend the TPC code to realize your idea of different tx power levels per VIF.
Awesome!
I'll look forward to your patches...
Ben
>
> Greetings Thomas
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2013-03-04 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 22:28 [ath9k-devel] Enabling tx-power-per-vif in ath9k? Ben Greear
2013-03-04 22:38 ` Felix Fietkau
2013-03-04 22:42 ` Thomas Hühn
2013-03-04 22:44 ` Ben Greear [this message]
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=513523CC.30506@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.