On 21.06.22 12:21, Hector Martin wrote: > The Anker PowerExpand USB-C to Gigabit Ethernet adapter uses this > chipset, but exposes CDC Ethernet configurations as well as the > vendor specific one. This driver ends up binding first to both CDC > interfaces, tries to instantiate two Ethernet interfaces talking to > the same device, and the result is a nice fireworks show. Could you explicitly state here that the root cause is that the driver for the vendor specific mode binds to the device based only on vendor:product ID, thus taking interfaces that only the class driver can handle properly? This log reads like the basic issue is that it binds to two interfaces. The patch itself is fine. Regards Oliver
