Project

General

Profile

Actions

KernelBuild » History » Revision 9

« Previous | Revision 9/41 (diff) | Next »
Denis 'GNUtoo' Carikli, 02/03/2016 05:16 PM


KernelBuild

Use case

Building a kernel aside Replicant, is faster to setup and faster to build since you need to fetch and use the huge Android build system.

Users wanting to add a driver to their kernel, or developers that want to work on kernel related areas can do that to speed up the development process, however if the changes are integrated back into Replicant, they will automatically be built by the Android build system, when building images.

Dependencies

Since you are not compiling any userspace applications, you don't need the Android build system. The Linux Kenrel, and Bootloaders such as uboot can be built without the Android build system.

The Trisquel ARM version of gcc seem to work well.

If you use distributions such as Parabola, this will probably not work because the arm-none-eabi-gcc is too recent for many devices kernels.

To workaround that you can install Trisquel in a container.
This way it will have very few CPU and memory overhead compared to a virtual machine.
It will also save disk space since you can just store the Trisquel rootfs in any directory.

Example under Trisquel

First download the following example image and its signatures:

As usual, verify the signature:

$ gpg --import 4A80EB23.asc
$ gpg --verify replicant-4.2-crespo.zip.asc

It should then say something like:
$ gpg --verify replicant-4.2-crespo.zip.asc 
gpg: assuming signed data in 'replicant-4.2-crespo.zip'
gpg: Signature made Tue 01 Sep 2015 01:31:47 PM CEST using RSA key ID 4A80EB23
gpg: Good signature from "Replicant project release key <contact@replicant.us>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: E776 092B 052A DC91 FDD1  FD80 16D1 FEEE 4A80 EB23

Then unpack the zip file:

$ mkdir replicant-4.2-crespo && cd replicant-4.2-crespo && unzip ../replicant-4.2-crespo.zip

That should have extracted a boot.img. We then should not forget to look at what format the boot.img is in:
$ file boot.img
boot.img: Android bootimg, kernel (0x30008000), ramdisk (0x31000000), page size: 4096, cmdline (console=ttyFIQ0 no_console_suspend)

Here it says it's an "Android bootimg", so we need the following tools:
  • mkbootimg
  • unbootimg
$ git clone https://git.replicant.us/replicant/kernel_samsung_crespo.git

Updated by Denis 'GNUtoo' Carikli almost 9 years ago · 9 revisions

Also available in: PDF HTML TXT