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] Current state of ath9k in linux release and compat-wireless
Date: Mon, 10 May 2010 11:02:47 -0700	[thread overview]
Message-ID: <20100510180246.GA2177@tux> (raw)
In-Reply-To: <m2j133e8d7e1005071659vf26c70e8k430c51c618e94a9c@mail.gmail.com>

On Fri, May 07, 2010 at 04:59:02PM -0700, Bj?rn Smedman wrote:
> On Thu, May 6, 2010 at 6:35 PM, Peter Stuge <peter@stuge.se> wrote:
> > I don't consider ath9k on AR5008 to be at production level for STA
> > with wireless-testing as of a week ago, but AP performance may be
> > different.
> 
> I've been running ath9k in a production network (AP mode) for the last
> year or so, but unfortunately have to concur: ath9k is not production
> ready.

I think it is a good time to highlight once again that Atheros has supported
anything >= AR9280 with actual staff and good commitment. Our resources are
limited though so we can only focus on a set of chipsets. The AR5008 and AR9001
family are those unfortunate families which did not get as much attention and
love.

So if you want production material support you should use >= AR9280 or
be willing to grind in as the older families *are* supported but with
limited attention and resources, more with the help of the community.

I hope this helps making choices on chipsets.

  Luis

  parent reply	other threads:[~2010-05-10 18:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  0:53 [ath9k-devel] Current state of ath9k in linux release and compat-wireless Alan
2010-05-06  5:29 ` Daniel Yingqiang Ma
2010-05-06 16:35 ` Peter Stuge
2010-05-07 23:59   ` Björn Smedman
2010-05-08  5:33     ` Felix Fietkau
2010-05-09 11:28       ` Björn Smedman
2010-05-09 16:39         ` Pavel Roskin
2010-05-10 18:02     ` Luis R. Rodriguez [this message]
2010-05-11  8:02       ` Daniel Yingqiang Ma
2010-05-11 16:25         ` Luis R. Rodriguez
2010-05-12  3:28           ` Xianghua Xiao

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=20100510180246.GA2177@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.