[ath9k-devel] ath9k/ath5k + 80211s crash

[austinxxh-ath9k at yahoo.com]

Not good, I definitely like to use 80211s with ath9k, though I'm not familiar enough to fix anything related to them yet. Say, I don't know what's the relationship between 80211s and ath9k/ath5k at this point. Trying 0602 release now and see if it improves anything. 

I was told b43 runs well with 80211s, hope ath5k/ath9k will do the same someday.

X Xiao

--- On Tue, 6/2/09, Luis R. Rodriguez <lrodriguez at atheros.com> wrote:

> From: Luis R. Rodriguez <lrodriguez at atheros.com>
> Subject: Re: [ath9k-devel] ath9k/ath5k + 80211s crash
> To: "Andrey Yurovsky" <andrey at cozybit.com>
> Cc: "austinxxh-ath9k at yahoo.com" <austinxxh-ath9k at yahoo.com>, "devel at lists.open80211s.org" <devel at lists.open80211s.org>, "ath9k-devel at lists.ath9k.org" <ath9k-devel at lists.ath9k.org>, "linux-wireless at vger.kernel.org" <linux-wireless at vger.kernel.org>
> Date: Tuesday, June 2, 2009, 5:30 PM
> On Tue, Jun 02, 2009 at 09:58:59AM
> -0700, Andrey Yurovsky wrote:
> > With wireless-testing from a couple of days ago, an
> X86 system, and this patch:
> > http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
> > ath9k can bring up a mesh point interface and doesn't
> crash for me,
> > but there are no mesh beacons, so mesh isn't
> working.  On ath5k, there
> > are also no beacons and mesh doesn't work, but there's
> no crash.
> 
> If no one is really interested in fixing we should just
> disable mesh
> for both ath5k and ath9k.
> 
>   Luis
>