Wireless-regdb Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Daiwei Li <daiweili@suitabletech.com>
Cc: Jouni Malinen <jouni@qca.qualcomm.com>,
	"wireless-regdb@lists.infradead.org"
	<wireless-regdb@lists.infradead.org>
Subject: Re: [wireless-regdb] [PATCH] wireless-regdb: Add back regulatory rules for US
Date: Sun, 18 Jan 2015 21:00:11 -0600	[thread overview]
Message-ID: <20150119030011.GA95848@ubuntu-hedt> (raw)
In-Reply-To: <CALf=PEbVwhqoV2-aXsNDJNB+wHrJm=ZNx6cYedjt7hu6UPJENg@mail.gmail.com>

On Fri, Jan 16, 2015 at 07:42:12PM -0800, Daiwei Li wrote:
> Hello,
> 
> We've found that our devices can't seem to operate on certain
> frequencies (e.g. 5660MHz) being used by access points like the Apple
> Airport Extreme and Asus RT-AC68U. I did a git bisect and found that
> 31dc1c5eca29d039ac8f26340defe44bd7e497c1 removed that band amongst
> others. A more recent [1] FCC source implies that these frequencies
> should be usable with DFS.
> 
> Does anyone know the source for the commit that removed these frequencies from?

The patch came from QCA. I'm adding Jouni to the Cc. Jouni, any
comments?

> Below is a patch that adds back these frequencies:
> -------------------------------------------------------------------------------------
> wireless-regdb: Add back regulatory rules for US
> 
> The FCC approved UNII devices operating in the
> 5470 - 5725MHz range with radar detection and DFS
> capabilities. See the [1] source for details.
> 
> [1] https://apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?id=41732&switch=P
> 
> Signed-off-by: Daiwei Li <daiweili@suitabletech.com>

This looks reasonable based on the documentation you linked to. I'm not
certain about the EIRP values, but that's at least consistent with what
was there before (i.e. they match the EIRP for the first DFS frequency
range).

I'm going to wait a bit to see if anyone has any comments about the
patch, and if no one objects I'll apply it.

Thanks,
Seth

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb


  reply	other threads:[~2015-01-19  3:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17  3:42 [wireless-regdb] [PATCH] wireless-regdb: Add back regulatory rules for US Daiwei Li
2015-01-19  3:00 ` Seth Forshee [this message]
2015-01-19 22:30   ` Daiwei Li
2015-01-23 10:37 ` Jouni Malinen
2015-01-23 15:33   ` Seth Forshee
2015-01-23 18:19     ` Daiwei Li
2015-01-30 14:48       ` 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=20150119030011.GA95848@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=daiweili@suitabletech.com \
    --cc=jouni@qca.qualcomm.com \
    --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