Messages in this thread | | | From | Oliver Neukum <> | Subject | Re: Load hid.o module synchronously? | Date | Fri, 7 May 2004 19:50:30 +0200 |
| |
Am Freitag, 7. Mai 2004 18:19 schrieb Stefan Smietanowski: > Hi Patrick. > > >>The set of devices connected to the machine is not static. Waiting > >>until all hardware is ready is very hard to even define. > > > > It is very easy to define for 99.999% of all keyboards, which start > > off connected and stay connected. > > > > This should be simple. I want to load a driver at boot time and wait > > until it either binds to something or fails to do so. If the user is > > But that means that the driver must include some sort of arbitrary > timelimit. Why push that from userspace to the driver?
No, upon module load the device tree could be locked and the module insertion could wait for all matching devices in the tree to be probed. It definitely can be done and that solution cannot be achieved from userspace because exporting such locks would be a disaster.
However, it is probably not wise to provide for this special case. It would probably be best to provide a generic probe method for devices, which could run synchronously.
Regards Oliver - 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/
| |