From: Seth Forshee <seth.forshee@canonical.com>
To: Petko Bordjukov <bordjukov@gmail.com>
Cc: wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] Updates for the regulatory rules for Bulgaria
Date: Thu, 21 Apr 2016 11:34:10 -0500 [thread overview]
Message-ID: <20160421163410.GC95003@ubuntu-hedt> (raw)
In-Reply-To: <87fuuf54ai.wl-bordjukov@gmail.com>
On Thu, Apr 21, 2016 at 07:12:53PM +0300, Petko Bordjukov wrote:
> On Thu, 21 Apr 2016 17:07:21 +0300,
> Seth Forshee wrote:
> > This is almost certainly because these frequencies require transmit
> > power control. We drop the TX power limits by half (i.e. 3 dB) when TPC
> > is required on account of not supporting TPC.
>
> I was under the impression that the underlying kernel infrastructure had support
> for TPC. What I am observing is that hostapd automatically includes the Power
> Constraint IE in beacons sent out on any channel with DFS enabled. The default
> transmit power reduction is 3dBm.
>
> This means that the TX power of any clients would be limited to 3dBm below the
> TX power of the AP even though it's not required.
>
> Would there be any merit in providing additional information regarding the TX
> power and the target average TX power reduction for the system when TPC is
> supported?
I'm frankly not certain about the status of kernel support, but my
impression was that some drivers might have some level of TPC support
but that it's not universal. I really haven't been keeping track of it
though.
However, even if there is universal TPC support in the kernel we still
lack any way to encode the TPC requirement for a given rule in the
database or inform the kernel about it.
> > > WAS/RLANs 5150-5250 MHz
> > > 200 mW maximum mean e.i.r.p.
> > > 10 mW/MHz maximum spectral density of the mean e.i.r.p.
> >
> > If this range doesn't require TPC then it could be bumped up to 200 mW
> > (23 dBm).
>
> Yes, the CRC's list explicitly states that TPC is required in the 5250-5350 MHz
> and 5470-5725 MHz bands and there's no further comments on the 5150-5250 MHz
> band. EN 301 893 has the notes below for the 5150-5250 MHz band that could have
> lead to the 3 dBm drop though, maybe linked to the AUTO-BW flag?
>
> > NOTE 1: The applicable limit is 20 dBm, except for transmissions whose nominal
> > bandwidth falls completely within the band 5 150 MHz to 5 250 MHz, in which
> > case the applicable limit is 23 dBm.
> >
> > NOTE 2: The applicable limit is 7 dBm/MHz, except for transmissions whose
> > nominal bandwidth falls completely within the band 5 150 MHz to 5 250 MHz, in
> > which case the applicable limit is 10 dBm/MHz.
It shouldn't be required for the AUTO-BW flag, so based on everything
I'm seeing here 23 dBm seems fine.
> I changed the TX power values to mW to be consistent with what is stated in the
> CRC's list. I'll resubmit the patch with the values in dBm and with the 3 dBm
> drop for the 5250-5350 MHz and 5470-5725 MHz bands.
Great, thanks. I think you should be fine to bump up the 5150-5250 MHz
rule by 3 dBm as well. If someone knows a reason it shouldn't be raised
they can let us know.
Thanks,
Seth
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2016-04-21 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 0:44 [wireless-regdb] Updates for the regulatory rules for Bulgaria Petko Bordjukov
2016-04-20 0:44 ` [wireless-regdb] [PATCH] Update the regulatory rules for Bulgaria (BG) Petko Bordjukov
2016-04-21 17:02 ` [wireless-regdb] [PATCH v2] " Petko Bordjukov
2016-04-21 18:53 ` Seth Forshee
2016-04-22 9:02 ` Petko Bordjukov
2016-04-22 9:07 ` [wireless-regdb] [PATCH v3] " Petko Bordjukov
2016-04-22 13:31 ` [wireless-regdb] [PATCH v4] " Petko Bordjukov
2016-05-02 13:43 ` Seth Forshee
2016-04-21 14:07 ` [wireless-regdb] Updates for the regulatory rules for Bulgaria Seth Forshee
2016-04-21 16:12 ` Petko Bordjukov
2016-04-21 16:34 ` Seth Forshee [this message]
2016-04-21 16:56 ` Luis R. Rodriguez
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=20160421163410.GC95003@ubuntu-hedt \
--to=seth.forshee@canonical.com \
--cc=bordjukov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.