Adrian Chadd wrote: > It's easy enough to diagnose - just enable NF cal logging. Look at > what's being read back from the initial NF cal and what's being > written into the time-series average. I discussed this with Felix a while ago, a small log is here: http://pastebin.ca/2312828 (Note the jump in signal level). > It may be that something dumb is happening, like there's no > per-channel history, or the history from the wrong channel is being > used on a new channel. I am not sure about the dumb part, but ath9k doesn't have per-channel history or calibration data. :) Sujith -- 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
