All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Hin-Tak Leung <hintak.leung@gmail.com>
Cc: Ismael Ojeda Perez <iojedaperez@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: zd1211rw NEW RF Type
Date: Wed, 4 Feb 2009 10:18:54 -0500	[thread overview]
Message-ID: <20090204151854.GC3845@tuxdriver.com> (raw)
In-Reply-To: <3ace41890902040717l7174fc0xc4589f17ea283e9c@mail.gmail.com>

On Wed, Feb 04, 2009 at 03:17:26PM +0000, Hin-Tak Leung wrote:
> On Wed, Feb 4, 2009 at 10:43 AM, Ismael Ojeda Perez
> <iojedaperez@gmail.com> 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.

Or someone can send a patch with a report that it is working for them
and I'll just merge it... :-)

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-02-04 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a4c529250902040227g35a375fdu35c2360f0916dba6@mail.gmail.com>
2009-02-04 10:43 ` zd1211rw NEW RF Type Ismael Ojeda Perez
2009-02-04 14:47   ` John W. Linville
2009-02-04 15:17   ` Hin-Tak Leung
2009-02-04 15:18     ` John W. Linville [this message]
2009-02-04 15:50       ` Hin-Tak Leung
2009-02-04 16:15         ` John W. Linville
2009-02-04 19:32     ` Ismael Ojeda Perez
2009-02-04 19:43       ` Hin-Tak Leung
2009-02-04 19:47         ` Gábor Stefanik

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=20090204151854.GC3845@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=hintak.leung@gmail.com \
    --cc=iojedaperez@gmail.com \
    --cc=linux-wireless@vger.kernel.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.