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] Ath9k MIMO Performance versus Proprietary Drivers
Date: Wed, 24 Feb 2010 16:39:40 -0800	[thread overview]
Message-ID: <20100225003940.GK13779@tux> (raw)
In-Reply-To: <B705A7E9-3E24-4220-B158-FF6A425BF320@zinkconsulting.com>

On Wed, Feb 24, 2010 at 11:41:46AM -0800, Galen wrote:
> 
> On Feb 24, 2010, at 11:33 AM, Felix Fietkau wrote:
> 
> > On 2010-02-24 8:22 PM, Galen wrote:
> >> This is an addendum to my earlier reply.
> >> 
> >> On Feb 22, 2010, at 1:09 PM, Felix Fietkau wrote:
> >>>>> Except for STBC, ath9k seems to have pretty much the same hardware
> >>>>> features as Atheros' other drivers. There may be some workarounds for
> >>>>> various hw issues missing, I have not extensively reviewed that yet.
> >>>> I would be interested in knowing more about these. LDPC? Others?
> >>>> There appear good software implementations of LDPC out there:
> >>>> http://planete-bcast.inrialpes.fr/article.php3?id_article=7
> >>> I'm pretty sure the current hardware also doesn't do LDPC yet.
> >> 
> >> I have looked over data presented on the Atheros website and as best as I can tell, the AR5008 (and other newer chipsets, I assume) support:
> >> 
> >> - STBC (space-time block coding) for TX and RX
> >> - MRC (maximal ratio combining) via zero forcing algorithm 
> >> - TxBF (transmit beam forming) 
> >> 
> >> From what you're saying, my understanding is that MRC and and TxBF
> >> are both functioning with ath9k, with STBC being the primary
> >> remaining feature. Is this correct?
> > TxBF isn't supported by the currently available hardware, so ath9k
> > doesn't make use of it either. I don't know about MRC, but I don't see a
> > difference between ath9k and other Atheros drivers in that area.
> > So yes, of those options, only STBC is missing.
> 
> Atheros' data is not very clear in all cases. However, their statements
> lead one to believe that transmit beamforming is supported, as is MRC. 

MRC is supported on all 11n chipsets, but not for cck rates.
TX beamforming is only supported on the shiny new AR93xx
chipsets. TX beamforming seems to have been supported on
some old legacy chipset but there is no code to support it
and I wouldn't bother trying.

  Luis

  parent reply	other threads:[~2010-02-25  0:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-21 20:41 [ath9k-devel] Ath9k MIMO Performance versus Proprietary Drivers Galen
2010-02-22 14:29 ` Felix Fietkau
2010-02-22 19:43   ` Galen
2010-02-22 21:09     ` Felix Fietkau
2010-02-24 18:12       ` Galen
2010-02-24 19:22       ` Galen
2010-02-24 19:33         ` Felix Fietkau
2010-02-24 19:41           ` Galen
2010-02-25  0:33             ` rootkit85 at yahoo.it
2010-02-26  4:03               ` Galen
2010-02-26 16:42                 ` Luis R. Rodriguez
2010-02-26 23:11                   ` Galen
2010-02-26 23:21                     ` Luis R. Rodriguez
2010-02-25  0:39             ` Luis R. Rodriguez [this message]
2010-02-26  5:37               ` Galen
2010-02-26 16:45                 ` Luis R. Rodriguez
2010-02-26 17:13                   ` Daniel Halperin
2010-02-26 17:31                     ` Luis R. Rodriguez
2010-02-26 21:00                     ` Galen
2010-02-26 20:45                   ` Galen
2010-02-26 21:46                     ` Luis R. Rodriguez
2010-02-26 22:46                       ` Galen
2010-03-16 12:25 ` Björn Smedman

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=20100225003940.GK13779@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.