On Tue, Jul 28, 2015 at 1:50 AM, Adrian Chadd <adrian@xxxxxxxxxxx> wrote: > is it never getting any readings before your patch? NF Readings all > look empty... Yes, looks like it. Unfortunately I haven't saved a complete kernel log (with ath9k debug level = 0x00004449) but only a few parts. Here are the interesting bits: <7>[ 449.746679] ath: phy1: NF calibrated [ctl] [chain 0] is -106 <7>[ 449.746697] ath: phy1: NF[0] (-106) > MAX (-110), correcting to MAX <7>[ 449.746714] ath: phy1: NF calibrated [ctl] [chain 1] is -90 <7>[ 449.746731] ath: phy1: NF[1] (-90) > MAX (-110), correcting to MAX <7>[ 449.746748] ath: phy1: NF calibrated [ext] [chain 0] is -103 <7>[ 449.746765] ath: phy1: NF[3] (-103) > MAX (-110), correcting to MAX <7>[ 449.746781] ath: phy1: NF calibrated [ext] [chain 1] is -86 <7>[ 449.746798] ath: phy1: NF[4] (-86) > MAX (-110), correcting to MAX <7>[ 449.746878] ath: phy1: Calibration @37407 finished: long ani, caldone: true I'd assume (because I don't know the ath9k code) that ath9k simply ignores NF readings that are "out of range" (as suggested by those messages). Regards, Martin -- 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
