> 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
