Andy : OMAP5 uses DWC3, while OMAP4 MUSB. I see no problem with both stacks built into the kernel. Only the one which has the relevant platform device populated (based upon which platform is it), would spring to life. The other shouldn't make any difference. BTW, I couldn't find Panda-omap5 even initializing USB gadget side.
Vishal : The following changes to your omap4plus_defconfig above, should get it working. 167c167 < CONFIG_USB_DWC3=m --- > CONFIG_USB_DWC3=y 170,171c170,171 < CONFIG_USB_MUSB_HDRC=m < CONFIG_USB_MUSB_OMAP2PLUS=m --- > CONFIG_USB_MUSB_HDRC=y > CONFIG_USB_MUSB_OMAP2PLUS=y 176,178c176 < CONFIG_USB_GADGET_MUSB_HDRC=m < CONFIG_USB_ZERO=m < CONFIG_USB_MASS_STORAGE=m --- > CONFIG_USB_GADGET_MUSB_HDRC=y -- You received this bug notification because you are a member of TI OMAP Developers, which is subscribed to linaro-landing-team-ti. https://bugs.launchpad.net/bugs/1017438 Title: Panda: adb over usb broken on panda-ics-gcc47-tilt-tracking- blob/#build=101" Status in Linaro Android: New Status in Linaro Texas Instruments Landing Team: New Bug description: Description: -------------- adb over USB broken on : https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob/#build=101 (Kernel version: 3.4) Steps: ------- 1. Bootup Android from sd card for above build 2. Connect USB cable after device boots up 3. type <path_to_android_sdk/platform-tools>adb devices -on host machine. Issue: No device listed. I do not see USB detection messages on serial console when USB cable is connected to device. To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-android/+bug/1017438/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~tiomap-dev Post to : tiomap-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~tiomap-dev More help : https://help.launchpad.net/ListHelp
