From: Karl Hiramoto <karl@hiramoto.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [ath9k-devel] New kernel recommendations for ath9k
Date: Thu, 07 May 2009 12:02:50 +0200 [thread overview]
Message-ID: <4A02B1CA.3060708@hiramoto.org> (raw)
In-Reply-To: <43e72e890905070104u59eebcceu18718a733e388cc9@mail.gmail.com>
Luis R. Rodriguez wrote:
> For those not subscribed to the ath9k wiki on wireless.kernel.org [1]
> (which we recommend you do if you're a user) here's a quick note to
> let you know our latest kernel recommendations for using ath9k:
>
> * >= 2.6.27.22
> * >= 2.6.28.10
> * 2.6.29
>
> If you want 802.11n support or AP support you'll want at least 2.6.29.
> If you happen to have one of our new 1x1 AR9285 devices (all AR9285
> devices are 1x1) then you'll need at least 2.6.29. If you want to
> start using ath9k on APs with AHB you will need at least 2.6.30 (still
> in RC series).
>
> As usual if you happen to be stuck on older kernels for one reason or
> another you can always use compat-wireless [2] and if that happens to
> be a little too bleeding edge we have now compat-wireless releases for
> stable kernel releases, starting as of the 2.6.30-rc series [3].
>
> Luis
>
> [1] http://wireless.kernel.org/en/users/Drivers/ath9k
> [2] http://wireless.kernel.org/en/users/Download
> [3] http://wireless.kernel.org/en/users/Download/stable
>
Thanks for the update. If i want to use multiple AP's with Ath9k it it
still best to use wireless-testing? Is multiple AP support in 2.6.30-rc
series net-next or wireless-next?
Thanks.
--
Karl
next prev parent reply other threads:[~2009-05-07 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 8:04 New kernel recommendations for ath9k Luis R. Rodriguez
2009-05-07 10:02 ` Karl Hiramoto [this message]
2009-05-07 17:20 ` [ath9k-devel] " Luis R. Rodriguez
2009-05-09 5:50 ` Jason Daly
2009-05-08 9:02 ` Johannes Berg
2009-05-08 17:15 ` Luis R. Rodriguez
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=4A02B1CA.3060708@hiramoto.org \
--to=karl@hiramoto.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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).