On 11/28/12 8:12 AM, "Simon Wunderlich" <simon.wunderlich@xxxxxxxxxxxxxxxxxxxx> wrote: >Hmm, that would be possible as well ... Using the scan function is very >convenient as I don't have to think about cycling, channel lists, etc. >But putting more control to userspace is also possible, if we can ask the >driver to just have a "quick spectral peek" on another channel. Well, you may not need to think about channel cycling etc. for scan operations, but you won't get much control over the timing or dwell duration for that matter. Remain-on-channel gives you that. >Anyway, you'd suggest to use the NL80211 remain on channel command for >that? Yes. >Or add a new "spectral scan" nl80211 command to do a spectral scan on this >(or multiple) channels, and use the various functions from >mac80211/offchannel.c? I would rather add a flag to the existing r-o-c command to indicate that spectral scan functionality is to be enabled (well, assuming Johannes is fine with this). >BTW, is there any limitation to remain on channel commands, like will they >work on AP ifaces, Ad-Hoc ifaces, MultiSSID in general, etc? I hope not. There may be some practical issues with not all drivers supporting this, but remain-on-channel is the mechanism we use for supporting concurrent operations (e.g., P2P negotiations or GAS/ANQP) and making this work in all combinations would be important regardless. - Jouni -- 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
