From: Felix Fietkau <nbd@openwrt.org>
To: Mark Mentovai <mark@moxienet.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: fix maximum tx power handling
Date: Fri, 04 Feb 2011 22:28:52 +0100 [thread overview]
Message-ID: <4D4C6F94.2070709@openwrt.org> (raw)
In-Reply-To: <AANLkTim7cnHNsYqezre3AGaEmnPkjafqmHcpk=1hw7gr@mail.gmail.com>
On 2011-02-04 9:19 PM, Mark Mentovai wrote:
> That would work for ath9k. I still think it’d be prudent to examine a
> handful of rates. I also seem to remember that some other values that
> were being used within ath9k_init_txpower_limits were invalid. I think
> ntxchains was invalid during that early phase of initialization, for
> example. That might not have any ultimate effect on the result, but
> it’s not right to hit that ath_debug claiming "Invalid chainmask
> configuration" once for every supported channel every time the driver
> initializes.
I'll take a look at fixing all of that stuff soon, then we can go back
to treating the driver's tx power values as a limit afterwards.
- Felix
next prev parent reply other threads:[~2011-02-04 21:28 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
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 [this message]
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=4D4C6F94.2070709@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 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).