-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Davide a écrit :
> I've more news on the subject as it may not me a driver or hardware problem.
>
> I found out that if I try to set manually frequency channel on ath5k driver
> it is successful only upto channel 11 while with the madwifi-nr-r3366+ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maxim Levitsky a écrit :
> Derek Smithies wrote:
>> Hi,
>> to verify that it is a rate control issue, there is one very simple and
>> very practical test.
>>
>> Take both ends of your link, and set them to fixed rate, and at the rate
>> you think it
Bob:
You are right, the bss_infor_changed is lost on the way.
Please review below patch:
From: Martin Xu <[EMAIL PROTECTED]>
Subject: disable beacon filter when station is not associated with any AP.
Ath5k driver has too many interrupts per second at idle
http://bugzilla.kernel.org/show_bug.cgi?i
On Fri, Nov 21, 2008 at 03:27:34PM -0500, John W. Linville wrote:
> > +static void ath5k_bss_info_changed(struct ieee80211_hw *hw,
> > + struct ieee80211_vif *vif,
> > + struct ieee80211_bss_conf *bss_conf,
> > + u32 chan
2008/11/21 Maxim Levitsky <[EMAIL PROTECTED]>:
> sorry for cross-posting, but this issue really spans both iwl3945 and ath5k.
I've no idea if this can be related, but recently there was some
report about ath5k && b43. Maybe it's some bug in ath5k?
https://lists.berlios.de/pipermail/bcm43xx-dev/20
