[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <adamyu5zo88.fsf@cisco.com>
Date: Fri, 26 Oct 2007 12:10:15 -0700
From: Roland Dreier <rdreier@...co.com>
To: Ivo van Doorn <ivdoorn@...il.com>
Cc: rt2400-devel@...ts.sourceforge.net, kernel-stuff@...cast.net,
linux-kernel@...r.kernel.org
Subject: Re: [Rt2400-devel] [PATCH] rt2500usb - Don't claim 050d:705{0/a}
> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists