Return-path: Received: from mail-ew0-f21.google.com ([209.85.219.21]:51412 "EHLO mail-ew0-f21.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751955AbZBDPR3 (ORCPT ); Wed, 4 Feb 2009 10:17:29 -0500 Received: by ewy14 with SMTP id 14so3410518ewy.13 for ; Wed, 04 Feb 2009 07:17:26 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 4 Feb 2009 15:17:26 +0000 Message-ID: <3ace41890902040717l7174fc0xc4589f17ea283e9c@mail.gmail.com> (sfid-20090204_161733_871459_EB1B0420) Subject: Re: zd1211rw NEW RF Type From: Hin-Tak Leung To: Ismael Ojeda Perez Cc: linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Feb 4, 2009 at 10:43 AM, Ismael Ojeda Perez wrote: > Hi, huston we have a problem > I have purchased a tp-link usb wireless device > model : tl-wn422g > i cant work with it because it says there is a new RF type > here its what dmesg shows > [ 526.984508] zd1211rw 7-2:1.0: RF MAXIM_NEW_RF 0x8 is not supported You probably don't hang out in the right place... two people on the sourceforge zd1211 mailing list recently reported that MAXIM_NEW_RF=0x08 is just the same as UW2453_RF=0x09 ; and one of them has a wn422g and the other wn322g (I just went back the mailing list archive and checked), so it is likely the same change would work for you: in drivers/net/wireless/zd1211rw/zd_rf.c, line 89, you see: -------------------- case UW2453_RF: r = zd_rf_init_uw2453(rf); break; --------------------- Just put an extra line case MAXIM_NEW_RF: either immediately before or immediately after the case UW2453_RF: line. If it reports success for you, maybe we'll consider putting this in properly... I am not the maintainer for that part, so it is likely we'll need advice/approval from somebody else for this change to go into the kernel.