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 11:11:00 -0500 [thread overview]
Message-ID: <20160325161100.GA112464@ubuntu-hedt> (raw)
In-Reply-To: <215edc732bbb4c8aa7b38dd1273f372a@ausx13mpc122.AMER.DELL.COM>
On Fri, Mar 25, 2016 at 03:59:30PM +0000, Thanh_Nguyen@Dell.com wrote:
> Seth,
> The sources I am using are also unofficial:
>
> o Broadcom’s document showing Russia allow 2.400-2.4835 (Ch 1-13), 5.15-5.25GHz (Ch 36-48), 5.25-5.35GHz (Ch 52-64), 5.470-5.725GHz (Ch 100-140)
>
> o Wi-Fi Russian Certificates that Broadcom and Intel (and some other major suppliers) provided to Dell don’t cover 5735-5835 MHz band
> I will try to obtain official documentation of Russia's regulations.
Thanks, that would be helpful. All I could turn up was a document
regarding fixed wireless installations, in which the 5375-5835 MHz range
was allowed.
> Regarding the Patch, I am new to Linux and I am not sure what that is. It will be great if you can make one or guide me how to do it.
Let's hold off a bit. That will give you some time to look for some
official sources, and I'd also like to leave a little time to see if QCA
has any comments since the rules we currently have for Russia came from
them.
Seth
prev parent reply other threads:[~2016-03-25 16:11 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 ` wireless-regdb: Update regulatory rules for Russia (RU) on 5735-5835 MHz band Seth Forshee
[not found] ` <215edc732bbb4c8aa7b38dd1273f372a@ausx13mpc122.AMER.DELL.COM>
2016-03-25 16:11 ` Seth Forshee [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=20160325161100.GA112464@ubuntu-hedt \
--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).