From: Parag Warudkar <kernel-stuff@comcast.net>
To: Adam Baker <linux@baker-net.org.uk>
Cc: rt2400-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}
Date: Thu, 25 Oct 2007 18:33:54 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.0.99.0710251826310.9840@parag-desktop> (raw)
In-Reply-To: <200710252035.20546.linux@baker-net.org.uk>
On Thu, 25 Oct 2007, Adam Baker wrote:
>
> Unfortunately Belkin have sold both RT73 and RT2500 devices with
> that USB ID. You don't say what distro you are runing or what version
> of RT2x00 it ships with but last time I checked with the git version of
> rt2x00 it tried to load both drivers but the rt2500 driver noticed it was the
> wrong hardware and shut down.
Like I said this did not work with 2.6.24-rc1 (latest git). My distro
(Ubuntu 7.10) kernel 2.6.22-10 also has the same behavior.
> There are a few such devices but they are all cases where there are reliable
> reports of manufacturers shipping both device types with one USB ID. There
> are some cases where the alternate chipset with the same USB ID isn't even a
> ralink device but there isn't much we can do about those.
>
Ok, I failed to imagine the hardware makers' stupidity :) - In the case
that you mentioned I agree that there is little that can be done based on
device IDs. I'll check out subsequent releases to see if it gets fixed
based on hardware characteristics (rt2500usb unloading and requesting the
right one in my case for example).
Thanks
Parag
next prev parent reply other threads:[~2007-10-25 22:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 23:22 Parag Warudkar
2007-10-25 19:35 ` [Rt2400-devel] " Adam Baker
2007-10-25 22:33 ` Parag Warudkar [this message]
2007-10-25 21:15 ` Ivo van Doorn
2007-10-25 22:41 ` Parag Warudkar
2007-10-26 18:39 ` Ivo van Doorn
2007-10-26 19:10 ` Roland Dreier
2007-10-26 19:58 ` Adam Baker
2007-10-26 20:05 ` Roland Dreier
2007-10-26 21:34 ` Ivo van Doorn
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=alpine.DEB.0.99.0710251826310.9840@parag-desktop \
--to=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@baker-net.org.uk \
--cc=rt2400-devel@lists.sourceforge.net \
/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®