Hi Dave
I've upgraded to the latest 2.4-gadget bitkeeper tree. CDC ethernet still works and RNDIS still doesn't. Here are my updated messages.
~ # modprobe g_ether Using /lib/modules/2.4.25-vrs2.rndis/kernel/drivers/usb/gadget/g_ether.o usb0: Ethernet Gadget, version: St Patrick's Day 2004 usb0: using n9604_udc, OUT ep2out IN ep1in STATUS ep3in usb0: MAC 66:69:9c:68:61:bf usb0: CDC host enet AA3CFD7EDE3C usb0: RNDIS ready ~ # usb0: full speed config #2: Ethernet Gadget, using RNDIS
Also the RNDIS never asks to queue any usb requests on endpoints 1 or 2. I never see windows trying to communicate with endpoint 2, but there are a lot of NAKs to endpoint 1.
Are you sure control-OUT works for your n9604_udc driver?
You should be able to use "gadget zero" on that hardware with "usbtest" from a Linux 2.6 host ... one testcase gives a pretty good workout to ep0out, run it all day:
testusb -a -t 14 -c 15000 -s 256 -v 1
If you turned on RNDIS debug, you should have gotten a wad of RNDIS messages, all delivered using ep0out. But your output showed none of them...
- Dave
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
