From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Fix ETSI compliance for AR9462 2.0
Date: Fri, 14 Feb 2014 16:34:41 +0100 [thread overview]
Message-ID: <52FE3791.8020104@openwrt.org> (raw)
In-Reply-To: <1392345920-28891-1-git-send-email-sujith@msujith.org>
On 2014-02-14 03:45, Sujith Manoharan wrote:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> The minimum CCA power threshold values have to be adjusted
> for existing cards to be in compliance with new regulations.
> Newer cards will make use of the values obtained from EEPROM,
> support for this was added earlier. To make sure that cards
> that are already in use and don't have proper values in EEPROM,
> do not violate regulations, use the initvals instead.
>
> Cc: stable at vger.kernel.org
> Reported-by: Jeang Daniel <dyjeong@qca.qualcomm.com>
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Wouldn't it be better to do this for all AR93xx chipsets in
ar9003_hw_apply_minccapwr_thresh instead of initvals?
I'm pretty sure this patch will leave most other devices non-compliant.
- Felix
WARNING: multiple messages have this Message-ID (diff)
From: Felix Fietkau <nbd@openwrt.org>
To: Sujith Manoharan <sujith@msujith.org>,
John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org
Subject: Re: [PATCH] ath9k: Fix ETSI compliance for AR9462 2.0
Date: Fri, 14 Feb 2014 16:34:41 +0100 [thread overview]
Message-ID: <52FE3791.8020104@openwrt.org> (raw)
In-Reply-To: <1392345920-28891-1-git-send-email-sujith@msujith.org>
On 2014-02-14 03:45, Sujith Manoharan wrote:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> The minimum CCA power threshold values have to be adjusted
> for existing cards to be in compliance with new regulations.
> Newer cards will make use of the values obtained from EEPROM,
> support for this was added earlier. To make sure that cards
> that are already in use and don't have proper values in EEPROM,
> do not violate regulations, use the initvals instead.
>
> Cc: stable@vger.kernel.org
> Reported-by: Jeang Daniel <dyjeong@qca.qualcomm.com>
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Wouldn't it be better to do this for all AR93xx chipsets in
ar9003_hw_apply_minccapwr_thresh instead of initvals?
I'm pretty sure this patch will leave most other devices non-compliant.
- Felix
next prev parent reply other threads:[~2014-02-14 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 2:45 [ath9k-devel] [PATCH] ath9k: Fix ETSI compliance for AR9462 2.0 Sujith Manoharan
2014-02-14 2:45 ` Sujith Manoharan
2014-02-14 15:34 ` Felix Fietkau [this message]
2014-02-14 15:34 ` Felix Fietkau
2014-02-17 2:27 ` [ath9k-devel] " Sujith Manoharan
2014-02-17 2:27 ` Sujith Manoharan
2014-02-17 2:46 ` [ath9k-devel] " Felix Fietkau
2014-02-17 2:46 ` Felix Fietkau
2014-02-17 3:07 ` [ath9k-devel] " Sujith Manoharan
2014-02-17 3:07 ` Sujith Manoharan
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=52FE3791.8020104@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.org \
/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.