All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] compat-wireless
Date: Mon, 12 Apr 2010 11:07:44 -0700	[thread overview]
Message-ID: <20100412180744.GC2920@tux> (raw)
In-Reply-To: <19390.40989.738364.466420@gargle.gargle.HOWL>

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

      reply	other threads:[~2010-04-12 18:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 13:08 [ath9k-devel] compat-wireless Oleh
2010-04-09  3:33 ` Sujith
2010-04-12 18:07   ` Luis R. Rodriguez [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=20100412180744.GC2920@tux \
    --to=lrodriguez@atheros.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.