All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Petko Bordjukov <bordjukov@gmail.com>,
	wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] Updates for the regulatory rules for Bulgaria
Date: Thu, 21 Apr 2016 18:56:45 +0200	[thread overview]
Message-ID: <20160421165645.GW1990@wotan.suse.de> (raw)
In-Reply-To: <20160421163410.GC95003@ubuntu-hedt>

On Thu, Apr 21, 2016 at 11:34:10AM -0500, Seth Forshee wrote:
> 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.

When I looked at adding support for Linux, IIRC the status of affairs
was that it was complex, and iffy, and no one ever really implemented
it even on Windows / OSX so the adjustments were easier to make so
that's what people did.

  Luis

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb


      reply	other threads:[~2016-04-21 16:57 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
2016-04-21 16:56       ` Luis R. Rodriguez [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=20160421165645.GW1990@wotan.suse.de \
    --to=mcgrof@suse.com \
    --cc=bordjukov@gmail.com \
    --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 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.