public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: "linville@tuxdriver.com" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ipw3945-devel@lists.sourceforge.net"
	<ipw3945-devel@lists.sourceforge.net>,
	"Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>
Subject: Re: [PATCH 02/13] iwlwifi: fix EEPROM enhance tx power offset
Date: Fri, 02 Oct 2009 13:59:36 -0700	[thread overview]
Message-ID: <1254517177.26521.3503.camel@rc-desk> (raw)
In-Reply-To: <1254516247-4085-3-git-send-email-reinette.chatre@intel.com>

John,

I neglected to mark this patch subject with v2.6.32 - could you please
take this patch for 2.6.32 also?

Thank you very much

Reinette


On Fri, 2009-10-02 at 13:43 -0700, Chatre, Reinette wrote:
> From: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> 
> Set the correct EEPROM offset for enhance tx power for 6000 series
> 
> Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
> ---
>  drivers/net/wireless/iwlwifi/iwl-eeprom.h |   20 ++++++++++----------
>  1 files changed, 10 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/net/wireless/iwlwifi/iwl-eeprom.h b/drivers/net/wireless/iwlwifi/iwl-eeprom.h
> index 75fe022..3bcd600 100644
> --- a/drivers/net/wireless/iwlwifi/iwl-eeprom.h
> +++ b/drivers/net/wireless/iwlwifi/iwl-eeprom.h
> @@ -220,35 +220,35 @@ struct iwl_eeprom_enhanced_txpwr {
>   * Section 10: 2.4 GHz 40MHz channels: 132, 44 (_above_)
>   */
>  /* 2.4 GHz band: CCK */
> -#define EEPROM_LB_CCK_20_COMMON       ((0xAA)\
> +#define EEPROM_LB_CCK_20_COMMON       ((0xA8)\
>  		| INDIRECT_ADDRESS | INDIRECT_REGULATORY)   /* 8 bytes */
>  /* 2.4 GHz band: 20MHz-Legacy, 20MHz-HT, 40MHz-HT */
> -#define EEPROM_LB_OFDM_COMMON       ((0xB2)\
> +#define EEPROM_LB_OFDM_COMMON       ((0xB0)\
>  		| INDIRECT_ADDRESS | INDIRECT_REGULATORY)   /* 24 bytes */
>  /* 5.2 GHz band: 20MHz-Legacy, 20MHz-HT, 40MHz-HT */
> -#define EEPROM_HB_OFDM_COMMON       ((0xCA)\
> +#define EEPROM_HB_OFDM_COMMON       ((0xC8)\
>  		| INDIRECT_ADDRESS | INDIRECT_REGULATORY)   /* 24 bytes */
>  /* 2.4GHz band channels:
>   *	1Legacy, 1HT, 2Legacy, 2HT, 10Legacy, 10HT, 11Legacy, 11HT */
> -#define EEPROM_LB_OFDM_20_BAND       ((0xE2)\
> +#define EEPROM_LB_OFDM_20_BAND       ((0xE0)\
>  		| INDIRECT_ADDRESS | INDIRECT_REGULATORY)   /* 64 bytes */
>  /* 2.4 GHz band HT40 channels: (1,+1) (2,+1) (6,+1) (7,+1) (9,+1) */
> -#define EEPROM_LB_OFDM_HT40_BAND       ((0x122)\
> +#define EEPROM_LB_OFDM_HT40_BAND       ((0x120)\
>  		| INDIRECT_ADDRESS | INDIRECT_REGULATORY)   /* 40 bytes */
>  /* 5.2GHz band channels: 36Legacy, 36HT, 64Legacy, 64HT, 100Legacy, 100HT */
> -#define EEPROM_HB_OFDM_20_BAND       ((0x14A)\
> +#define EEPROM_HB_OFDM_20_BAND       ((0x148)\
>  		| INDIRECT_ADDRESS | INDIRECT_REGULATORY)   /* 48 bytes */
>  /* 5.2 GHz band HT40 channels: (36,+1) (60,+1) (100,+1) */
> -#define EEPROM_HB_OFDM_HT40_BAND       ((0x17A)\
> +#define EEPROM_HB_OFDM_HT40_BAND       ((0x178)\
>  		| INDIRECT_ADDRESS | INDIRECT_REGULATORY)   /* 24 bytes */
>  /* 2.4 GHz band, channnel 13: Legacy, HT */
> -#define EEPROM_LB_OFDM_20_CHANNEL_13       ((0x192)\
> +#define EEPROM_LB_OFDM_20_CHANNEL_13       ((0x190)\
>  		| INDIRECT_ADDRESS | INDIRECT_REGULATORY)   /* 16 bytes */
>  /* 5.2 GHz band, channnel 140: Legacy, HT */
> -#define EEPROM_HB_OFDM_20_CHANNEL_140       ((0x1A2)\
> +#define EEPROM_HB_OFDM_20_CHANNEL_140       ((0x1A0)\
>  		| INDIRECT_ADDRESS | INDIRECT_REGULATORY)   /* 16 bytes */
>  /* 5.2 GHz band, HT40 channnels (132,+1) (44,+1) */
> -#define EEPROM_HB_OFDM_HT40_BAND_1       ((0x1B2)\
> +#define EEPROM_HB_OFDM_HT40_BAND_1       ((0x1B0)\
>  		| INDIRECT_ADDRESS | INDIRECT_REGULATORY)   /* 16 bytes */
>  
> 


  reply	other threads:[~2009-10-02 20:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 20:43 [PATCH 0/13] iwlwifi driver updates 10/2/2009 Reinette Chatre
2009-10-02 20:43 ` [PATCH 01/13 v2.6.31, v2.6.32 and w-t] iwlwifi: incorrect method used for finding valid OTP blocks Reinette Chatre
2009-10-02 20:43 ` [PATCH 02/13] iwlwifi: fix EEPROM enhance tx power offset Reinette Chatre
2009-10-02 20:59   ` reinette chatre [this message]
2009-10-02 20:43 ` [PATCH 03/13] iwlwifi: fix compile warning Reinette Chatre
2009-10-02 20:43 ` [PATCH 04/13] iwlwifi: reliable entering of critical temperature state Reinette Chatre
2009-10-02 20:43 ` [PATCH 05/13] iwlwifi: change valid EEPROM version for 1000 series Reinette Chatre
2009-10-02 20:44 ` [PATCH 06/13] iwlwifi: clear the translate table area Reinette Chatre
2009-10-02 20:44 ` [PATCH 07/13] iwlwifi: set default aggregation frame count limit to 31 Reinette Chatre
2009-10-02 20:44 ` [PATCH 08/13] iwlwifi: device tracing Reinette Chatre
2009-10-06 14:48   ` Stanislaw Gruszka
2009-10-06 14:59     ` Johannes Berg
2009-10-02 20:44 ` [PATCH 09/13] iwlwifi: LED cleanup Reinette Chatre
2009-10-02 20:44 ` [PATCH 10/13] iwlwifi/iwl3945 : unify apm stop operation Reinette Chatre
2009-10-02 20:44 ` [PATCH 11/13] iwlwifi: replace iwl_poll_direct_bit with iwl_poll_bit for CSR access Reinette Chatre
2009-10-02 20:44 ` [PATCH 12/13] iwlwifi: validate the signature for EEPROM and OTP Reinette Chatre
2009-10-02 20:44 ` [PATCH 13/13] iwlagn: fix compile warning in iwl5000_gain_computation Reinette Chatre

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=1254517177.26521.3503.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=wey-yi.w.guy@intel.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