Linux wireless drivers development
 help / color / mirror / Atom feed
From: Cesar Eduardo Barros <cesarb@cesarb.eti.br>
To: Seth Forshee <sforshee@kernel.org>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for Brazil (BR)
Date: Wed, 31 Aug 2022 23:44:17 -0300	[thread overview]
Message-ID: <2cf2cb6e-8083-9c09-c2a6-ae49424ea37a@cesarb.eti.br> (raw)
In-Reply-To: <Yw4cTotCZm7CH/v7@ubuntu-x1>

Em 30/08/2022 11:18, Seth Forshee escreveu:
> On Wed, Aug 17, 2022 at 08:31:56PM -0300, Cesar Eduardo Barros wrote:
>> 	#(902 - 907.5 @ ???), (30)
>> 	#(915 - 928 @ ???), (30)
> 
> For these ranges I think you should use the same bandwidth as other
> rules in the database, i.e. 2 and 16 MHz.

I found only two entries in the database with rules for the 900MHz 
frequencies: US and "world". I don't think the US rule is a good model 
here; it can use 16 MHz because it's a contiguous range, but the range 
for Brazil has a hole in the middle.

Since there's nothing that a found in these rules which mention a 
maximum channel width, the correct width is probably the maximum which 
fits on each piece of the range. That is,

(902 - 907.5 @ 4), (30)
(915 - 928 @ 8), (30)

As far as I could find, the hole between 907.5 and 915 exists because 
there are three 2.5 MHz-wide GSM uplink channels there. However, I also 
found out that there is a proposal within ANATEL (Consulta Pública 52 
from 2021) to expand it with another uplink channel at 905 - 907.5 
(there are actually five uplink channels in that proposal, the other one 
is at 898.5 - 901). I have no idea when this will become official, or 
whether it has already happened (and just wasn't reflected yet in the 
restricted radiation rules I had researched), and what effect it would 
have on 802.11ah users.

Given the uncertainty from that change, and given that so far there are 
rules for the 900 MHz range in wireless-regdb only for the USA, it might 
be wise to hold it for now and apply only the rest of the changes, 
without these 900 MHz ranges.

> Otherwise I think these changes look good. If you can send a patch with
> the changes I would appreciate it, otherwise let me know and I can send
> a patch.

I will prepare a patch tomorrow.

-- 
Cesar Eduardo Barros
cesarb@cesarb.eti.br


  reply	other threads:[~2022-09-01  2:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 23:31 wireless-regdb: Update regulatory rules for Brazil (BR) Cesar Eduardo Barros
2022-08-18  0:07 ` [wireless-regdb] " Cesar Eduardo Barros
2022-08-18  0:36   ` Cesar Eduardo Barros
2022-08-30 14:18 ` Seth Forshee
2022-09-01  2:44   ` Cesar Eduardo Barros [this message]
2022-09-01 12:50     ` 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=2cf2cb6e-8083-9c09-c2a6-ae49424ea37a@cesarb.eti.br \
    --to=cesarb@cesarb.eti.br \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sforshee@kernel.org \
    --cc=wireless-regdb@lists.infradead.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