From: Felix Fietkau <nbd@openwrt.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH 2/4] ath9k: add debugfs files for reading/writing the rx and tx chainmask
Date: Tue, 11 May 2010 21:55:06 +0200 [thread overview]
Message-ID: <4BE9B61A.2090708@openwrt.org> (raw)
In-Reply-To: <AANLkTilDwhBErduNt_vZLSsEVVkC1SDMwUPkoumym1o3@mail.gmail.com>
On 2010-05-11 8:15 PM, Luis R. Rodriguez wrote:
> On Tue, May 11, 2010 at 8:23 AM, Felix Fietkau <nbd@openwrt.org> wrote:
>> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
>
> How about we use bruno's patch instead and we help review it for
> 802.11n? Then this would not be needed?
I'd like to keep those separate. I've seen cards where the wrong
chainmask was programmed into the eeprom, this debugfs file is for
detecting that and trying other settings.
When Bruno's patch gets implemented for ath9k, the values that it can
set should be masked by the internal value, while the debugfs file can
override the internal value.
- Felix
next prev parent reply other threads:[~2010-05-11 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 15:23 [PATCH 1/4] ath9k: use debugfs_remove_recursive() instead of keeping pointers to all entries Felix Fietkau
2010-05-11 15:23 ` [PATCH 2/4] ath9k: add debugfs files for reading/writing the rx and tx chainmask Felix Fietkau
2010-05-11 15:23 ` [PATCH 3/4] ath9k: add debugfs files for reading/writing registers Felix Fietkau
2010-05-11 15:23 ` [PATCH 4/4] ath9k_hw: clean up EEPROM endian handling on AR9003 Felix Fietkau
2010-05-12 6:03 ` [PATCH 3/4] ath9k: add debugfs files for reading/writing registers Benoit Papillault
2010-05-11 18:15 ` [PATCH 2/4] ath9k: add debugfs files for reading/writing the rx and tx chainmask Luis R. Rodriguez
2010-05-11 19:55 ` Felix Fietkau [this message]
2010-05-11 20:14 ` Luis R. Rodriguez
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=4BE9B61A.2090708@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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.