From mboxrd@z Thu Jan  1 00:00:00 1970
From: Luis R. Rodriguez <lrodriguez@atheros.com>
Date: Mon, 12 Apr 2010 11:07:44 -0700
Subject: [ath9k-devel] compat-wireless
In-Reply-To: <19390.40989.738364.466420@gargle.gargle.HOWL>
References: <op.vauj87suhn1eay@zeus>
	<19390.40989.738364.466420@gargle.gargle.HOWL>
Message-ID: <20100412180744.GC2920@tux>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

On Thu, Apr 08, 2010 at 08:33:49PM -0700, Sujith wrote:
> Oleh wrote:
> >   Greetings,
> > 
> > 
> >   I cant change bit rate of wireless connection for TP-LINK TL-WN722N
> >   (ath9k_htc driver from compat-wireless-2010-03-28). Here is how it
> >   happens, it is always 1 Mb/s but real speed may be higher:
> > 
> >   iwconfig wlan1
> >   wlan1     IEEE 802.11bgn  ESSID:"TP-LINK"
> >              Mode:Managed  Frequency:2.437 GHz  Access Point:
> >   00:1D:0F:D6:73:98
> >              Bit Rate=1 Mb/s   Tx-Power=20 dBm
> >              Retry  long limit:7   RTS thr:off   Fragment thr:off
> >              Encryption key:off
> >              Power Management:off
> >              Link Quality=38/70  Signal level=-72 dBm
> >              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
> >              Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> Rate control for ath9k_htc is handled by the firmware.
> So you can't set fixed rate using iwconfig.
> 
> The reported TX rate also stays at 1, because the firmware
> does not report the actual transmission rate.
> You can check the actual throughput using iperf.

Hopefully we'll fix this with an eventual release of firmware. But for now
a flag seems appropriate for hardware that cannot report proper rate back.

 Luis