linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	"Felix Fietkau" <nbd@openwrt.org>,
	"Thomas Hühn" <thomas@net.t-labs.tu-berlin.de>
Subject: Re: [PATCHv4] mac80211: enable TPC through mac80211 stack
Date: Wed, 14 Jan 2015 09:29:40 +0100	[thread overview]
Message-ID: <1421224180.1950.10.camel@sipsolutions.net> (raw)
In-Reply-To: <CAA2SeNL76Pd3ft4biBsHD9oTA4JOpD7oa5E+5ajk37irSDPhtw@mail.gmail.com> (sfid-20150108_120711_878615_1424844D)

Sorry ...

On Thu, 2015-01-08 at 12:07 +0100, Lorenzo Bianconi wrote:

> Sounds good, now I have clearer vision :)
> I will overwrite bss_conf nl80211_tx_power_setting value in
> ieee80211_set_tx_power() when txpower type is set to
> NL80211_TX_POWER_AUTOMATIC from userspace. Moreover should we set
> nl80211_tx_power_setting to NL80211_TX_POWER_LIMITED in
> ieee80211_handle_pwr_constr() when the station receives a power
> constraint in beacon frames? What do you think?

Isn't it basically always only valid to have LIMITED and FIXED? I don't
see much value in fixed really though, but if the user requested
that ...

johannes


      reply	other threads:[~2015-01-14  8:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 17:41 [PATCHv4] mac80211: enable TPC through mac80211 stack Lorenzo Bianconi
2015-01-07 14:12 ` Johannes Berg
2015-01-07 14:39   ` Lorenzo Bianconi
2015-01-08  7:48     ` Johannes Berg
2015-01-08 11:07       ` Lorenzo Bianconi
2015-01-14  8:29         ` Johannes Berg [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=1421224180.1950.10.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi83@gmail.com \
    --cc=nbd@openwrt.org \
    --cc=thomas@net.t-labs.tu-berlin.de \
    /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).