From: Jon Loeliger <jdl@bigfootnetworks.com>
To: Christian Lamparter <chunkeey@web.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ar9170 vs otus advice?
Date: Wed, 03 Jun 2009 10:59:59 -0500 [thread overview]
Message-ID: <1244044799.1559.38.camel@bigfoot-m4a75t> (raw)
In-Reply-To: <200906030337.27448.chunkeey@web.de>
On Wed, 2009-06-03 at 03:37 +0200, Christian Lamparter wrote:
> >
> > So, I'm trying to understand the current state of the ar9170 and otus
> > drivers so that I may know where to direction some effort. I'd like to
> > get an WN111v2 running with 11n support, and am willing to start with
> > either the ar9170 or otus drivers as needed. But I've not been following
> > along in too much detail so far.
>
> well, otus is a dead end. However it does fully support all 11n features the
> device has to offer. But you'll need a special and very old wpa_supplicant.
> (see otus' driver page on wireless.kernel.org where to get it.)
OK, got it, thanks.
> ar9170 - on the other hand - is only capable of receiving 11n frames.
> ( that said, enabling it makes the device unstable and therefore one can
> only _sniff_ 11n frames coming from other stations for now. )
Ewww.... So, does the ar9170 fully handle b/g as a station at least?
> > Advice on where I should start, what's working, what's not working,
> > what needs help, etc?
> a lot! first and foremost needed is the _final_ 802.11n specification,
> which sadly will still take a while... (2010? I think at least...)
> it's a really mess now...
Heh. But I'm not going to be able to help that much... :-)
> As other devices/firmwares are usually designed
> after a different revision of the drafts which makes it complicated.
> This is no joke and the original otus incorporates "workarounds" for all
> 11n vendors (including Atheros itself) to get it going.
> ( else, the performance can be worse than 802.11b )
Is the in-tree Otus up-to-date with all of these workarounds?
> > And should I start with one of the linville Git trees? Or wireless-everything?
>
> linville's wireless-testing is where we put the most recent code.
Excellent.
> Regards,
> Chr
Thanks,
jdl
next prev parent reply other threads:[~2009-06-03 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 22:07 ar9170 vs otus advice? Jon Loeliger
2009-06-03 1:37 ` Christian Lamparter
2009-06-03 15:59 ` Jon Loeliger [this message]
2009-06-03 18:32 ` Christian Lamparter
2009-06-03 18:09 ` Jon Loeliger
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=1244044799.1559.38.camel@bigfoot-m4a75t \
--to=jdl@bigfootnetworks.com \
--cc=chunkeey@web.de \
--cc=linux-wireless@vger.kernel.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