To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: rt2400-devel@lists.sourceforge.net, kernel-stuff@comcast.net,
       linux-kernel@vger.kernel.org
Subject: Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}
References: <alpine.DEB.0.99.0710241909250.18618@parag-desktop>
	<200710252315.49427.IvDoorn@gmail.com>
	<alpine.DEB.0.99.0710251837040.9840@parag-desktop>
	<200710262039.17027.IvDoorn@gmail.com>
From: Roland Dreier <rdreier@cisco.com>
Date: Fri, 26 Oct 2007 12:10:15 -0700
In-Reply-To: <200710262039.17027.IvDoorn@gmail.com> (Ivo van Doorn's message of "Fri, 26 Oct 2007 20:39:16 +0200")
Message-ID: <adamyu5zo88.fsf@cisco.com>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.20 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 852
Lines: 17

 > 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.

But a driver (especially a driver for something as hot-pluggable as a
USB device) shouldn't return -ENODEV just because no devices are
present at the moment.  It should just load successfully and wait for
a device to appear.

 - R.
-
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/