From: Seth Forshee <seth.forshee@canonical.com>
To: Jouni Malinen <jouni@qca.qualcomm.com>
Cc: "wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>,
Daiwei Li <daiweili@suitabletech.com>
Subject: Re: [wireless-regdb] [PATCH] wireless-regdb: Add back regulatory rules for US
Date: Fri, 23 Jan 2015 09:33:03 -0600 [thread overview]
Message-ID: <20150123153303.GB4094@ubuntu-hedt> (raw)
In-Reply-To: <20150123103720.GA7274@jouni.qca.qualcomm.com>
On Fri, Jan 23, 2015 at 12:37:20PM +0200, Jouni Malinen wrote:
> On Fri, Jan 16, 2015 at 07:42:12PM -0800, Daiwei Li wrote:
> > 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?
>
> I'm not sure what the exact rationale for that part of the commit was.
>
> > @@ -1125,6 +1125,8 @@ country US: DFS-FCC
> > (2402 - 2472 @ 40), (30)
> > (5170 - 5250 @ 80), (17), AUTO-BW
> > (5250 - 5330 @ 80), (23), DFS, AUTO-BW
> > + (5490 - 5600 @ 80), (23), DFS, AUTO-BW
> > + (5650 - 5710 @ 40), (23), DFS, AUTO-BW
> > (5735 - 5835 @ 80), (30)
>
> AUTO-BW does not seem to make much sense here since neither new range
> has immediately neighboring ranges with different flags.
Good point. Daiwei, care to send an updated patch?
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2015-01-23 15:33 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
2015-01-19 22:30 ` Daiwei Li
2015-01-23 10:37 ` Jouni Malinen
2015-01-23 15:33 ` Seth Forshee [this message]
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=20150123153303.GB4094@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