On Tue, Jul 24, 2012 at 10:47 AM, Ming Lei <ming....@canonical.com> wrote: > > I remembered that Matthew objected caching firmware because he thought > it can't solve the isight camera problem after warm reset. But now, > this specific > problem can be solved easily by letting its driver defer probe.
I really think the isight thing is a totally different thing entirely. And quite frankly, that's just a BUG in the USB implementation. If the USB ID changes, it shouldn't be considered a "resume" thing at all, but a probe thing, and that should not be done in early resume - it should be done *after* the resume is done. The fact that USB confuses resuming existing devices and probing new ones is just an implementation issue, and is a bug. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/