Hi Sujith!
> Yep, that is the problem. But that chunk of code (and the bug) has been
> there forever,
> so am not sure why it is creating a problem now.
Maybe because the scanning code was changed? But I have discovered this bug at the end of the last year before the scanning code was changed the last time.
> And it can be fixed by
> making use of the scan start/stop mac80211 callbacks.
I think a much cleaner way would be if the ath9k_hw_write_associd() honor the FIF_BCN_PRBRESP_PROMISC flag and determine with it if sc->curbssid should be set or ath_bcast_mac. So the the old sc->curbssid setting is saved. And then remove the following code...
if (*total_flags & FIF_BCN_PRBRESP_PROMISC) {
memcpy(sc->curbssid, ath_bcast_mac, ETH_ALEN);
sc->curaid = 0;
...so that ath9k_hw_write_associd() is called if the FIF_BCN_PRBRESP_PROMISC is cleared at the end of the scanning, too. So that it can set the BSSID in the hardware back to sc->curbssid.
Regards
Alina
--
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
