On 2011-02-04 9:19 PM, Mark Mentovai wrote: > That would work for ath9k. I still think it’d be prudent to examine a > handful of rates. I also seem to remember that some other values that > were being used within ath9k_init_txpower_limits were invalid. I think > ntxchains was invalid during that early phase of initialization, for > example. That might not have any ultimate effect on the result, but > it’s not right to hit that ath_debug claiming "Invalid chainmask > configuration" once for every supported channel every time the driver > initializes. I'll take a look at fixing all of that stuff soon, then we can go back to treating the driver's tx power values as a limit afterwards. - Felix -- 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
