From: Pavel Roskin <proski@gnu.org>
To: Ivo Van Doorn <ivdoorn@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Amit Kucheria <amit.kucheria@canonical.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 11:11:39 -0400 [thread overview]
Message-ID: <1251990699.6521.12.camel@mj> (raw)
In-Reply-To: <a32f33a40909030718v494f8fech6ba3c854b5c84ef8@mail.gmail.com>
On Thu, 2009-09-03 at 16:18 +0200, Ivo Van Doorn wrote:
> On Thu, Sep 3, 2009 at 1:55 PM, John W. Linville<linville@tuxdriver.com> wrote:
> > On Thu, Sep 03, 2009 at 02:42:20PM +0300, Amit Kucheria 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>
> >
> > IIRC there are IDs that are used by different devices where rt73usb
> > covers one device and the rt2500usb covers another. Are you sure
> > this is not one of those?
>
> Yes, I believe this particular ID was already discussed some time ago
> on this list. This is one of the infamous duplicate IDs. (Fortunately not
> one of those infamous Linksys devices with 5 different chipsets for the
> same ID).
The famous Linksys devices can be distinguished by the textual PCMCIA
ID. In this case, there is no reliable way to distinguish the devices
without trying the drivers. I tried and could not find any difference
between "lsusb -v" output for the devices said to be supported by
rt2500usb and rt73usb.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2009-09-03 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 11:42 [PATCH] rt2x00: Get rid of duplicate usb id from rt2500usb Amit Kucheria
2009-09-03 11:54 ` Ivo Van Doorn
2009-09-03 12:27 ` Amit Kucheria
2009-09-03 13:27 ` Johannes Berg
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 [this message]
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=1251990699.6521.12.camel@mj \
--to=proski@gnu.org \
--cc=amit.kucheria@canonical.com \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).