From: Johannes Berg <johannes@sipsolutions.net>
To: Amit Kucheria <amit.kucheria@canonical.com>
Cc: Ivo Van Doorn <ivdoorn@gmail.com>,
List Linux Kernel <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rt2x00: Get rid of duplicate usb id from rt2500usb
Date: Thu, 03 Sep 2009 15:27:35 +0200 [thread overview]
Message-ID: <1251984455.3336.24.camel@johannes.local> (raw)
In-Reply-To: <20090903122727.GA4465@matterhorn.verdurent.com>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
On Thu, 2009-09-03 at 15:27 +0300, Amit Kucheria wrote:
> On 09 Sep 03, Ivo Van Doorn wrote:
> > > USB_DEVICE(0x148f, 0x2573) is served by the rt73usb driver where it is already
> > > defined. Remove it from rt2500usb.
> > >
> > > Signed-off-by: Amit Kucheria <amit.kucheria@canonical.com>
> > > Cc: Ivo van Doorn <IvDoorn@gmail.com>
> >
> > NACK
> >
> > Users have reported that this is a valid rt2500usb ID. You can thank the
> > manufacturer of the dongle to produce dongles with the same USB ID but
> > with different chipsets.
> >
> > Ivo
>
> Interesting. On my laptop, without this patch both the drivers are loaded
> (lsmod), rt2500usb aborts without allocating a device successfully but I am
> unable to associate to the AP.
Sounds like the detection logic is somehow messing with the device, or
rt2500usb isn't actually freeing the device for rt73usb to bind?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-09-03 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 11:42 Amit Kucheria
2009-09-03 11:54 ` Ivo Van Doorn
2009-09-03 12:27 ` Amit Kucheria
2009-09-03 13:27 ` Johannes Berg [this message]
2009-09-03 14:19 ` Ivo Van Doorn
2009-09-03 11:55 ` John W. Linville
2009-09-03 14:18 ` Ivo Van Doorn
2009-09-03 15:11 ` Pavel Roskin
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=1251984455.3336.24.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=amit.kucheria@canonical.com \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®