On 2014-05-05 09:33, Johannes Berg wrote: > On Sat, 2014-05-03 at 22:55 +0200, Felix Fietkau wrote: >> At the moment, the ath9k/ath10k DFS module only supports detecting ETSI >> radar patterns. > > It seems this should also be advertised to the userspace. Right. >> Add a bitmap in the interface combinations, indicating which DFS regions >> are supported by the detector. > > Does that make sense? It seems unlikely to me that it would be interface > combination specific? Having it there made about as much sense to me as having the supportede channel width there :) Got any better suggestions? > I think it's already questionable to put this in after -rc4, in > particular with the userspace advertising part. Can we do anything > else? I mostly pushed it for 3.15, because right now you can already enable DFS and it will bring it up on a FCC regdomain and it will appear to be working (but probably just not recognize any radars). However, now that I look at the description of the options that you have to enable, it should be clear enough that this is not guaranteed to be functional yet, so I guess it can wait for 3.16. - Felix -- 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
