linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Saqeb Akhter <saqeb.akhter@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: carl9170: wnda3100 only 54MB/s
Date: Sat, 2 Oct 2010 04:52:22 +0200	[thread overview]
Message-ID: <201010020452.24306.chunkeey@googlemail.com> (raw)
In-Reply-To: <AANLkTinrbFLFN7PsVYpxGrnp0==FYVHGdbOBAXsKGWsv@mail.gmail.com>

On Saturday 02 October 2010 04:32:04 Saqeb Akhter wrote:
> ------------------------------------------------------------
> Client connecting to 192.168.10.52, TCP port 5001
> TCP window size: 16.0 KByte (default)
> ------------------------------------------------------------
> [  3] local 192.168.10.60 port 50647 connected with 192.168.10.52 port 5001
> [ ID] Interval       Transfer     Bandwidth
> [  3]  0.0-10.0 sec  98.6 MBytes  82.6 Mbits/sec
>  
> Seems to be doing a lot better now thanks :)
Hm, I'm not too optimistic. After all, it took a long time to get to this
point and even now the driver isn't "stable" yet (hence the EXPERIMENTAL
flag).

> I was not aware the WMM extensions were needed to get HT working.
;)

I think 802.11n says somewhere, something like:
"An HT STA is also a QoS STA"

And QoS is enabled/setup by WMM.
> I ended up upgrading my distro to 10.10 RC, and compiling the
> compat-wireless u posted, and enable WMM extensions on my router.
> Working considerably better :)

One more thing: I've updated the firmware to 1.8.8.3
http://wireless.kernel.org/en/users/Drivers/carl9170#Firmware_binary
(In case you are still using the original 1.8.8.1)

Best Regards,
	Christian

  reply	other threads:[~2010-10-02  2:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimN3X_e4fZhUSoTs-GmQ9kmaJUrgnxAu8=W2dT_@mail.gmail.com>
2010-10-01 14:22 ` carl9170: wnda3100 only 54MB/s Saqeb Akhter
2010-10-01 14:36   ` Christian Lamparter
     [not found]     ` <AANLkTimZYgDLLag+uGgdojrckZ5tgySC+UeyHCfee74J@mail.gmail.com>
2010-10-01 22:34       ` Saqeb Akhter
2010-10-01 22:52       ` Christian Lamparter
2010-10-01 23:56         ` Saqeb Akhter
2010-10-02  0:26           ` Christian Lamparter
2010-10-02  2:32             ` Saqeb Akhter
2010-10-02  2:52               ` Christian Lamparter [this message]
2010-10-02  2:56                 ` Saqeb Akhter
2010-10-02  3:19                   ` Christian Lamparter
2010-10-02  3:28                     ` Saqeb Akhter
2010-10-02  6:18                       ` Saqeb Akhter
2010-10-02 11:32                         ` Christian Lamparter
2010-10-02 16:40                           ` Saqeb Akhter
2010-11-29 17:14                           ` [RFC] mac80211: filter multicast rx (was: Re: carl9170: wnda3100 only 54MB/s) Christian Lamparter
2010-11-29 18:37                             ` [PATCH for-2.6.37?] mac80211: ignore non-bcast mcast managment frames Christian Lamparter
2010-11-29 18:45                               ` Johannes Berg
2010-11-29 19:53                                 ` [PATCH for-2.6.37 v2] mac80211: ignore non-bcast mcast deauth/disassoc franes Christian Lamparter
2010-12-04 21:38                                   ` Jouni Malinen
2010-10-04 17:58                     ` carl9170: wnda3100 only 54MB/s Dan Williams

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=201010020452.24306.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=saqeb.akhter@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).