From: Gertjan van Wingerde <gwingerde@gmail.com>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: John Linville <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>,
Gabor Juhos <juhosg@openwrt.org>
Subject: Re: [PATCH 1/3] rt2x00: rt2800: increase EEPROM_SIZE to 512 bytes
Date: Mon, 24 Jun 2013 19:32:07 +0200 [thread overview]
Message-ID: <2DDF15FE-CA30-4683-ABFE-63204952F561@gmail.com> (raw)
In-Reply-To: <1371915734-13966-2-git-send-email-juhosg@openwrt.org>
Sent from my iPad
On 22 jun. 2013, at 17:42, Gabor Juhos <juhosg@openwrt.org> wrote:
> Ralink 3T chipsets are using a different EEPROM
> layout than the others. The EEPROM on these devices
> contain more data than the others which does not fit
> into 272 byte which the rt2800 driver actually uses.
>
> The Ralink reference driver defines EEPROM_SIZE to
> 512/1024 bytes for PCI/USB devices respectively.
>
> Increase the EEPROM_SIZE constant to 512 bytes, in
> order to make room for EEPROM data of 3T devices.
>
> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>
> ---
> drivers/net/wireless/rt2x00/rt2800.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2800.h b/drivers/net/wireless/rt2x00/rt2800.h
> index fe43d01..d78c495 100644
> --- a/drivers/net/wireless/rt2x00/rt2800.h
> +++ b/drivers/net/wireless/rt2x00/rt2800.h
> @@ -100,7 +100,7 @@
> #define CSR_REG_BASE 0x1000
> #define CSR_REG_SIZE 0x0800
> #define EEPROM_BASE 0x0000
> -#define EEPROM_SIZE 0x0110
> +#define EEPROM_SIZE 0x0200
> #define BBP_BASE 0x0000
> #define BBP_SIZE 0x00ff
> #define RF_BASE 0x0004
> --
> 1.7.10
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-06-24 17:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 15:42 [PATCH 0/3] rt2x00: rt2800: prepare for three-chain device support Gabor Juhos
2013-06-22 15:42 ` [PATCH 1/3] rt2x00: rt2800: increase EEPROM_SIZE to 512 bytes Gabor Juhos
2013-06-24 13:01 ` Helmut Schaa
2013-06-24 17:32 ` Gertjan van Wingerde [this message]
2013-06-22 15:42 ` [PATCH 2/3] rt2x00: rt2800lib: turn on secondary PAs/LNAs for 3T/3R devices Gabor Juhos
2013-06-24 13:00 ` Helmut Schaa
2013-06-24 19:00 ` Gabor Juhos
2013-06-24 17:33 ` Gertjan van Wingerde
2013-06-22 15:42 ` [PATCH 3/3] rt2x00: rt2800lib: turn on tertiary " Gabor Juhos
2013-06-24 13:02 ` Helmut Schaa
2013-06-24 17:42 ` Gertjan van Wingerde
2013-06-24 19:17 ` Gabor Juhos
2013-06-24 16:00 ` [rt2x00-users] [PATCH 0/3] rt2x00: rt2800: prepare for three-chain device support Stanislaw Gruszka
2013-06-24 19:09 ` Gabor Juhos
2013-06-25 19:18 ` Stanislaw Gruszka
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=2DDF15FE-CA30-4683-ABFE-63204952F561@gmail.com \
--to=gwingerde@gmail.com \
--cc=juhosg@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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).