From: Aleksander Morgado <aleksander@xxxxxxxxxxxxx> Date: Wed, 27 Sep 2017 23:31:03 +0200 > I'm not sure if binding this logic to a specific vid:pid (1410:9030) > would be more appropriate here, or if it's ok to just bind > class/subclass/protocol (as in the activesync case). Let me know > what you think. I don't have enough USB Networking knowledge to make a decision here. Some things seem confusing. For example, if we should be matching USB_CLASS_MISC, subclass=4, protocol=1 for RNDIS over Ethernet, then we why aren't we also matching USB_CLASS_MISC, subclass=4, protocol=2 for RNDIS over wireless and instead are matching "Remote RNDIS" in the form of USB_CLASS_WIRELSS, subclass=1, protocol=3? I really don't understand any of this magic :-) So someone more knowledgable needs to review this. -- 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
