Hi
For this gadget driver what drivers would be required on the host end (MS Windows)? Can the windows machine recognize the USB device as a standard device, or is something else required?
MSFT has this thing against vendor neutral standards ... so the short answer is that something else is required.
This gadget driver talks two different protocols, both of which have had Linux support since 2.4.10 or earlier:
- The vendor-neutral "CDC Ethernet" protocol is preferred on all hardware that supports it.
- Or, a strict subset of cdc ethernet, which omits some non-essential stuff but uses the same frame encoding. Essentially any USB device (except low-speed stuff) can support this simple protocol.
Many cable modems talk CDC Ethernet (it's one of only two options in DOCSIS), and they work with Windows. There are commercial driver stacks for CDC Ethernet on Windows. So: connectivity is easily had; just it's not direct from MSFT.
What MSFT wants is a vendor-specific protocol called RNDIS. They publish some pretty lousy documentation; enough to see that it's gratuitously complex. But recent versions of Windows bundle RNDIS support, so it's what they tell hardware manufacturers to support.
The folk at Pengutronix were working on RNDIS modifications for the "ether.c" code, but last I heard it wasn't yet usable.
- Dave
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
