On Mon, Oct 06, 2014 at 04:52:14PM +0200, Johannes Berg wrote: >> I found what I believe is an edge case: What happens if the element suddenly >> goes away from one beacon to another? Shouldn't there be a reset of the power >> level and then a new call to __ieee80211_recalc_txpower()? >> >> (If so, I believe this bug was already present in the code before my first >> patch, as I understand the existing logic.) > I'm not sure it's worth worrying about, but if you want to write a patch > I'd take it :) It actually happened to me in a real situation, which is why I noticed. It seems neither power element is typically sent at all if the value is 0. (Well, Aruba seems to do. I haven't found anyone else who does.) /* Steinar */ -- Homepage: http://www.sesse.net/ -- 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
