Ben Greear wrote: > Then default to minstrel, but no need to make people re-compile their > kernel to try a different rate control. For some users/systems this is > effectively impossible, and for the rest, it is an extra bit of pain. > > The point of leaving ath9k rate control in is exactly to help make sure > minstrel has something to compare against. And if a user happens to know > they have a clean environment always and forever, then ath9k may be > the best solution for them. > > It is a trivial amount of change to your patch to enable this > behaviour. In fact, if you just remove the code I mentioned then > they will *automatically* get defaulted to minstrel regardless of > their kernel config. The only way to use ath9k rate control after > that is to set the module option in mac80211 (and enable ath9k rate > control for compilation). Yes, I think this can be done instead, since we have always had both ath9k RC and minstrel compiled in by default. I'll send a v2. Sujith -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html