On Mon, 02 Jan 2012 20:41:00 +0000 Jack Stone <jwjstone@xxxxxxxxxxx> wrote: > On 02/01/12 16:54, Alan Stern wrote: > > What Oliver and I have been discussing is delaying the probe call until > > after resume is finished, when userspace is back up and everything is > > operating normally again. It would be more awkward than the current > > code, but it definitely can be done. > > What about the case where the firmware that needs to be loaded is on the > USB device that needs the firmware. This can be resolved at boot using > an initrd but at resume time we don't have that. There is a very simple answer to such conflicts - don't do it. If you have firmware you need to reload to get stuff back which might form a dependancy chain then cache it for the lifetime of the device being in use. You will never sanely compute that dependancy chain IMHO (although by all means prove me wrong!) given it might involve things like firmware over raid over iscsi over nfs over a usb wireless link... We have the same theoretical problem btw with kernel modules. if they are on a usb device you need the driver loaded and kept loaded while the driver is in use - we just happen to do that right anyway so it works fine. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
