From: Felix Fietkau <nbd@openwrt.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Mark Mentovai <mark@moxienet.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: fix maximum tx power handling
Date: Fri, 04 Feb 2011 20:26:02 +0100 [thread overview]
Message-ID: <4D4C52CA.3030806@openwrt.org> (raw)
In-Reply-To: <AANLkTikNUv2VuL8ftQAF_x4R-ccB0Y_aPFFdF52UBnBt@mail.gmail.com>
On 2011-02-04 8:20 PM, Luis R. Rodriguez wrote:
> On Sun, Jan 30, 2011 at 9:01 AM, Mark Mentovai <mark@moxienet.com> wrote:
>> I certainly like the idea of providing better feedback of the
>> effective power level, or even the power level limit, back to users.
>> This patch seems to artificially limit the effective power level in
>> some cases, while allowing a value in excess of what would be
>> appropriate in others.
>
> John, Mark's interpretation is correct, the exception here is accepted
> because the driver request is being respected to override the max
> regulatory power, nothing more. Felix are you observing userspace
> requests overriding the orig power?
What I'm observing is that with the first regdomain setting it sets
orig_power to something that exceeds the tx power value that the
hardware is capable of using.
Because of that, the tx power setting reported to the user is wrong.
- Felix
next prev parent reply other threads:[~2011-02-04 19:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 17:01 [PATCH] cfg80211: fix maximum tx power handling Mark Mentovai
2011-01-31 18:43 ` Luis R. Rodriguez
2011-02-03 21:25 ` John W. Linville
2011-02-03 22:11 ` Luis R. Rodriguez
2011-02-04 19:20 ` Luis R. Rodriguez
2011-02-04 19:26 ` Felix Fietkau [this message]
2011-02-04 19:36 ` Luis R. Rodriguez
2011-02-04 19:42 ` Mark Mentovai
2011-02-04 19:49 ` Luis R. Rodriguez
2011-02-04 20:19 ` Mark Mentovai
2011-02-04 21:28 ` Felix Fietkau
2011-02-04 20:00 ` Felix Fietkau
-- strict thread matches above, loose matches on Subject: below --
2011-01-29 13:51 Felix Fietkau
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=4D4C52CA.3030806@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mark@moxienet.com \
--cc=mcgrof@gmail.com \
/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.