From: Kalle Valo <kvalo@adurom.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH v2] cfg80211: allow restricting supported dfs regions
Date: Tue, 06 May 2014 03:15:09 +0300 [thread overview]
Message-ID: <87iopj4vaq.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1399283320-66468-1-git-send-email-nbd@openwrt.org> (Felix Fietkau's message of "Mon, 5 May 2014 11:48:40 +0200")
Felix Fietkau <nbd@openwrt.org> writes:
> At the moment, the ath9k/ath10k DFS module only supports detecting ETSI
> radar patterns.
> Add a bitmap in the interface combinations, indicating which DFS regions
> are supported by the detector. If unset, support for all regions is
> assumed.
>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
[...]
> --- a/include/uapi/linux/nl80211.h
> +++ b/include/uapi/linux/nl80211.h
> @@ -3688,6 +3688,8 @@ enum nl80211_iface_limit_attrs {
> * different channels may be used within this group.
> * @NL80211_IFACE_COMB_RADAR_DETECT_WIDTHS: u32 attribute containing the bitmap
> * of supported channel widths for radar detection.
> + * @NL80211_IFACE_COMB_RADAR_DETECT_REGIONS: u32 attribute containing the bitmap
> + * of supported regulatory regions for radar detection.
> * @NUM_NL80211_IFACE_COMB: number of attributes
> * @MAX_NL80211_IFACE_COMB: highest attribute number
> *
> @@ -3721,6 +3723,7 @@ enum nl80211_if_combination_attrs {
> NL80211_IFACE_COMB_STA_AP_BI_MATCH,
> NL80211_IFACE_COMB_NUM_CHANNELS,
> NL80211_IFACE_COMB_RADAR_DETECT_WIDTHS,
> + NL80211_IFACE_COMB_RADAR_DETECT_REGIONS,
How is the bitmap mapped with regions? That's not clear for me. It would
be good to document that in the comment.
--
Kalle Valo
next prev parent reply other threads:[~2014-05-06 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 9:48 [PATCH v2] cfg80211: allow restricting supported dfs regions Felix Fietkau
2014-05-06 0:15 ` Kalle Valo [this message]
2014-05-13 13:51 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iopj4vaq.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).