Linux wireless drivers development
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: suchan <abnoeh@mail.com>
Cc: wireless-regdb@lists.infradead.org,
	Peter Oh <peter.oh@bowerswilkins.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] [PATCH v2] wireless-regdb: Update regulatory rules for South Korea
Date: Wed, 15 May 2019 11:21:42 -0500	[thread overview]
Message-ID: <20190515162142.GC4357@ubuntu-xps13> (raw)
In-Reply-To: <a2fa616d-7829-137c-7f48-6c59974cfa46@mail.com>

You dropped Peter and the linux-wireless list from your reply, adding
them back.

On Thu, May 16, 2019 at 12:10:16AM +0900, suchan wrote:
> 
> 2019-05-15 10:03PM at Seth Forshee wrote:
> > 
> > Is there any mention of transmit power control in the document? The fact
> > that some of the old limits are exactly half of they values you've given
> > makes me wonder if they weren't set lower for TPC, especially for
> > 5250-5350 MHz where TPC is common.
> > 
> > Since you're changing these rules, I'd also like to see the frequency
> > ranges changed to match the documented ranges, i.e.:
> > 
> >   2400 - 2483.5
> >   5150 - 5250
> >   5250 - 5350
> >   5470 - 5710
> >   5735 - 5850
> > 
> > I left the gap in the 5470-5850 MHz range since I can't tell exactly
> > where the DFS requirement ends. Usually it seems to be 5725 MHz, but
> > that is not universal. If you can determine where the break is those
> > ranges could also be expanded.
> > 
> > Thanks,
> > Seth
> > 
> > _______________________________________________
> > wireless-regdb mailing list
> > wireless-regdb@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/wireless-regdb
> 
> from same document, just under the table for wifi range itself 5250∼5350
> MHz and 5470∼5725 MHz need TPC and DFS
> 
> TPC rule is if power exceeds 25mW/MHz (this includes antenna gain), it
> has do be able to reduce it under 12.5mW/Mhz.
> 
> DFS rule itself (DFS-JP) looks right.

Thanks! Based on that I think this is probably what we need:

 (2400 - 2483.5 @ 40), (23)
 (5150 - 5250 @ 80), (23), AUTO-BW
 (5250 - 5350 @ 80), (20), DFS, AUTO-BW
 (5470 - 5725 @ 160), (20), DFS
 (5725 - 5835 @ 80), (23)

Peter, if that looks good to you please send a v3 patch.

Thanks,
Seth

  parent reply	other threads:[~2019-05-15 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 21:31 [PATCH v2] wireless-regdb: Update regulatory rules for South Korea Peter Oh
2019-05-15 13:03 ` [wireless-regdb] " Seth Forshee
     [not found]   ` <a2fa616d-7829-137c-7f48-6c59974cfa46@mail.com>
2019-05-15 16:21     ` Seth Forshee [this message]
2019-05-15 19:08       ` Peter Oh

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=20190515162142.GC4357@ubuntu-xps13 \
    --to=seth.forshee@canonical.com \
    --cc=abnoeh@mail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=peter.oh@bowerswilkins.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