From: Eliad Peller <eliad@wizery.com>
To: Johannes Berg <johannes@sipsolutions.net>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: [PATCH] regulatory: don't rule out some valid rules
Date: Sun, 13 Apr 2014 16:15:58 +0300 [thread overview]
Message-ID: <1397394958-6827-1-git-send-email-eliad@wizery.com> (raw)
commit 6d87df6 ("regdb: allow 40 MHz on world roaming
channels 12/13") in wireless-regdb did the following
change:
- # Channel 12 - 13. No HT40 channel fits here
- (2457 - 2482 @ 20), (3, 20), PASSIVE-SCAN, NO-IBSS
+ # Channel 12 - 13.
+ (2457 - 2482 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS
in order to allow HT40+ on lower channels (such as 9).
However, the current regulatory rules verification forbids
such rules, as 2482 - 2457 < 40.
Remove this requirement from the rules verification function.
Signed-off-by: Eliad Peller <eliad@wizery.com>
---
net/wireless/reg.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/net/wireless/reg.c b/net/wireless/reg.c
index 6c4b507..c8a5c34 100644
--- a/net/wireless/reg.c
+++ b/net/wireless/reg.c
@@ -610,8 +610,7 @@ static bool is_valid_reg_rule(const struct ieee80211_reg_rule *rule)
freq_diff = freq_range->end_freq_khz - freq_range->start_freq_khz;
- if (freq_range->end_freq_khz <= freq_range->start_freq_khz ||
- freq_range->max_bandwidth_khz > freq_diff)
+ if (freq_range->end_freq_khz <= freq_range->start_freq_khz)
return false;
return true;
--
1.8.5.2.229.g4448466.dirty
next reply other threads:[~2014-04-13 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 13:15 Eliad Peller [this message]
2014-04-25 15:24 ` [PATCH] regulatory: don't rule out some valid rules 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=1397394958-6827-1-git-send-email-eliad@wizery.com \
--to=eliad@wizery.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
/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).