On Wed, 15 Mar 2006, Marc Singer wrote: > On Wed, Mar 15, 2006 at 05:47:05PM -0500, Alan Stern wrote: > > On Wed, 15 Mar 2006, Marc Singer wrote: > > > > > > > Isn't that the responsibility of the gadget itself and not the UDC? > > > > > > > > Yes, it is. What gadget driver were you using for your test? > > > > > > ether.c > > > > That's your problem. You should be using g_zero. Then test 14 would work > > as expected. > > Now, you are confused. I *was* testing with gadget zero. Now I'm > using the ether driver to see if I can bring-up the link. Gadget zero > wouldn't pass test 14, but it certainly is possible that the reason it > failed is the same reason that ether isn't sending an interface > descriptor for configuration 1.
No, those two drivers are very different. Gadget zero passes test 14 on my system. If it doesn't on yours then something is wrong. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
