2010/7/22 Michał Nazarewicz <m.nazarewicz@xxxxxxxxxxx>: >> Actually, Windows' enumeration of composite devices is quite broken >> (ok, maybe "not ideal") and it will in fact only select a >> configuration if a composite device has a single config. If it has >> multiple configs Windows punts and makes you install an INF to force >> it to select a config (using a registry setting of course...ugh!). >> I've been trying to find a way to work around both the Linux RNDIS >> issue and various Windows issues from the device side since I have >> control of the device firmware. At this point I'm pretty much >> convinced it's not possible to make both Linux and Windows happy at >> the same time. I'd love to be wrong about that, though. > > Unfortunately my experiences are similar... I think it should be fairly > easy to create an INF that attaches usb composite driver to the gadget > even if it has more then one configuration but I never managed to do > that. > I am not so sure if the fake USB composite device method works or not. http://www.argyllcms.com/fcompexample.inf I have tried to use the above inf file to make any single interface device to enumerate as a USB composite device and thus attach the usb composite device driver to it. libusb-win32 filter driver does not work with WinUSB based USB device (or UMDF based device). However, with the above INF file, the device can fake as a USB composite device and the filter driver seems to work with it. Maybe similar trick can work for your use case. -- Xiaofan http://sourceforge.net/projects/libusb-win32/ -- 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
