From: Gertjan van Wingerde <gwingerde@gmail.com>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org,
Ivo van Doorn <IvDoorn@gmail.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: [PATCH] rt2x00: Properly detect Ralink RT3070 devices.
Date: Mon, 09 Nov 2009 23:11:36 +0100 [thread overview]
Message-ID: <4AF89398.6060305@gmail.com> (raw)
In-Reply-To: <69e28c910911091404i18e4e4b8ydd9d334bc833de3b@mail.gmail.com>
On 11/09/09 23:04, Gábor Stefanik wrote:
> On Mon, Nov 9, 2009 at 10:59 PM, Gertjan van Wingerde
> <gwingerde@gmail.com> wrote:
>> Allow rt2800usb to properly detect RT307X based devices, and set the appropriate chipset values.
>>
>> Signed-off-by: Gertjan van Wingede <gwingerde@gmail.com>
>> ---
>> drivers/net/wireless/rt2x00/rt2800usb.c | 21 ++++++++++++++-------
>> drivers/net/wireless/rt2x00/rt2x00.h | 1 +
>> 2 files changed, 15 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/net/wireless/rt2x00/rt2800usb.c b/drivers/net/wireless/rt2x00/rt2800usb.c
>> index d22ab64..bd2f6e6 100644
>> --- a/drivers/net/wireless/rt2x00/rt2800usb.c
>> +++ b/drivers/net/wireless/rt2x00/rt2800usb.c
>> @@ -790,16 +790,19 @@ static int rt2800usb_init_eeprom(struct rt2x00_dev *rt2x00dev)
>> */
>> value = rt2x00_get_field16(eeprom, EEPROM_ANTENNA_RF_TYPE);
>> rt2800_register_read(rt2x00dev, MAC_CSR0, ®);
>> - rt2x00_set_chip(rt2x00dev, RT2870, value, reg);
>> + rt2x00_set_chip_rf(rt2x00dev, value, reg);
>>
>> /*
>> * The check for rt2860 is not a typo, some rt2870 hardware
>> * identifies itself as rt2860 in the CSR register.
>> */
>> - if (!rt2x00_check_rev(&rt2x00dev->chip, 0xfff00000, 0x28600000) &&
>> - !rt2x00_check_rev(&rt2x00dev->chip, 0xfff00000, 0x28700000) &&
>> - !rt2x00_check_rev(&rt2x00dev->chip, 0xfff00000, 0x28800000) &&
>> - !rt2x00_check_rev(&rt2x00dev->chip, 0xffff0000, 0x30700000)) {
>> + if (rt2x00_check_rev(&rt2x00dev->chip, 0xfff00000, 0x28600000) ||
>> + rt2x00_check_rev(&rt2x00dev->chip, 0xfff00000, 0x28700000) ||
>> + rt2x00_check_rev(&rt2x00dev->chip, 0xfff00000, 0x28800000)) {
>> + rt2x00_set_chip_rt(rt2x00dev, RT3070);
>
> Typo?
>
Doh. You're right. And I did even test this on a RT2870 device :-(
Thanks for noticing this.
I'll resend the patch with this fixed.
But first, I need to find a brown paper bag somewhere. ;-)
---
Gertjan.
prev parent reply other threads:[~2009-11-09 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 21:59 [PATCH] rt2x00: Properly detect Ralink RT3070 devices Gertjan van Wingerde
2009-11-09 22:04 ` Gábor Stefanik
2009-11-09 22:11 ` Gertjan van Wingerde [this message]
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=4AF89398.6060305@gmail.com \
--to=gwingerde@gmail.com \
--cc=IvDoorn@gmail.com \
--cc=bzolnier@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.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).