this bug has a solution it seems. From the info I see here it feels like a low hanging fruit.
Potential board specific issues can be followed up on in individual bugs afterwards. The sooner we land this fix in platform, the sooner we'll know. -- You received this bug notification because you are a member of Linaro Release Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/807230 Title: ADB requires new userland setup w/ linux-linaro-android 3.0-2011.07 Status in Linaro Android: Confirmed Bug description: ADB was reworked in the linux-3.0 kernel, removing the need for device specific platform drivers (similar to the change I did in 2.6.39). However, for adb to work over USB, some userland commands have to be issued at boot: Workaround: echo 0 > /sys/class/android_usb/android0/enable echo adb,acm > /sys/class/android_usb/android0/functions echo 2 > /sys/class/android_usb/android0/f_acm/instances echo 1 > /sys/class/android_usb/android0/enable (The above were found in the commit log here: https://review.source.android.com/#/c/23890/ ) After those commands are issued, I was able to get ADB functioning with the android-3.0 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-android/+bug/807230/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linaro-release Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-release More help : https://help.launchpad.net/ListHelp
