On Mon, 2012-05-28 at 13:18 +0200, Michal Kazior wrote:
> Helper function for finding out which channel is
> used by a given interface.
>
> Will be used for matching interface combinations.
>
> Change-Id: Ic9e5a68d66aaa26e73901648b04a6e9b465430d0
> Signed-off-by: Michal Kazior <michal.kazior@xxxxxxxxx>
> ---
> net/wireless/chan.c | 31 +++++++++++++++++++++++++++++++
> net/wireless/core.h | 4 ++++
> 2 files changed, 35 insertions(+), 0 deletions(-)
>
> diff --git a/net/wireless/chan.c b/net/wireless/chan.c
> index c1999e4..45b28ab 100644
> --- a/net/wireless/chan.c
> +++ b/net/wireless/chan.c
> @@ -92,3 +92,34 @@ int cfg80211_set_monitor_channel(struct cfg80211_registered_device *rdev,
>
> return rdev->ops->set_monitor_channel(&rdev->wiphy, chan, chantype);
> }
> +
> +struct ieee80211_channel *
> +cfg80211_get_used_channel(struct cfg80211_registered_device *rdev,
> + struct wireless_dev *wdev)
> +{
> + ASSERT_RDEV_LOCK(rdev);
> + ASSERT_WDEV_LOCK(wdev);
> +
> + switch (wdev->iftype) {
> + case NL80211_IFTYPE_ADHOC:
> + case NL80211_IFTYPE_STATION:
> + case NL80211_IFTYPE_P2P_CLIENT:
> + if (wdev->current_bss)
> + return wdev->current_bss->pub.channel;
I think the IBSS part isn't something we should really do. Maybe if we
track whether it's fixed-channel or not (to not break some use cases
like freifunk), but I don't think we should assume IBSS stays here.
In mac80211, IBSS causes it to assume "channel hopping" to handle this.
Maybe here we could return some "cookie" channel pointer to handle this.
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
