Date: Thu, 25 Oct 2007 18:41:16 -0400 (EDT)
From: Parag Warudkar <kernel-stuff@comcast.net>
Reply-To: kernel-stuff@comcast.net
To: Ivo van Doorn <ivdoorn@gmail.com>
cc: rt2400-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}
In-Reply-To: <200710252315.49427.IvDoorn@gmail.com>
Message-ID: <alpine.DEB.0.99.0710251837040.9840@parag-desktop>
References: <alpine.DEB.0.99.0710241909250.18618@parag-desktop>
 <200710252315.49427.IvDoorn@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1028
Lines: 25


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.

Parag
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/