On Tue, 2013-01-29 at 13:21 +0100, Simon Wunderlich wrote:
> Right now, channels at least on my machine have the NO IBSS and PASSIVE SCAN
> flags set, which prevents reg_can_beacon from returning true, even if we do
> have radar support. This is due to my reg database setting these flags for
> country code 00, and this is still kept when changing the country code to
> something else (DE in my case). How should we proceed with this? Shouldn't
> these flags be removed when selecting a country code?
I don't think any country sets that, you may be running into that whole
"regdb intersect" thing ... FWIW the flags are set for 00 since for
world roaming we don't know if we're in a country that even allows
transmission on that AP.
> The channel states are now implemented in cfg80211. Shall we inform userspace
> about channel changes? If yes, how should we do that? We could add channel states
> to the channel list, and give "channel list changed" events to userspace as it
> happens now, or define a new kind of event ("channel-available-again-event").
> Suggestions welcome. :)
You already inform it of the changes by the radar event, but it would
probably also be good to export the state as part of the channel list
that you get with things like "iw list".
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
