Hello all, I'm new to the list and I wonder if I could get some help/orientation with regards to the state of g_ether/RNDIS? We have been unable to get ethernet-over-USB using RNDIS to a Windows XP host. At first I suspected it was do to the RNDIS .inf "script" on the Windows side, but after much futzing with several scripts and registry entries we now believe a problem exists in either the platform driver or the gadget RNDIS support. Searching the linux-usb-devel list for RNDIS issues, I see a discussion from 2007: On Nov 12 2007, David Brownell wrote: However, that particular version doesn't actually connect more than one function into a configuration. The reason is that it still needs a bit of API restructure ... it should combine function drivers into *configurations* which in turn combine to make gadget drivers. Instead, that code use a slightly broken model, combining functions into configurations. That works OK until you try to handle multi-configuration gadget drivers like g_ether (with RNDIS enabled). On Dec 3rd 2007, David Brownell wrote: I've not updated them recently, other than making sure the existing patches don't break on various platforms (and the trivial include file path change I already mentioned). In particular, fixing that one known-broken issue hasn't yet been done. (There need to be three components: function, configuration, device. "Configuration" is not currently present, which is why updating Gadget Zero and Ether/RNDIS has been problematic.) If I understand this thread correctly, the patch(es) are required only for multi-function and/or dynamic loading? We are not trying to get a multi-function device working at this point, simply a static configured g_ether/RNDIS. Should the existing kernel code work without patches? Background: we're using a 2.6.31-based kernel but I've tried many of the USB gadget/RNDIS related diffs up to 2.6.35 to no avail. Advanced thanks, Marc -- 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
