From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Date: Mon, 04 Mar 2013 14:44:28 -0800 Subject: [ath9k-devel] Enabling tx-power-per-vif in ath9k? In-Reply-To: <6E089F57-3AC7-4026-BA2E-19D7FA884479@net.t-labs.tu-berlin.de> References: <5135201D.6080905@candelatech.com> <51352254.9080802@openwrt.org> <6E089F57-3AC7-4026-BA2E-19D7FA884479@net.t-labs.tu-berlin.de> Message-ID: <513523CC.30506@candelatech.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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 Candela Technologies Inc http://www.candelatech.com