On Mon, 2012-03-19 at 15:38 +0530, Sujith Manoharan wrote: > Johannes Berg wrote: > > > As far as ath9k/ath9k_htc is concerned, I think we have to reset/reconfigure the HW > > > when a channel switch happens, since we reprogram various MAC/PHY registers based on > > > the HT bandwidth. Both ath9k and ath9k_htc update their rate control modules > > > correctly - ath9k via the rate_update() callback and ath9k_htc using BSS_CHANGED_HT > > > in bss_info_changed(). > > > > I'm not sure ath9k_htc is behaving correctly. Ok I should say that > > differently -- it's probably behaving "correctly" wrt. whatever mac80211 > > did before, but we're changing the way mac80211 behaves and I believe > > that to be (more) correct, see my other email. > > Well, we do a bunch of HW configuration based on the channel bandwidth, like > TX power, program MAC/PHY registers, various calibration routines at the baseband level. > So when the bandwidth changes, doing a full HW reset is required, I think. I guess I'm arguing that the channel bandwidth never changed, only the inputs to rate control changed in a way that means you'll now transmit only 20 MHz frames on that 40 MHz channel. After all, at least in AP mode you have to deal with that anyway if a station joins that can't receive 40 MHz for some reason, unless you want to penalise all others as well? johannes -- 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
