Am Dienstag, 3. Januar 2012, 14:20:53 schrieb Alan Cox: > > That said, I guess there are more complicated / difficult pieces of > > hardware that might not do that. Is that the case here? Can we detect > > that the firmware needs reloading and have the primary driver "yield" to > > the firmware driver? > > That doesn't really make any sense in the way USB works. > > However if you've got a system to load and pin firmware on suspend and > flush it post resume then you don't actually need special 'firmware' > drivers just a slightly fancier lib/firmware that refcounts and handles > load on suspend/delayed flush. How so? You still need to get the firmware to the device before you unfreeze user space to get a benefit from this. Having it in RAM is only half the deal. Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
