All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: ptb@cs.bham.ac.uk
Cc: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: dead RT2501USB ?
Date: Tue, 07 Jul 2009 11:49:43 -0400	[thread overview]
Message-ID: <1246981783.23943.10.camel@mj> (raw)
In-Reply-To: <200907071526.n67FQICE002753@barney.it.uc3m.es>

On Tue, 2009-07-07 at 17:26 +0200, Peter Breuer wrote:
> Firstly: lsusb output:
> 
>   Bus 005 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter
...
> Loaading the  rt73usb module produces this stack (after a fair old delay
> for the modprobe to come back)
...
> So it thinks it's not the right chipset. Perhaps I should add an
> identification line somewhere in the code?

Try rt2500usb instead of rt73usb.  Both drivers support 148f:2573.  As
far as I know, it's impossible to find out which driver would work with
a particular device from USB ID alone.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2009-07-07 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 15:26 dead RT2501USB ? Peter Breuer
2009-07-07 15:49 ` Pavel Roskin [this message]
2009-07-07 16:07 ` Luis Correia

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=1246981783.23943.10.camel@mj \
    --to=proski@gnu.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ptb@cs.bham.ac.uk \
    --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 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.