From: Seth Forshee <seth.forshee@canonical.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: wireless-regdb <wireless-regdb@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 4/5] wireless-regdb: Update 5GHz rules for US
Date: Tue, 4 Aug 2015 08:43:17 -0500 [thread overview]
Message-ID: <20150804134317.GB78399@ubuntu-hedt> (raw)
In-Reply-To: <CAGb2v650TmbAtkvK8YWQvzcoxkgB21=Lr6LXZ4uOZe9OGzqSpw@mail.gmail.com>
On Tue, Aug 04, 2015 at 09:31:58AM +0800, Chen-Yu Tsai wrote:
> On Tue, Aug 4, 2015 at 2:34 AM, Seth Forshee <seth.forshee@canonical.com> wrote:
> > On Thu, Jul 23, 2015 at 11:32:59AM +0800, Chen-Yu Tsai wrote:
> >> The FCC increased the maximum conducted transmission power for the
> >> U-NII-1 (5150 ~ 5250 MHz) band to 30 dBm or 1 W for master devices
> >> and 24 dBm or 250 mW for mobile/portable devices.
> >>
> >> Effective 6/2/2014.
> >>
> >> See FCC KDB 905462 D06.
> >>
> >> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >> ---
> >> db.txt | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/db.txt b/db.txt
> >> index cadd52c..29ba4b6 100644
> >> --- a/db.txt
> >> +++ b/db.txt
> >> @@ -1160,7 +1160,7 @@ country UG: DFS-FCC
> >>
> >> country US: DFS-FCC
> >> (2402 - 2472 @ 40), (30)
> >> - (5170 - 5250 @ 80), (17), AUTO-BW
> >> + (5170 - 5250 @ 80), (30), AUTO-BW
> >
> > The 30 dB limit is for devices in master mode, for clients the limit
> > seems to be 250 mW (about 24 dB). Given the TPC requirement for U-NII
> > devices the most it could be bumped up to is 21 dB, unless there's some
> > other reason I don't know about to keep it at 17 dB.
>
> I suppose we have no way to differentiate between master mode and clients?
> I'll drop it down to 24 dBm and add a comment above it.
We don't have any way to specify differing rules for APs and clients
today.
Probably the limit should be 23 dBm instead, since 250 mW comes out to
just less than 24 dBm. Better to be conservative, and besides that is
consistent with other ranges which have a 250 mW limit.
> As for 17 dB, that was the original limit prior to the bump, as seen in
> the FCC KDB attachment "905462 D05 802.11 Channel Plans Old Rules v01".
Ah, okay.
Thanks,
Seth
next prev parent reply other threads:[~2015-08-04 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 3:32 [PATCH v2 0/5] wireless-regdb: Update TW and US rules to latest regulations Chen-Yu Tsai
2015-07-23 3:32 ` [PATCH v2 1/5] wireless-regdb: Update U-NII-2c (5470 ~ 5725 MHz) rules for Taiwan (TW) Chen-Yu Tsai
2015-08-03 18:27 ` Seth Forshee
2015-08-04 1:26 ` Chen-Yu Tsai
2015-08-04 1:55 ` Chen-Yu Tsai
2015-08-04 13:37 ` Seth Forshee
2015-07-23 3:32 ` [PATCH v2 2/5] wireless-regdb: Update regulatory rule boundary frequencies " Chen-Yu Tsai
2015-07-23 3:32 ` [PATCH v2 3/5] wireless-regdb: Add U-NII-1 (5150 ~ 5250 MHz) band " Chen-Yu Tsai
2015-08-03 18:40 ` Seth Forshee
2015-07-23 3:32 ` [PATCH v2 4/5] wireless-regdb: Update 5GHz rules for US Chen-Yu Tsai
2015-08-03 18:34 ` Seth Forshee
2015-08-03 18:47 ` Seth Forshee
2015-08-04 1:31 ` Chen-Yu Tsai
2015-08-04 13:43 ` Seth Forshee [this message]
2015-07-23 3:33 ` [PATCH v2 5/5] wireless-regdb: Update 5 GHz rules for Taiwan (TW) to follow US Chen-Yu Tsai
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=20150804134317.GB78399@ubuntu-hedt \
--to=seth.forshee@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wens@csie.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).