From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Seth Forshee <seth.forshee@canonical.com>, Wei Zhong <wzhong@google.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: wireless-regdb: update CA rules for 5600 - 5650 mHz
Date: Mon, 06 Jul 2015 16:40:56 +0200 [thread overview]
Message-ID: <559A9378.7000006@neratec.com> (raw)
In-Reply-To: <20150706132707.GA22962@ubuntu-hedt>
On 07/06/2015 03:27 PM, Seth Forshee wrote:
> On Fri, Jul 03, 2015 at 05:01:20PM +0200, Zefir Kurtisi wrote:
>> On 07/03/2015 04:20 PM, Wei Zhong wrote:
>> [...]
>> From your other post:
>>>> >
>>>> > - (5490 - 5730 @ 160), (24), DFS
>>>> > + (5490 - 5590 @ 80), (24), DFS
>>>>
>>>> I agree. 5590 is more strict than 5600.
>>>>
>>>>
>>>> On a second thought, 5590 implies channel 116 can't have 40MHz. I think that is
>>>> still allowed per regulation.
>>>>
>>>>
>>
>> No, channel 116 is not usable for HT40 if weather radar channels are disabled,
>> since it can only be combined with channel 120 and that one partially falls into
>> the restricted range.
>
> It's not necessary to restrict the band down to 5590 or break out the
> rule for channel 116 separately, the software is smart enough to work
> out what's allowed based on the original rule Wei supplied for 5490-5600
> MHz. In fact that rule exactly matches what we used to have in db.txt
> for the US prior to the TDWR restrictions being lifted.
>
Yes, the SW is smart and sane enough to extract the limitations even if they are
defined less restrictive than required. Which raises the general question of what
needs to be defined as rule and what can be relied on to be handled correctly by
the SW.
Example: why do we need to bother about the max-bw parameter for a rule at all? We
know there is no 160MHz channel within 5490 and 5600, as does the SW. If we wrote
(5490 - 5600 @ 160) instead of (5490 - 5600 @ 80), nothing would change.
To me it sounds not fully consistent to explicitly limit max-bw while relying on
SW to sanitize frequency ranges. Not that it really matters in practice, but it
has a potential to simplify the rules (i.e. provide max-bw parameter only if the
according country defines restrictions and leave SW to handle it otherwise).
Cheers,
Zefir
next prev parent reply other threads:[~2015-07-06 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 5:44 wireless-regdb: update CA rules for 5600 - 5650 mHz Wei Zhong
2015-07-02 13:48 ` Seth Forshee
2015-07-02 14:21 ` Wei Zhong
2015-07-02 14:31 ` Seth Forshee
2015-07-03 11:08 ` Zefir Kurtisi
2015-07-03 14:20 ` Wei Zhong
2015-07-03 15:01 ` Zefir Kurtisi
2015-07-06 13:27 ` Seth Forshee
2015-07-06 14:40 ` Zefir Kurtisi [this message]
2015-07-06 17:13 ` Wei Zhong
2015-07-07 20:11 ` Seth Forshee
2015-07-08 10:19 ` Zefir Kurtisi
2015-07-09 14:04 ` Seth Forshee
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=559A9378.7000006@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=linux-wireless@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=wireless-regdb@lists.infradead.org \
--cc=wzhong@google.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).