That doesn't work. If I load the adb gadget driver for usb to work then I see "enabling adb" and "adb_open" prints on the console as adb is started from init.rc and 'adb connect' does not work but adb over usb works fine. Running 'netstat -a' shows no port, 5555 or otherwise, open for listening. If I don't load the adb gadget driver I don't see the adb console prints at startup and 5555 is open for listening and adb over ethernet works fine.
On Jun 30, 12:17 pm, sws-vinpa <[email protected]> wrote: > #adb shell > > Should connect via USB to the attached device. > > #adb connect <host>:<port> > > Will connect via Ethernet to the device at the specified <host> and > <port>, where <port>, in most cases, is 5555. > > sws-vinpa. > > On Jun 29, 2:34 pm, tracheur <[email protected]> wrote: > > > > > Is there a mechanism for dynamically switching the adb transport > > between usb and ethernet? We are using rowboat with a 2.6.32 kernel > > where the adb gadget driver build has been changed to not allow > > building as a module. In 2.6.29 we have a custom mechanism to decide > > to insmod f_android.ko when we want to use adb over usb. With 2.6.32 > > so far the adb over usb gadget is built-in to the kernel and I have to > > change the kernel build to switch between the two adb transports. > > > The Kconfig help for the android gadget says "The Android gadget > > driver supports multiple USB functions. The functions can be > > configured via a board file and may be enabled and disabled > > dynamically." What mechanism is used to do this enable/disable > > dynamically? -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
