From: Gertjan van Wingerde <gwingerde@gmail.com>
To: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Hong Wu <Hong.Wu@dspg.com>,
helmut.schaa@googlemail.com, openwrt-devel@lists.openwrt.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rt2800: Initialize max_txpower to MAX_G_TXPOWER and MAX_A_TXPOWER respectively
Date: Fri, 18 May 2012 08:57:57 +0200 [thread overview]
Message-ID: <4FB5F2F5.7090702@gmail.com> (raw)
In-Reply-To: <20120517230400.GB22418@yumi.tdiedrich.de>
On 05/18/12 01:04, Tobias Diedrich wrote:
> rt2800: Initialize max_txpower to MAX_G_TXPOWER and MAX_A_TXPOWER
> respectively, similar to how it is already done in rt2[45]00pci.c
>
> rt2800lib.c doesn't initialize max_power and thus after
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next.git;a=commitdiff;h=eccc068e8e84c8fe997115629925e0422a98e4de
> was applied txpower is limited to 0 for these devices.
>
> This should be the proper fix compared to the net/wireless/reg.c
> hack in http://patchwork.openwrt.org/patch/2165/
>
> (Patch against the OpenWRT compat-wireless version, but applies
> equally well against wireless-next with a 19-line offset)
>
> Signed-off-by: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>
>
>
> Index: compat-wireless-2012-04-17/drivers/net/wireless/rt2x00/rt2800lib.c
> ===================================================================
> --- compat-wireless-2012-04-17.orig/drivers/net/wireless/rt2x00/rt2800lib.c 2012-05-18 00:25:22.515271380 +0200
> +++ compat-wireless-2012-04-17/drivers/net/wireless/rt2x00/rt2800lib.c 2012-05-18 00:28:48.809658951 +0200
> @@ -4622,6 +4622,7 @@
> default_power2 = rt2x00_eeprom_addr(rt2x00dev, EEPROM_TXPOWER_BG2);
>
> for (i = 0; i < 14; i++) {
> + info[i].max_power = MAX_G_TXPOWER;
> info[i].default_power1 = default_power1[i];
> info[i].default_power2 = default_power2[i];
> }
> @@ -4631,6 +4632,7 @@
> default_power2 = rt2x00_eeprom_addr(rt2x00dev, EEPROM_TXPOWER_A2);
>
> for (i = 14; i < spec->num_channels; i++) {
> + info[i].max_power = MAX_A_TXPOWER;
> info[i].default_power1 = default_power1[i];
> info[i].default_power2 = default_power2[i];
> }
>
--
---
Gertjan
next prev parent reply other threads:[~2012-05-18 7:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 23:04 [PATCH] rt2800: Initialize max_txpower to MAX_G_TXPOWER and MAX_A_TXPOWER respectively Tobias Diedrich
2012-05-18 6:57 ` Gertjan van Wingerde [this message]
2012-05-18 9:18 ` Helmut Schaa
2012-05-18 12:13 ` Andreas Hartmann
2012-05-18 16:21 ` Tobias Diedrich
2012-05-19 8:14 ` Helmut Schaa
2012-05-19 9:37 ` Andreas Hartmann
2012-05-22 8:38 ` Andreas Hartmann
2012-05-22 10:02 ` Helmut Schaa
2012-05-22 11:26 ` Andreas Hartmann
2012-05-22 11:32 ` Helmut Schaa
2012-05-22 12:47 ` Andreas Hartmann
2012-05-24 7:35 ` Andreas Hartmann
2012-06-04 11:08 ` Stanislaw Gruszka
2012-06-04 12:24 ` Helmut Schaa
2012-05-22 11:33 ` Helmut Schaa
2012-05-22 20:58 ` Tobias Diedrich
2012-05-23 11:32 ` Helmut Schaa
2012-05-23 13:55 ` Tobias Diedrich
2012-05-23 19:30 ` Helmut Schaa
2012-05-23 20:51 ` Tobias Diedrich
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=4FB5F2F5.7090702@gmail.com \
--to=gwingerde@gmail.com \
--cc=Hong.Wu@dspg.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=openwrt-devel@lists.openwrt.org \
--cc=ranma+openwrt@tdiedrich.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).