From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Karl Hiramoto <karl@hiramoto.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Gabor Juhos <juhosg@openwrt.org>, Felix Fietkau <nbd@openwrt.org>
Subject: Re: [ath9k-devel] New kernel recommendations for ath9k
Date: Thu, 7 May 2009 10:20:48 -0700 [thread overview]
Message-ID: <43e72e890905071020v26857c52p3abea96be04ef1d9@mail.gmail.com> (raw)
In-Reply-To: <4A02B1CA.3060708@hiramoto.org>
On Thu, May 7, 2009 at 3:02 AM, Karl Hiramoto <karl@hiramoto.org> wrote:
> 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?
Yeah wireless-testing is best for that. I should also mention that if
you want to use AP mode you want to be at least on 2.6.29 (your own
kernel, not the compat-wireless one) if you care about Power Save
buffering on the AP as otherwise even if you use a compat-wireless
with code from > 2.6.29 those frames will be dropped. IIRC its due to
the way we use skb->cb for this and there not being a clean way to
backport this (so we just drop them).
Luis
next prev parent reply other threads:[~2009-05-07 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 8:04 Luis R. Rodriguez
2009-05-07 10:02 ` [ath9k-devel] " Karl Hiramoto
2009-05-07 17:20 ` Luis R. Rodriguez [this message]
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=43e72e890905071020v26857c52p3abea96be04ef1d9@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=juhosg@openwrt.org \
--cc=karl@hiramoto.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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
all inboxes | Powered by JetHome®