On Thu, May 6, 2010 at 6:35 PM, Peter Stuge <[email protected]> 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. The frustrating part is it doesn't really seem to be stabilizing. For example the latest "stable" OpenWRT branch (backfire) is currently based on compat-wireless from 2010-04-28 and a recent git snapshot of hostapd (and I guess there is good reason). That's just not workable from a production point of view. So question is how do we get it to production quality? I think we need more focus on stable branches that are maintained and stress/interoperability tested, but I'm far from the expert here. What is the official plan? /Björn _______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
