From: Seth Forshee <seth.forshee@canonical.com>
To: Thanh_Nguyen@Dell.com
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: wireless-regdb: Update regulatory rules for Russia (RU) on 5735-5835 MHz band
Date: Fri, 25 Mar 2016 08:51:47 -0500 [thread overview]
Message-ID: <20160325135147.GA27324@ubuntu-xps13> (raw)
In-Reply-To: <b7a3a22077814e7da4e94a61e59c585d@ausx13mpc122.AMER.DELL.COM>
On Thu, Mar 24, 2016 at 09:19:46PM +0000, Thanh_Nguyen@Dell.com wrote:
> Dear Seth,
> Currently the db.txt has following setting for Russia:
>
> country RU: DFS-ETSI
> (2402 - 2482 @ 40), (20)
> (5170 - 5250 @ 80), (20), AUTO-BW
> (5250 - 5330 @ 80), (20), DFS, AUTO-BW
> (5650 - 5730 @ 80), (30), DFS
> (5735 - 5835 @ 80), (30)
> # 60 GHz band channels 1-4, ref: Changes to NLA 124_Order №129_22042015.pdf
> (57000 - 66000 @ 2160), (40)
>
> Dell’s understanding is 5735-5835 MHz band is still not allowed in Russia. Dell would like to submit a request for the wireless-regdb to investigate and update the setting for Russia RU in the db.txt file.
I wasn't able to track down any official documentation of Russia's
regulations, but a few unofficial sources showed that range as being
allowed. What source(s) are you using to determine that it is not?
Feel free to send a patch if you think this should be changed, or I can
make one if you're not comfortable doing so. It would be helpful to have
a link to support the change though.
Thanks,
Seth
next parent reply other threads:[~2016-03-25 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b7a3a22077814e7da4e94a61e59c585d@ausx13mpc122.AMER.DELL.COM>
2016-03-25 13:51 ` Seth Forshee [this message]
[not found] ` <215edc732bbb4c8aa7b38dd1273f372a@ausx13mpc122.AMER.DELL.COM>
2016-03-25 16:11 ` wireless-regdb: Update regulatory rules for Russia (RU) on 5735-5835 MHz band 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=20160325135147.GA27324@ubuntu-xps13 \
--to=seth.forshee@canonical.com \
--cc=Thanh_Nguyen@Dell.com \
--cc=linux-wireless@vger.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;
as well as URLs for NNTP newsgroup(s).