On Wed, 2011-08-31 at 15:49 +0200, Alexander Simon wrote: > > Use for what? That's confusing. You're asking if it can be used for > > beaconing, as the old function name *clearly* said. Now you're making it > > confusing. > I'm not only asking for beaconing. In 4/4, i am using this function to see if > regdom allows me to use HT40 on the extension channel (beacons and data > traffic). Hence can_use_ext_chan. > > Even cfg80211_set_freq in net/wireless/chan.c uses this to see if we can > communicate (see printk) on that channel. > > So my suggestion would be to use that name. But I'd also use the old if > preferred. But the type of usage should be made clear. You're going to use it for uncontrolled transmissions, so regulatory rules that apply are different than "can I use this channel to connect to an AP" for example. The "can beacon" made that obvious. Obviously, if I can beacon, I can also TX data, but vice versa isn't necessarily true depending on regulatory rules, since data TX can happen controlled by the AP (e.g. DFS channels). johannes -- 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
