Hello.
I have had kernel 2.6.5 successful running on lubbock. all usb-gadget related had kept sync with the latest one got from http://usb-gadget.bkbits.net:8080/gadget-2.6/, the windows driver had download from microsoft site, and using the linux.inf from the 2.6.6 kernel.
Sounds like it ought to be OK; I don't recall anything in other parts of the stack that would affect that.
I just made one change to pxa2xx_udc.c add #undef CONFIG_USB_PXA2XX_SMALL to avoid the message from appearing:"can't run RNDIS on 'pxa2xx_udc' ", After connecting with the windows host, pc
There's also
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=108506544319679&w=2
shows a non-working ethernet card. On lubbock side there is a usb0 net card.ifconfig show the card never shows RUNNING(after you config it an ip address).
The link needs to be running, but that bit gets set when the MSFT host activates the link. Which it won't do if you've not configured it right. Each different release of MS-Windows seems to have different quirks in configuration, and (I think) in how its RNDIS support works.
I know little about rndis protocol. I don't know where to start.Could anybody give a checklist to make it works?
One thing to do is make sure it talks to a Linux 2.6 host first; that'll help make sure the code is basically running on Lubbock. Then see about the RNDIS/Windows side of things.
The RNDIS code might well have some PXA-specific issues, but it's behaved on other controllers.
- Dave
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
