From: Ivo van Doorn <ivdoorn@gmail.com>
To: rt2400-devel@lists.sourceforge.net, kernel-stuff@comcast.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}
Date: Fri, 26 Oct 2007 20:39:16 +0200 [thread overview]
Message-ID: <200710262039.17027.IvDoorn@gmail.com> (raw)
In-Reply-To: <alpine.DEB.0.99.0710251837040.9840@parag-desktop>
On Friday 26 October 2007, Parag Warudkar wrote:
>
> Hi Ivo
>
> On Thu, 25 Oct 2007, Ivo van Doorn wrote:
>
> > I awknowledge the problem, but the solution cannot be found in the USB ID's
> > listed in the driver. The bug is the manufacturer who changed chipset while
> > keeping the USB ID the same.
> > There are 2 possible ways around this: hacking the module loader so
> > it continues searching for a different driver when the first driver indicates
> > that it cannot control the device.
> > Or the easiest way, just blacklist rt2500usb if you are sure you need the rt73 driver.
>
> Thanks for the heads up - I think you have a good idea - there should be
> an interface between the loader and module to specify conditions like this.
>
> I will see if I can generate interest in that idea and hack up something
> along the lines of your suggestion.
Well it could be something quite simple, in the module loader it is looping
through all modules to look for a device with the correct USB/PCI ID.
Currently, after the first occurence it loads the module and doesn't continue,
it should perhaps be relatively easy that it checks if the driver returned -ENODEV
and continues looping to search for another driver.
Ivo
next prev parent reply other threads:[~2007-10-26 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 23:22 [PATCH] rt2500usb - Don't claim 050d:705{0/a} Parag Warudkar
2007-10-25 19:35 ` [Rt2400-devel] " Adam Baker
2007-10-25 22:33 ` Parag Warudkar
2007-10-25 21:15 ` Ivo van Doorn
2007-10-25 22:41 ` Parag Warudkar
2007-10-26 18:39 ` Ivo van Doorn [this message]
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=200710262039.17027.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--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 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.