Hi, I've done some digging here. Yes, you're right, the big clobber isn't the right solution. What I've been told is: * with such a strong blocker and a weak signal (~ 5dB maximum above blocker) that the strong signal detection logic won't fire; * and if weak signal detection is disabled entirely as it's done at the moment, you will likely decode very little. So the solution of disabling sfcorr_low is right (as that's supposed to be for super-low signals and in the presence of such a blocker, it won't ever help) and leaving the first level low threshold detection is "right". I still can't help but wonder if there's a situation where the big "disable" is needed. Eg, in the presence of a very strong signal (ie, where strong signal detection will fire) but a weak blocker; you may wish to disable both so you don't end up with high levels of spurious weak signal detections and possibly OFDM restarts (ie, the hardware would then detect an increase in power during a weak OFDM frame decode -> OFDM restart.) So how about we treat this as an excuse to turn OFDM weak signal detection into three levels - entirely on, disable low weak detect, disable medium weak detect - and see if this is enough. I'd like to not break things for existing users where the "big thunk" is good enough. What do you think? Adrian -- 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
