On Fri, 2010-09-24 at 21:59 -0400, Luis R. Rodriguez wrote: > Association is dealt with as an atomic offchannel operation, > we do this because we don't know we are associated until we > get the associatin response from the AP. When we do get the > associatin response though we were never clearing the offchannel > state. This has a few implications, we told drivers we were > still offchannel, and the first configured TX power for the > channel does not take into account any power constraints. > > For ath9k this meant ANI calibration would not start upon > association, and we'd have to wait until the first bgscan > to be triggered. There may be other issues this resolves > but I'm too lazy to colb the code to check. colb? But anyway, looks OK to me. Need to revisit some of the off-channel stuff eventually, but for now this is fine I think. 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
