On 01/29/2013 01:21 PM, Simon Wunderlich wrote:
> [...]
>
> 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. :)
>
An event whenever a channel state changes is perfect, ideally provided with the
time-stamp when this change happened.
With the centralized channel state handling proposed here, the required
modification to allow managed DFS operation can be minimized to a proprietary (or
even upstreamed but CONFIG_CFG80211_CERTIFICATION_ONUS guarded) function to modify
channel states.
Can't contribute much to code review, but full ACK for the updated concept.
> If you prefer, I can split off the channel state stuff from the radar detect
> patches.
>
> Cheers,
> Simon
>
--
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
