public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: Chen-Yu Tsai <wens@csie.org>,
	wireless-regdb@lists.infradead.org,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless-regdb: Extend 5470-5725 MHz range to 5730 MHz for Taiwan (TW)
Date: Tue, 29 Oct 2019 07:20:33 -0500	[thread overview]
Message-ID: <20191029122033.GK30813@ubuntu-xps13> (raw)
In-Reply-To: <20190809205025.GP10402@ubuntu-xps13>

On Fri, Aug 09, 2019 at 03:50:25PM -0500, Seth Forshee wrote:
> On Fri, Jul 26, 2019 at 11:05:38AM +0800, Chen-Yu Tsai wrote:
> > From: Chen-Yu Tsai <wens@csie.org>
> > 
> > This range ends at 5725 MHz, but channel 144 extends to 5730 MHz.
> > The Linux kernel however does not seem capable of considering them
> > most restrictive subset of multiple rules.
> > 
> > Since 5725 ~ 5730 MHz belongs to the next range which has looser
> > requirements, we can do this manually and extend the range by 5 MHz
> > to make the kernel happy and be able to use channel 144.
> > 
> > Also, looking at the US regulations, which the TW ones are based on,
> > The DFS range ends at 5730 MHz, while the next range starts at 5735
> > MHz. This doesn't match the actual regulations, but is skewed to meet
> > wireless channel boundaries. I prefer the database match the law,
> > and be adjuested only if necessary.
> > 
> > Signed-off-by: Chen-Yu Tsai <wens@csie.org>

Sorry for the delay, applied now. Thanks!


      reply	other threads:[~2019-10-29 12:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26  3:05 [PATCH] wireless-regdb: Extend 5470-5725 MHz range to 5730 MHz for Taiwan (TW) Chen-Yu Tsai
2019-08-09 20:50 ` Seth Forshee
2019-10-29 12:20   ` 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=20191029122033.GK30813@ubuntu-xps13 \
    --to=seth.forshee@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wens@csie.org \
    --cc=wens@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