Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Anyone doing WiFi throughput tests?
Date: Tue, 29 May 2012 10:14:31 +0200	[thread overview]
Message-ID: <4FC48567.2030701@neratec.com> (raw)
In-Reply-To: <201205261958.22934.chunkeey@googlemail.com>

On 05/26/2012 07:58 PM, Christian Lamparter wrote:
> 
> Well, Atheros made some nice presentations about that:
> <http://wenku.baidu.com/view/ac0523f57c1cfad6195fa7f4.html>
> take a look at slide 12. It has 11n technology (2x2 vs
> 3x3 ZF vs ML vs CC vs LDPC vs (TxBF) vs range vs tcp
> throughput all on one diagramm)
> 
Well, that's a really helpful document to have as reference for our
throughput testing. Sadly, the second source Google knows
(http://wenku.it168.com/d_000141980.shtml) also requires to create an
account for downloading the PDF, which I fail after I missed to learn
Chinese in time ;(

QCA folks, any chance to post an official download link to these slides?


Cheers, Zefir

  reply	other threads:[~2012-05-29  8:14 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-26  3:17 [ath9k-devel] Anyone doing WiFi throughput tests? Ben Greear
2012-05-26  3:24 ` Sujith Manoharan
2012-05-26  5:48   ` Joe Semler
2012-05-26  7:43     ` Sujith Manoharan
2012-05-26  7:55       ` Josef Semler
2012-05-26 11:28         ` Sujith Manoharan
2012-05-26 12:35         ` Felix Fietkau
2012-05-26 17:15           ` Joe Semler
2012-05-26 17:50             ` Adrian Chadd
2012-05-29 10:24               ` Josef Semler
2012-05-29 10:58                 ` Felix Fietkau
2012-05-26 18:27             ` Felix Fietkau
2012-05-26 15:37   ` Ben Greear
2012-05-26 16:24     ` Sujith Manoharan
2012-05-26 16:39       ` Sujith Manoharan
2012-05-27 15:08         ` Ben Greear
2012-05-27 16:48           ` Peter Stuge
2012-05-27 17:38             ` Adrian Chadd
2012-05-27 17:40           ` Adrian Chadd
2012-05-27 18:14             ` Felix Fietkau
2012-05-27 23:15               ` Adrian Chadd
2012-05-27 23:29                 ` Felix Fietkau
2012-05-28  3:55             ` Ben Greear
2012-05-28  6:50               ` Adrian Chadd
2012-05-28  7:15                 ` Sujith Manoharan
2012-05-28 20:07                   ` Adrian Chadd
2012-05-31 19:24                     ` Adrian Chadd
2012-05-31 22:31                       ` Ben Greear
2012-05-29 18:23           ` Ben Greear
2012-05-29 19:07             ` Christian Lamparter
2012-05-29 19:19               ` Ben Greear
2012-05-30  0:06               ` Ben Greear
2012-05-30  3:22                 ` Dave Taht
2012-05-30  3:47                   ` Ben Greear
2012-05-31  2:29             ` Sujith Manoharan
2012-05-26 17:58     ` Christian Lamparter
2012-05-29  8:14       ` Zefir Kurtisi [this message]
2012-05-29 10:09         ` Peter Stuge
2012-05-26 17:56 ` Adrian Chadd
2012-05-27  2:05   ` Sujith Manoharan
2012-05-27  2:09     ` Sujith Manoharan
2012-05-27  2:16       ` Ben Greear
2012-05-27  2:23         ` Sujith Manoharan
2012-05-27 11:30       ` Felix Fietkau
2012-05-27 12:32       ` Adrian Chadd
2012-05-27 12:31     ` Adrian Chadd
2012-06-15 21:08   ` Stephen Donecker
2012-06-16 21:03     ` Adrian Chadd
2012-06-20  2:20       ` Stephen Donecker

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=4FC48567.2030701@neratec.com \
    --to=zefir.kurtisi@neratec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox