From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Arik Nemtsov <arik@wizery.com>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
Arik Nemtsov <arikx.nemtsov@intel.com>
Subject: Re: [PATCH 2/7] cfg80211: introduce regulatory flags controlling bw
Date: Tue, 10 Jun 2014 14:28:08 -0700 [thread overview]
Message-ID: <CAB=NE6Vs5y0DANeRbhU7J1z45uxENhcKDG+6b84XPxOh_f_KPw@mail.gmail.com> (raw)
In-Reply-To: <CA+XVXfcvXEi0o-UGNu1T95+rEfpQoVZPf9oVGL3AiqgGiu-LEw@mail.gmail.com>
On Tue, May 20, 2014 at 5:31 AM, Arik Nemtsov <arik@wizery.com> wrote:
> On Tue, May 20, 2014 at 12:54 PM, Luis R. Rodriguez
> <mcgrof@do-not-panic.com> wrote:
>> On Tue, May 20, 2014 at 2:25 AM, Arik Nemtsov <arik@wizery.com> wrote:
>>>
>>> Why won't old regdb rules work? The NL80211_RRF_NO_160MHZ for instance
>>> is not used anywhere in old or new regdbs.
>>> So all the new code in reg_get_max_bandwidth is ignored in current or
>>> older crda/regdb flows.
>>>
>>> What am I missing?
>>
>> It will also be ignored on newer kernels using old wireless-regdb.
>
> Is that a problem?
I would have not brought it up otherwise.
> Note that the new flags don't permit more things, but only narrow down
> the range. So if VHT80 was blocked due to the range, it will still be
> blocked.
> Don't really see a reason to use them in newer regdbs either. Like you
> said - range only is more scalable.
You can keep all those bells and whistles provided you respect old
userspace and old behavior first.
> These flags are very useful for translating the Intel FW regulatory
> format to reg.c format. We don't have ranges there, only flags per
> channel. This allows for seamless interop, with per-channel rules.
I get it, its all fine but just address ensuring that old behavior is
respected first, then you can add whatever on top of it.
Luis
next prev parent reply other threads:[~2014-06-10 21:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 8:50 [PATCH 0/7] regulatory enhancements Emmanuel Grumbach
2014-05-11 8:50 ` [PATCH 1/7] cfg80211: don't set reg timeout for user-handled hint Emmanuel Grumbach
2014-05-12 6:47 ` Kalle Valo
2014-05-12 6:49 ` Grumbach, Emmanuel
2014-05-12 7:48 ` Johannes Berg
2014-05-20 8:09 ` Luis R. Rodriguez
2014-05-20 13:21 ` Johannes Berg
2014-05-11 8:50 ` [PATCH 2/7] cfg80211: introduce regulatory flags controlling bw Emmanuel Grumbach
2014-05-20 8:26 ` Luis R. Rodriguez
2014-05-20 8:33 ` Arik Nemtsov
2014-05-20 8:51 ` Luis R. Rodriguez
2014-05-20 9:25 ` Arik Nemtsov
2014-05-20 9:54 ` Luis R. Rodriguez
2014-05-20 12:31 ` Arik Nemtsov
2014-06-10 21:28 ` Luis R. Rodriguez [this message]
2014-06-11 5:24 ` Arik Nemtsov
2014-06-11 6:21 ` Janusz Dziedzic
2014-06-11 6:38 ` Arik Nemtsov
2014-06-18 21:50 ` Luis R. Rodriguez
2014-05-11 8:50 ` [PATCH 3/7] cfg80211: allow drivers to provide regulatory settings Emmanuel Grumbach
2014-05-20 8:44 ` Luis R. Rodriguez
2014-05-20 9:12 ` Arik Nemtsov
2014-05-20 9:53 ` Luis R. Rodriguez
2014-05-20 12:00 ` Arik Nemtsov
2014-06-10 21:43 ` Luis R. Rodriguez
2014-06-11 5:51 ` Arik Nemtsov
2014-05-11 8:50 ` [PATCH 4/7] cfg80211: treat the special "unknown" alpha2 as valid Emmanuel Grumbach
2014-05-11 8:50 ` [PATCH 5/7] cfg80211: accept world/same regdom from driver/user hints Emmanuel Grumbach
2014-05-11 8:50 ` [PATCH 6/7] cfg80211: leave invalid channels on regdomain change Emmanuel Grumbach
2014-05-11 8:50 ` [PATCH 7/7] regulatory: add NULL to alpha2 Emmanuel Grumbach
2014-05-20 8:48 ` [PATCH 0/7] regulatory enhancements Luis R. Rodriguez
2014-06-10 21:44 ` Luis R. Rodriguez
2014-06-11 5:20 ` Arik Nemtsov
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='CAB=NE6Vs5y0DANeRbhU7J1z45uxENhcKDG+6b84XPxOh_f_KPw@mail.gmail.com' \
--to=mcgrof@do-not-panic.com \
--cc=arik@wizery.com \
--cc=arikx.nemtsov@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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).