You need to make sure the kernel image has necessary options and drivers enabled.
In the kernel config file, you need to make sure: peripheral or otg mode is enabled. such as # CONFIG_USB_MUSB_PERIPHERAL=y or # CONFIG_USB_MUSB_OTG=y do not enable both, they would be conflicting options. gadget support needs to be enabled CONFIG_USB_GADGET=y and android usb adb gadget needs to built into kernel with 'y' or you can have it build as a module 'm' (insmod during init.rc) CONFIG_USB_ANDROID=y what do you mean by: > I have tried the No 1. approach. But it looks like > drivers/usb/gadget/f_adb.c > has several problems. Has it ever been tested on any device? To test, you can do lsusb on your host system to see if the android usb device shows up. I had to run sudo adb start-server for the device to show up, could not get udev rules working properly. If you want to get this device working with the windows drivers, you may need to modify inf file to add proper PID and VID and force driver install with "have disk" option. On Jul 17, 6:28 am, "Iram Shahzad" <[email protected]> wrote: > Hi > > I am trying to enable ADB through USB on my experimental device. > I have the following question in this regard. > > It seems there are two ways for this. > 1. support USB gadget driver > 2. support USB function driver > > Which one of the above is recommended? > > It seems that devphone uses the No 2. approach. > But the common kernel at > git://android.git.kernel.org/kernel/common.git > does not contain the function driver related codes. > > I have tried the No 1. approach. But it looks like > drivers/usb/gadget/f_adb.c > has several problems. Has it ever been tested on any device? > > Many thanks in advance > IS --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
