From: Johannes Berg <johannes@sipsolutions.net>
To: "Seth Forshee" <seth.forshee@canonical.com>,
"Karl Möller" <karl@excors.net>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for South Africa (ZA) on 5GHz
Date: Mon, 28 Sep 2015 19:42:45 +0200 [thread overview]
Message-ID: <1443462165.2401.7.camel@sipsolutions.net> (raw)
In-Reply-To: <20150928160741.GA25936@ubuntu-hedt> (sfid-20150928_180803_494069_1D6E674B)
On Mon, 2015-09-28 at 11:07 -0500, Seth Forshee wrote:
> On Mon, Sep 28, 2015 at 09:44:20AM +0200, Johannes Berg wrote:
> >
> > > The bands don’t quite match up and DFS/TPC is (apparently) not
> > > required for 5470 - 5725. More importantly, the max transmitted
> > > power
> > > seems to be 1W/30dBm e.i.r.p and not 27dBm.
> >
> > Without checking now, just a note: we sometimes have lower limits
> > here
> > due to spectral power density, indoor/outdoor or TPC requirements.
>
> One of the documents says that the TPC requirement for that range was
> lifted in March 2015, so if it was lowered for TPC then we may be
> able to bump it up to 30 dBm.
>
That's very well possible then - the typical TCP requirement is "1/2 of
the power w/o TPC", which would match the 3dB
johannes
next prev parent reply other threads:[~2015-09-28 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 19:10 wireless-regdb: Update regulatory rules for South Africa (ZA) on 5GHz Karl Möller
2015-09-28 7:44 ` [wireless-regdb] " Johannes Berg
2015-09-28 16:07 ` Seth Forshee
2015-09-28 17:42 ` Johannes Berg [this message]
2015-09-28 20:26 ` Karl Möller
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=1443462165.2401.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=karl@excors.net \
--cc=linux-wireless@vger.kernel.org \
--cc=seth.forshee@canonical.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;
as well as URLs for NNTP newsgroup(s).