linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Walter <goldenstranger@yahoo.com>
To: Ivo van Doorn <ivdoorn@gmail.com>,
	linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [rt2x00] rt3070 fails to initialize with rt2800usb
Date: Sat, 17 Apr 2010 06:09:51 -0700 (PDT)	[thread overview]
Message-ID: <79834.90907.qm@web56804.mail.re3.yahoo.com> (raw)
In-Reply-To: <201004171445.13785.IvDoorn@gmail.com>

> From: Ivo van Doorn <ivdoorn@gmail.com>
> Subject: Re: [rt2x00] rt3070 fails to initialize with rt2800usb
> To: "Walter" <goldenstranger@yahoo.com>
> Cc: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
> Date: Saturday, April 17, 2010, 8:45 AM
> On Saturday 17 April 2010, Walter
> wrote:
> > I've been monitoring the community's work for the
> rt3070 chips and especially your recent success towards
> improving the driver.
> > 
> > I would like to share something with the rt2x00
> development team which may or may not be known.
> > 
> > The rt3070 card I own fails to initialize with the
> latest (working) compat-wireless release. When I plug the
> USB card, rt2800usb doesn't automatically load and when I
> manually modprobe the driver it does not recognize it as
> well.
> > 
> > Looking in to the rt2800usb.c file I found the
> 'problem'. The VIDs aren't properly set. Mine shows
> 148f:3070. Although a line is included in the "#ifdef
> CONFIG_RT2800USB_RT30XX", the module won't initialize the
> card.
> > 
> > I fixed the problem by adding my device here:
> > 
> >     /* Ralink */
> >     { USB_DEVICE(0x148f, 0x2770),
> USB_DEVICE_DATA(&rt2800usb_ops) },
> >     { USB_DEVICE(0x148f, 0x2870),
> USB_DEVICE_DATA(&rt2800usb_ops) },
> >     /* Samsung */ 
> > 
> > which now looks like:
> > 
> >     /* Ralink */
> >     { USB_DEVICE(0x148f, 0x2770),
> USB_DEVICE_DATA(&rt2800usb_ops) },
> >     { USB_DEVICE(0x148f, 0x2870),
> USB_DEVICE_DATA(&rt2800usb_ops) },
> >         {
> USB_DEVICE(0x148f, 0x3070),
> USB_DEVICE_DATA(&rt2800usb_ops) },
> >     /* Samsung */
> > 
> > This pertains to the rt3071 as well.
> 
> That USB ID is already known, did you compile the driver
> with support
> for CONFIG_RT2800USB_RT30XX enabled?
> 
> Ivo

Yes, compat-wireless ships with ''CONFIG_RT2800USB_RT30XX=y'' in config.mk, but the card's VIDs aren't shown in modinfo rt2800usb when compiled, thus the module doesn't recognize the card at all. The only workaround I rustled up is the above mentioned one. 


      

  reply	other threads:[~2010-04-17 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17 12:26 [rt2x00] rt3070 fails to initialize with rt2800usb Walter
2010-04-17 12:45 ` Ivo van Doorn
2010-04-17 13:09   ` Walter [this message]
2010-04-17 13:16     ` Ivo van Doorn
2010-04-19 16:13 Walter
2010-04-19 16:25 ` Ivo van Doorn
2010-04-21  8:17   ` Walter Goldens
2010-04-21 21:10     ` Gertjan van Wingerde
2010-04-22  9:05       ` Walter Goldens
2010-04-22 20:51         ` Gertjan van Wingerde
2010-04-23  8:46           ` Walter Goldens

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=79834.90907.qm@web56804.mail.re3.yahoo.com \
    --to=goldenstranger@yahoo.com \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --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).