> IMO, the driver probing path is allowed to sleep, so looks request firmware > should be allowed inside .probe().
I'm not convinced about that. It can sleep but its holding various locks in most cases, and it looks like that can end up in a complete heap. By all means *request* the firmware asynchronously in the probe, but there needs to be a seperate method somewhere after the probe to finish the job once the firmware appears. Alan _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
