On Mon, Oct 28, 2013 at 10:11 PM, Jeffrey Johnson <jjohnson@xxxxxxxxxxxxxxxx> wrote: > The issue that has been debated internally is whether or not userspace needs > to know the source of the interference. In other words, if we have an > enumerated set of interference sources, would userspace behave differently > based upon the source? This is ignoring my overall architectural considerations of this being cross RF domains and likely being a better idea to instead consider a frequency broker for this sort of information. The only reason I believe we can let that argument go here is that in this particular case the same antenna is being used and the information seems to be coming from the wireless firmware, as such it is pertinent to the struct wiphy, and hence seems proper placement for an nl80211 event. In so far as the source of information -- as I have said internally, although userspace may not use it today, it may tomorrow, and having that information can be useful. I consider a random source of associated "frequency advisory" simply pointless. At least with some sort of category of source, userspace, say hostapd or the supplicant, may decide to treat it in a very specific way today. Luis -- 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
