Thanks for your reply, Brian.
Before I saw this reply, I ended up backporting the low-level gadget driver to 2.6.25 and managed to get RNDIS driver working. Somehow regular cdc_ether is not working. Strange. Have not spent too much to look into any further. If anybody knows why, let me know. Here is the hack/patch for the backported gadeget driver. http://junsun.net/linux/android-dream/090121-android-usb-gadget-rndis.patch BTW, from what you were saying, it seems the usb functions are composite-able. That is interesting. Cheers. Jun On Tue, Jan 20, 2009 at 11:17:27PM -0800, Brian Swetland wrote: > > > You're going to have to configure the function to be included in the usb > composite device (look in board-trout.c), and probably will have to > modify the VID/PID to match one your desktop linux kernel associates > with the "simple" ethernet profile. > > Also, I've found that having other interfaces (like adb) present tends > to confuse the host driver (which assumes that *all* interfaces are > ethernet interfaces). > > I have successfully used this driver with several different desktop > linux systems, but things are not rigged up so simply including the > driver in the build gets it all going. > > Brian > > [Jun Sun <[email protected]>] > > > > Does this feature work as it suggests? > > > > I compiled a 2.6.25 kernel with this feature enable. Then I > > plugged into a fedora 9 host. Nothing happened on the host > > side. No usb0 detected. > > > > Anything I need to do here? > > > > Further, I can do "ifconfig usb0 xxxx.xxx.xxx.xxx up" on the G1 > > device. However, when I do "ping ...." over the interface, the > > phone looks dead. adb shell connection is disconnected. > > > > Any hints? > > > > Jun > > > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
