From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR Chipset Differences
Date: Fri, 26 Feb 2010 09:23:58 -0800 [thread overview]
Message-ID: <20100226172358.GF3802@tux> (raw)
In-Reply-To: <51021A57-4161-4ECE-8958-9CF462EF6EBF@zinkconsulting.com>
On Fri, Feb 26, 2010 at 08:08:31AM -0800, Galen wrote:
> I'm trying to determine the differences in features of the various Atheros chipsets supported by ath9k. Please note, I have only chosen dual band parts with at least 2 spatial stream support, as the single band parts are generally subsets of the dual band parts and the <2 spatial stream parts are generally extremely value-oriented (or power oriented.)
>
> Gen 1 - AR5008:
> AR5416+AR5122 - 2x2 dual band, PCI
> AR5416+AR5133 - 3x3 dual band, PCI
> AR5418+AR5133 - 3x3 dual band, PCIe
>
> Gen 2 - AR9001:
> AR9160+AR9104 - 2x2 dual band, PCI
> AR9160+AR9106 - 3x3 dual band, PCI
>
> Gen 3 - AR9002:
> AR9220 - 2x2, dual band, PCI
> AR9280 - 2x2, dual band, PCIe
>
> Did I miss any 2x2 or better 802.11n radios?
Yeah our AR9287 is 2x2 single band IIRC.
There is also our USB 2x2 AR9170 but that uses
a Zydas MAC and Atheros Radio. But hey the firmware
is available as GPL and driver is upstream.
There is another USB 2x2 with Atheros MAC and Atheros
Radio but not yet sure of the chipset name and if it
ships. Think it might somewhere.
> Questions:
>
> 1) What differences exist between the AR5133 and AR9106?
Beats me.
> If the AR9106 offers 3x3 with superior performance to the AR5008, why
> didn't they ever offer any kind of PCIe option?
Not sure, but the answer to these sort of questions is usually demand.
> 2) What is the advantage of the AR9002 family over the AR9001
> family? Obviously, the AR9002 is a single chip solution, likely
> reducing cost, power and size.
>
> But is there any improvement to radio functionality or other features?
Having a single chip itself yields a lot more benefits than that.
Since things are closer together it also means less complexity on
overall programming. You can tell where things got easier by looking
at AR_SREV_9280_10_OR_LATER(ah) checks on the hardware code, I had
documented some of this on phy.c.
Apart from that you also get radio and baseband enhancements,
fixes, tunings, etc, the usual life of generation changes of
chipsets for 802.11. I can't get into specifics as that would
imply giving away the actual list of differences on each of
the blocks, but to be honest I only look at that stuff when
needed and that doesn't happen that often. I'm sure marketing
would have glanced over that and put together docs about this
with what is to be shared publicly.
If you have more questions you should work with our sales or
marketing teams.
> Note, I am interested in 802.11n features supported, quality of
> implementation, relative effective sensitivity, pretty much
> everything on the radio / DSP / layer 1 angle of things. I am
> curious as I want to be able to make the most appropriate
> hardware choices, and frankly, testing these chipsets to try
> and figure this out isn't the best way to do this based on
> my experiences thus far...
I recommend the single chip families, and specificaly AR9280
is a great candidate as its dual band and uses PCI-E. From a
software perspective Atheros dedicates more of its own resources
for testing our newer chipsets, the newer gernation 802.11n
chipsets. The AR9001 didn't get formal testing but the AR9002
did. Now its AR9002, in the near future it will be AR9003 and
so on.
And that's the way the cookie crumbles.
Luis
next prev parent reply other threads:[~2010-02-26 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 16:08 [ath9k-devel] AR Chipset Differences Galen
2010-02-26 17:23 ` Luis R. Rodriguez [this message]
2010-02-26 22:48 ` Galen
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=20100226172358.GF3802@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.