From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net,
Larry.Finger@lwfinger.net, mcgrof@gmail.com
Subject: Re: [PATCH] cfg80211: default to regulatory max power for channel
Date: Thu, 3 Apr 2008 22:08:37 +0200 [thread overview]
Message-ID: <200804032208.37588.mb@bu3sch.de> (raw)
In-Reply-To: <1207251174-23860-1-git-send-email-linville@tuxdriver.com>
On Thursday 03 April 2008 21:32:54 John W. Linville wrote:
> If the driver does not specify a maximum power output, default to the
> regulatory max.
>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
> Is this a worth alternative to Larry's b43legacy patch? It looked like
Yeah, I like this one much better.
The b43 devices can all be configured up to regulatory limits.
So it doesn't really make sense to define a hardware limit.
And I think we currently don't even know the real HW limit. One might
try to calculate it, but that seems difficult.
> ath5k wasn't setting max_power either -- how does it work?
>
> net/wireless/reg.c | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/net/wireless/reg.c b/net/wireless/reg.c
> index 8cc6037..185488d 100644
> --- a/net/wireless/reg.c
> +++ b/net/wireless/reg.c
> @@ -136,7 +136,10 @@ static void handle_channel(struct ieee80211_channel *chan,
> chan->flags = flags;
> chan->max_antenna_gain = min(chan->orig_mag,
> rg->max_antenna_gain);
> - chan->max_power = min(chan->orig_mpwr, rg->max_power);
> + if (chan->orig_mpwr)
> + chan->max_power = min(chan->orig_mpwr, rg->max_power);
> + else
> + chan->max_power = rg->max_power;
> }
>
> static void handle_band(struct ieee80211_supported_band *sband,
--
Greetings Michael.
next prev parent reply other threads:[~2008-04-03 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY103-F373BE8D28C2F2A21BC15E0D8F70@phx.gbl>
[not found] ` <200804031719.44026.mb@bu3sch.de>
2008-04-03 18:38 ` [PATCH] b43legacy: Partial Fix for Range issue Larry Finger
2008-04-03 18:50 ` Michael Buesch
2008-04-03 20:10 ` Larry Finger
2008-04-03 19:32 ` [PATCH] cfg80211: default to regulatory max power for channel John W. Linville
2008-04-03 20:08 ` Michael Buesch [this message]
2008-04-03 21:01 ` Larry Finger
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=200804032208.37588.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.