From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] regulatory: don't rule out some valid rules
Date: Fri, 25 Apr 2014 17:24:51 +0200 [thread overview]
Message-ID: <1398439491.4152.13.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1397394958-6827-1-git-send-email-eliad@wizery.com> (sfid-20140413_151604_220848_6C7D5666)
On Sun, 2014-04-13 at 16:15 +0300, Eliad Peller wrote:
> 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.
For better or worse, this is how the rules verification was defined. I
don't like this definition either and think the whole "max bandwidth"
thing was done badly in the original implementation, but this is
userspace API.
To bust this limit would mean to change the rule interpretation quite
significantly, I don't think we can do that without more analysis on why
it's safe or won't matter for the regdb.
However, we have the NL80211_RRF_AUTO_BW flag now, which presumably
could also be somehow set for the rule here to solve this issue?
johannes
prev parent reply other threads:[~2014-04-25 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 13:15 [PATCH] regulatory: don't rule out some valid rules Eliad Peller
2014-04-25 15:24 ` Johannes Berg [this message]
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=1398439491.4152.13.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eliad@wizery.com \
--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).