Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> writes: > On Tue, 29 May 2012, Bjørn Mork wrote: > >> We need to make sure that the USB serial driver we found >> matches the USB driver whose probe we are currently >> executing. Otherwise we will end up with USB serial >> devices bound to the correct serila driver but wrong >> USB driver. >> >> This is a real problem for the generic USB serial driver >> because it matches any device. > > Do you have any idea why this hasn't shown up before? It's not at all > clear why the recent changes to the usb-serial core should cause this > to start happening. No, that is not clear to me either. The probe is not changed, so there shouldn't be anything preventing this from happening before the new registration model either. But I only noticed it after starting running the new code. I assume it must have something to do with how the drivers are registered, since that's the only new part, but I could be entirely wrong. Why would the old code only run the "correct" probe anyway? Does the new registration somehow change the probing order? Bjørn -- 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
