On Sat, Aug 29, 2009 at 8:47 AM, Nick Kossifidis wrote:
> 2009/8/29 Benoit PAPILLAULT :
>>
>> I have been working on XR (in madwifi) for some time with no result. I
>> would appreciate to be able to test it in ath5k.
>
> All XR related stuff is missing from both Legacy and Sam's HAL + it's
> nasty
Hi all,
While profiling ath5k_reset, I noticed that ath5k_hw_txpower() takes
around 200-300 us due to a lot of calls to ath5k_get_interpolated_value().
I'm not too familiar with the code, is there anything we could cache
here that we wouldn't have to recompute? 200-300s is only a small
part of re
2009/8/29 Benoit PAPILLAULT :
>
> I have been working on XR (in madwifi) for some time with no result. I
> would appreciate to be able to test it in ath5k.
All XR related stuff is missing from both Legacy and Sam's HAL + it's
nasty IMHO. We need to define new rates, send beacons on both 0.25 and
1
Hi All,
I am VERY interested in XR.
John
___
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick Kossifidis a écrit :
> Since we started the discussion about ath5k and proprietary
> features i started a new thread to continue.
>
> So this is what we have...
>
> a) X.R.: eXtended Range is a set of proprietary rates and some
> extra techniques
