ADB for mainline kernels (usefull for the GTA04).

Dr. H. Nikolaus Schaller hns at goldelico.com
Fri Nov 22 07:29:46 UTC 2013


Cool!

Am 21.11.2013 um 21:20 schrieb Denis 'GNUtoo' Carikli:

> Hi,
> 
> I found a post[1] from John Stultz documenting how to get ADB on a
> mainline kernel:
> 
> """
> For me the process was as follows:
> 
> 1) Make sure you have Jelly Bean 4.2 Android userland image.

Does this mean we need to upgrade Replicant to 4.2 (or 4.4?) first?

> Linaro provides a number of images for different boards here:
>    http://www.linaro.org/downloads/
> 
> 2) When building your kernel, make sure to configure in FunctionFS:
>    Device Drivers -> USB Support -> USB Gadget Support
>        -> USB Gadget Driver -> Function Filesystem
> 
> 3) Modify your boot parameters to set the vendor and product ids so adb
> on your host recognizes the device. g_ffs.idVendor=0x18d1
> g_ffs.idProduct=0x4e26
> 
> Alternatively this can also be done if you built the gadget driver as a
> module at load time: insmod g_ffs.ko idVendor=0x18d1 idProduct=0x4e26
> 
> 4) Now here I'm assuming you've got a serial port working. Boot your
> target device with your new kernel (and insmod the g_ffs driver if
> necessary), and setup the functionfs directory: # mkdir /dev/usb-ffs #
> mkdir /dev/usb-ffs/adb # mount -o uid=2000,gid=2000 -t functionfs
> adb /dev/usb-ffs/adb
> 
> 5) If everything is working, you can kill adbd and when it restarts it
> should find the functionfs mount and make use of it. # ps adbd
>    # kill <pid for adbd>
> 
> 6) On your host system, connect to the target using the adb program:
>    $ ./adb shell
>    root at android:/#
> 
>    Hooray there's your shell!
> """
> 
> Reference:
> [1] https://plus.google.com/111524780435806926688/posts/AaEccFjKNHE

We will keep an eye on this approach.

Thanks,
Nikolaus


More information about the Replicant mailing list