ROM Android: Compile Kernel untuk ROM Android - Revision history

Onnowpurbo: /* Memperoleh file config */

2015-01-01T07:57:03Z

Memperoleh file config

Onnowpurbo: /* Referensi */

2014-12-30T22:24:04Z

Referensi

Onnowpurbo: /* HINDARI: Building hanya kernel dari kernel source */

2014-11-25T05:09:46Z

HINDARI: Building hanya kernel dari kernel source

Onnowpurbo: /* TO AVOID: Building only the kernel from the kernel source */

2014-11-25T04:34:33Z

TO AVOID: Building only the kernel from the kernel source

Onnowpurbo: /* Re-build */

2014-11-25T04:25:07Z

Re-build

Onnowpurbo: /* Re-build */

2014-11-23T22:58:30Z

Re-build

Onnowpurbo: /* Ubah konfigurasi kernel */

2014-11-23T22:35:58Z

Ubah konfigurasi kernel

Onnowpurbo: /* TO AVOID: Building only the kernel from the kernel source */

2014-11-23T22:30:02Z

TO AVOID: Building only the kernel from the kernel source

Onnowpurbo: /* Re-build */

2014-11-23T22:25:49Z

Re-build

Onnowpurbo at 01:12, 21 November 2014

2014-11-21T01:12:31Z

@@ Line 181: / Line 181: @@
 * Memperoleh dari kernel source code.
-I will show you both the ways of doing it so.
+Caranya adalah sebagai berikut:
-) Getting config file from your phone with the help of ADB:
+===Memperoleh .config melalui adb===
-    First of all connect your phone to your computer.
+* sambungkan komputer ke telepon
-    Then type the mentioned code below:
+* tulis
-  adb pull proc/config.gz ~/home/crossfire77/kernel
+ cd ~/tempat-file-data-android-anda
-This will pull your existing config file from your phone and put it in kernel folder. Now extract it,
+* extract menggunakan perintah
   zcat config.gz > .config
-So we have directly config for building our kernel.
+Ya, kita memperoleh .config yang dibutuhkan untuk membuat kernel dari android kita.
 NOTE:  Many times users’ faces errors while connecting phone with computer via ADB, it’s mostly issue of a permission. There is two solutions for it.
@@ Line 351: / Line 356: @@
   make -j# ARCH=arm
 Note:The # means the number of CPU cores +1. For example my device has a quad core CPU and I will type
 Code:
@@ Line 369: / Line 375: @@
 Got the zip file go to the System folder and replace it's bcm4329.ko with your bcm4329.ko
 You are ready all you need to do is flash it.
 ==Mengapa CM menginginkan kernel built bersama dengan Android?==

← Older revision		Revision as of 22:24, 30 December 2014
Line 583:		Line 583:


		+
		+
		+
		+
		+	As alluded to above, all I really wanted to do was tweak the kernel config to enable CONFIG_FTRACE. The way I did that was to enter the directory the kernel source is in: ~/android/system/kernel/samsung/smdk4412, then copied the default config for my phone (arch/arm/configs/cyanogenmod_t0lte_defconfig) to .config. After that I could run make menuconfig as normal. For ease of examination I forked the kernel repo and stored the distinct changes I made to the config here.
		+
		+	After making tweaks with make menuconfig, I copied .config back to arch/arm/configs/cyanogenmod_t0lte_defconfig. To build the boot image I ran the following set of commands (which I put in a bash script:)
		+
		+	#!/bin/bash
		+
		+	set -e
		+
		+	cd ~/android/system
		+	make clean
		+	cd kernel/samsung/smdk4412
		+	make mrproper
		+	cd ~/android/system
		+	make -j8 bootimage
		+
		+	Note that I do not use mka. Some of the android build manuals recommend mka, but I found it was much less reliable than regular make, so I abandoned it.


Line 591:		Line 611:
	* http://forum.xda-developers.com/showthread.php?t=2152819		* http://forum.xda-developers.com/showthread.php?t=2152819
	* http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building		* http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
		+	* https://blog.afoolishmanifesto.com/posts/replacing-your-cyanogenmod-kernel-for-fun-and-profit/

@@ Line 466: / Line 466: @@
 Sejak CyanogenMod 9, kita tidak lagi menggunakan prebuilt kernel image. System build sudah di modifikasi untuk meminta untuk membuat kernel source.
-Membuat kernel dari system build CyanogenMod akan menjamin bahwa kita akan menggunakan dengan benar Android toolchain. It will also bring more guarantee of compatibility between the kernel and the userspace (system calls, like ioctl, should be consistent between the kernel and userspace).
+Membuat kernel dari system build CyanogenMod akan menjamin bahwa kita akan menggunakan dengan benar Android toolchain. Cara ini juga akan memberikan garansi kompatibilitas antara kernel dan userspace (system calls, seperti ioctl, harus konsisten antara kernel dengan userspace).
-Moreover, the kernel Makefile generally doesn't take care of creating the device-specific ramdisk, embedding the kernel image (zImage) and ramdisk into a boot.img (which structure is sometimes device specific) and pushing everything, including the loadable kernel modules, to the device. Whereas by building from the full CM source, the CM build tools will automate these steps.
+Selanjutnya, Makefile kernel biasanya tidak melakukan hal seperti membuat device-specific ramdisk, embedding kernel image (zImage) dan ramdisk ke boot.img (yang strukturnya kadang kala spesifik device tertentu) dan mem-push berbagai hal, termasuk loadable kernel module, ke device. Dengan membuat CM sepenuhnya dari source, tool CM build akan meng-automasi semua langkah tersebut.
 ====TO AVOID: Building only a kernel module and importing it on a different kernel version====

@@ Line 462: / Line 462: @@
 tidak membuat file zip ClockWordMod atau TWRP yang dapat di flash, kita harus membuat file tersebut jika kita tidak dapat menggunakan zImage secara langsung.
-====TO AVOID: Building only the kernel from the kernel source====
+====HINDARI: Building hanya kernel dari kernel source====
-Building an official kernel from the CyanogenMod build system will ensure your are using the proper Android toolchain. It will also bring more guarantee of compatibility between the kernel and the userspace (system calls, like ioctl, should be consistent between the kernel and userspace).
+Sejak CyanogenMod 9, kita tidak lagi menggunakan prebuilt kernel image. System build sudah di modifikasi untuk meminta untuk membuat kernel source.
 Moreover, the kernel Makefile generally doesn't take care of creating the device-specific ramdisk, embedding the kernel image (zImage) and ramdisk into a boot.img (which structure is sometimes device specific) and pushing everything, including the loadable kernel modules, to the device. Whereas by building from the full CM source, the CM build tools will automate these steps.

@@ Line 452: / Line 452: @@
 Perlu di catat bahwa kita tidak dapat menggunakan perintah <code>mm</code> untuk kernel modul. Karena perintah ini dibuat untuk modul yang menggunakan file Android.mk dan bukan file standard Makefile, seperti system modul (bukan kernel modul).
-{{tip|tip='''Escaping a bootloop:''' If your device is stuck in a bootloop after flashing, flash again the device with a working kernel (or in the worst case with a full ROM / nandroid backup).
+Tip '''keluar dari bootloop:''' Jika device kita stuck di bootloop sesudah di flash, flash lagi device tersebut dengan kernel yang jalan (atau dengan full ROM / nandroid backup).
-In your build directory, you can find the kernel zImage in ''$OUT/obj/KERNEL_OBJ/arch/arm/boot''. This file can be flashed on supported devices with [http://glassechidna.com.au/heimdall/ Heimdall] (for some Samsung devices) or [[Doc:_fastboot_intro|fastboot]] (for devices supporting fastboot mode).
+Jika di directory building, kita dapat menemukan kernel zImage di ''$OUT/obj/KERNEL_OBJ/arch/arm/boot''. File ini dapat di flash ke device yang mendukungnya dengan menggunakan http://glassechidna.com.au/heimdall/ Heimdall untuk device Samsung atau menggunakan fastboot untuk device yang mendukung fastboot.
-Note that however, <code>mka bootimage</code> doesn't generate a ClockWordMod or TWRP flashable zip file, you will have to build it yourself if you can't use the zImage directly.}}
+Perlu di catat bahwa,
 ====TO AVOID: Building only the kernel from the kernel source====

@@ Line 442: / Line 442: @@
 =====Re-build=====
-To re-build the kernel after you've made some changes to the source files or config file, just run <code>mka bootimage</code> again. The build will be much faster due to caching, and selective build of modified files. Beware the errors during the re-build process: the building system may use previously built object/modules if some objects fail to build, leading to inconsistencies. In case of doubt, run <code>mka clean</code>.
+Untuk membuat ulang kernel sesudah kita melakukan beberapa perubah di file source atau file config, cukup menjalankan kembali
-Note that you can't use <code>mm</code>'s command for kernel modules. These commands are made for modules that use an Android.mk file and not a standard Makefile, like system (not kernel) modules.
+ <code>mka bootimage</code>
 {{tip|tip='''Escaping a bootloop:''' If your device is stuck in a bootloop after flashing, flash again the device with a working kernel (or in the worst case with a full ROM / nandroid backup).

@@ Line 432: / Line 432: @@
 =====Ubah konfigurasi kernel=====
-To make a custom kernel configuration file, you can use the configuration build tools from the kernel dir, e.g. <code>make menuconfig</code>, and save the resulting hidden ''.config'' file to the location specified in <code>TARGET_KERNEL_CONFIG</code>. Then run <code>make mrproper</code> from the kernel dir and go back to the CM android source root dir (<code>croot</code>) before building.
+File konfigurasi kernel yang digunakan saat proses build biasanya di acu di <code>TARGET_KERNEL_CONFIG</code> variabel di ''device/vendor-name/device-name/BoardConfig.mk''. Biasanya menunjuk pada ''kernel/vendor-name/kernel-name/arch/arm/configs/cyanogenmod_device-name_deconfig''.
 =====Re-build=====

← Older revision		Revision as of 22:30, 23 November 2014
Line 437:		Line 437:


		+
		+	=====Re-build=====
		+	To re-build the kernel after you've made some changes to the source files or config file, just run <code>mka bootimage</code> again. The build will be much faster due to caching, and selective build of modified files. Beware the errors during the re-build process: the building system may use previously built object/modules if some objects fail to build, leading to inconsistencies. In case of doubt, run <code>mka clean</code>.
		+
		+	Note that you can't use <code>mm</code>'s command for kernel modules. These commands are made for modules that use an Android.mk file and not a standard Makefile, like system (not kernel) modules.
		+
		+	{{tip\|tip='''Escaping a bootloop:''' If your device is stuck in a bootloop after flashing, flash again the device with a working kernel (or in the worst case with a full ROM / nandroid backup).
		+
		+	In your build directory, you can find the kernel zImage in ''$OUT/obj/KERNEL_OBJ/arch/arm/boot''. This file can be flashed on supported devices with [http://glassechidna.com.au/heimdall/ Heimdall] (for some Samsung devices) or [[Doc:_fastboot_intro\|fastboot]] (for devices supporting fastboot mode).
		+
		+	Note that however, <code>mka bootimage</code> doesn't generate a ClockWordMod or TWRP flashable zip file, you will have to build it yourself if you can't use the zImage directly.}}

	====TO AVOID: Building only the kernel from the kernel source====		====TO AVOID: Building only the kernel from the kernel source====
−	As of	+	As of CyanogenMod 9, we are deprecating the usage of prebuilt kernel images. The build system has been modified to ask for (and build) the kernel source. So don't follow CM oldwiki kernel build guide.
		+
		+	Building an official kernel from the CyanogenMod build system will ensure your are using the proper Android toolchain. It will also bring more guarantee of compatibility between the kernel and the userspace (system calls, like ioctl, should be consistent between the kernel and userspace).
		+
		+	Moreover, the kernel Makefile generally doesn't take care of creating the device-specific ramdisk, embedding the kernel image (zImage) and ramdisk into a boot.img (which structure is sometimes device specific) and pushing everything, including the loadable kernel modules, to the device. Whereas by building from the full CM source, the CM build tools will automate these steps.
		+
		+	====TO AVOID: Building only a kernel module and importing it on a different kernel version====
		+	Kernel modules (e.g. a Wi-Fi driver) are built for a specific kernel version. Indeed, the kernel module (.ko file) embed the version of the kernel it is built for (check <code>modinfo module-name.ko</code>). The module will not load if its version is different than the running kernel version (check <code>uname -a</code> from the device terminal prompt). One reason behind this version interdependency is that internal interfaces within the kernel (the interfaces used in your module to access other kernel resources/modules) can and do change between versions. [source: [http://tldp.org/LDP/lkmpg/2.6/html/x569.html#AEN691 LKMPG]]
		+
		+	Therefore you should build and flash a full kernel if you need to change a module.
		+
		+	Otherwise, and if you make no kernel configuration change, you can build a kernel module from the same exact kernel source version (i.e. ''Github commit'') that you're planning to import the module into. If you've not built the kernel yourself, this becomes highly complicated and deprecated: you may need to rebase your CM repository to the exact Github commit that your kernel was built from, extract and use the .config from your device, and eventually trick the source files that take care of defining the magic version of the built kernel module.
		+
		+	==How to reference a custom kernel for building?==
		+	This chapter is intended for people that want to use a totally different kernel than the officially supported ones.
		+	If you only need to modify an officially supported firmware, go back to the previous chapter and play with the kernel files in ''kernel/vendor-name/kernel-name'' (the official kernel files for your device will be downloaded after running the <code>breakfast</code> or <code>lunch</code> commands as described in the [[Build Guides]]).
		+
		+	====Step 0. Preparing the build environment====
		+	Depending on whether your device is supported or not, follow the [[Build Guides]] or [[Doc:_porting_intro\|Porting Guide]] to prepare the Build Environment and get CM Android source code, prebuilt apps, device-specific code and proprietary blobs.
		+
		+	====Step 1. Deploying the kernel source at the proper location====
		+
		+	The minimal requirement is that the kernel's source tree for that device be present at kernel/''vendor-name''/''device-name'' of the CM Android source.
		+
		+	* Officially supported devices:
		+	** For devices which are part of mainline CyanogenMod and have their kernels in CM's github, this can be accomplished by usage of CyanogenMod's ''roomservice'' feature. Create a ''device/vendor-name/device-name/cm.dependencies'' file ('''if it doesn't exist yet'''), with the following syntax. This will take care of downloading the source automatically into the right location.
		+
		+	<pre>
		+
		+	[
		+	{
		+	"repository": "name-of-repository-in-the-CyanogenMod-github",
		+	"target_path": "kernel/vendor-name/device-name",
		+	"branch": "name-of-branch"
		+	}
		+	]
		+
		+
		+	</pre>
		+
		+	* Work-in-progress, unofficial, or otherwise non-integrated devices:
		+	** For devices which don't have their kernel source at the CM github, usage of ''local_manifest.xml'' is recommended in order to deploy the source at the right location, and keeping it synchronized.
		+
		+	* Devices using shared kernel repositories:
		+	** If your device shares a kernel with others, the default ''kernel/vendor-name/device-name'' path will lead to unnecessary duplication of source trees, so usage of the '''TARGET_KERNEL_SOURCE''' configuration variable in ''device/vendor-name/device-name/BoardConfig.mk'' is advised. All devices sharing that source should have the following line in their ''BoardConfig.mk'' files:
		+
		+	<code>
		+	TARGET_KERNEL_SOURCE := kernel/''vendor-name''/''unique-shared-source-name''
		+	</code>
		+
		+	==== Step 2. Configuring the device to build the kernel ====
		+
		+	After the source is in place, configuration of the device to build the kernel is trivial. Just add the '''TARGET_KERNEL_CONFIG''' variable to your ''device/vendor-name/device-name/BoardConfig.mk'' file, pointing to the configuration file name for your device (as present in ''kernal/vendor-name/kernel-name/arch/arm/configs''). For example:
		+
		+	<code>
		+	TARGET_KERNEL_CONFIG := cyanogenmod_device-name_defconfig
		+	</code>
		+
		+	This will trigger the full kernel build, including the modules (if present) as specified in that configuration. Any modules built will be deployed at ''/system/lib/modules/'' in the final image
		+
		+	If your device requires uImage, also ensure the following is present in your 'BoardConfig.mk'
		+
		+	<code>
		+	BOARD_USES_UBOOT := true
		+	</code>
		+
		+	==== Step 3. Configuring the build of out-of-tree kernel modules ====
		+
		+	If your device needs modules that aren't part of the kernel source tree, those can also be built automatically. Some hardware (Texas Instruments' TIWLAN adapters, Broadcom's BCM adapters) is directly supported by CM repositories, but if that isn't your case we suggest you add your module's source to either your device repository, or an isolated path in your kernel source.
		+
		+	To build these modules, the '''TARGET_KERNEL_MODULES''' variable can be used, pointing to a ''make target'' that will build and install such modules. Definition of such a target is the device author's responsibility, the only restriction is that it is a normal makefile recipe. To include, for example, the TI WLAN modules, this can be used:
		+
		+	<pre>
		+	TIWLAN_MODULES:
		+	make -C hardware/ti/wlan/wl1283/platforms/os/linux/ KERNEL_DIR=$(KERNEL_OUT) ARCH="arm" CROSS_COMPILE="arm-eabi-" TNETW=1273 RANDOM_MAC=n REPORT_LOG=n
		+	mv hardware/ti/wlan/wl1283/platforms/os/linux/tiwlan_drv.ko $(KERNEL_MODULES_OUT)
		+	make -C hardware/ti/wlan/wl1283_softAP/platforms/os/linux/ KERNEL_DIR=$(KERNEL_OUT) ARCH="arm" CROSS_COMPILE="arm-eabi-" TNETW=1273 REPORT_LOG=n
		+	mv hardware/ti/wlan/wl1283_softAP/platforms/os/linux/tiap_drv.ko $(KERNEL_MODULES_OUT)
		+
		+	TARGET_KERNEL_MODULES := TIWLAN_MODULES
		+	</pre>
		+
		+	As a rule of thumb, you can just paste your current standalone build commands into a make recipe, replacing the kernel source path with the ''$(KERNEL_OUT)'' variable.
		+
		+	==== Step 4. Configuring the fallback to prebuilts ====
		+
		+	If for some reason the kernel source can't be present, you can still fall back to prebuilt binaries, by defining the '''TARGET_PREBUILT_KERNEL''' variable, like this:
		+
		+	<code>
		+	TARGET_PREBUILT_KERNEL := device/vendor-name/device-name/kernel
		+	</code>
		+
		+	==== Step 5. Building the kernel or full ROM ====
		+
		+	Now that your custom kernel is linked to your device, you can build the device kernel or the device full ROM as you would do with an official kernel, as described in the first part of this page.
		+
		+	==== Full configuration example ====
		+
		+	The following is the p920's configuration (''device/vendor-name/device-name/BoardConfig.mk''), which attempts to build the kernel, uses external modules, and has a prebuilt fallback:
		+
		+	<pre>
		+	# Try to build the kernel
		+	TARGET_KERNEL_CONFIG := cyanogenmod_cosmo_defconfig
		+	# Keep this as a fallback
		+	TARGET_PREBUILT_KERNEL := device/lge/p920/kernel
		+
		+	KERNEL_EXTERNAL_MODULES:
		+	make -C hardware/ti/wlan/wl1283/platforms/os/linux/ KERNEL_DIR=$(KERNEL_OUT) ARCH="arm" CROSS_COMPILE="arm-eabi-" TNETW=1273 RANDOM_MAC=n REPORT_LOG=n
		+	mv hardware/ti/wlan/wl1283/platforms/os/linux/tiwlan_drv.ko $(KERNEL_MODULES_OUT)
		+	make -C hardware/ti/wlan/wl1283_softAP/platforms/os/linux/ KERNEL_DIR=$(KERNEL_OUT) ARCH="arm" CROSS_COMPILE="arm-eabi-" TNETW=1273 REPORT_LOG=n
		+	mv hardware/ti/wlan/wl1283_softAP/platforms/os/linux/tiap_drv.ko $(KERNEL_MODULES_OUT)
		+
		+	TARGET_KERNEL_MODULES := KERNEL_EXTERNAL_MODULES
		+	</pre>
		+
		+
		+
		+
		+
		+
		+
		+	==Referensi==
		+
		+	* https://source.android.com/source/building-kernels.html
		+	* http://www.movzio.com/howto/compile-android-kernel-source-beginners-guide-2/
		+	* http://forum.xda-developers.com/showthread.php?t=2152819
		+	* http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building

@@ Line 152: / Line 152: @@
   gedit .bashrc
-It will open one document, then put this codes at the end of it.
+Tambahkan di bagian bawah
   export PATH=${PATH}:path/to/toolchain/folder/arm-eabi-4.4.3/bin
+Selesai sudah dengan pekerjaan download dan setup. Lanjut ke langkah selanjutnya.
-) Download Source Code:
+==Download Source Code==
-Kernel source codes are under GNU GPL open source license so vendors (ex. Sony, HTC, Samsung, LG) have to release it. You can find your appropriate kernel source code from mentioned websites:
+Source code kernel menggunakan lisensi open source GNU GPL, oleh karenanya vendor (seperti Sony, HTC, Samsung, LG) harus melepas source cidenya. Kita dapat memperoleh kernel source code dari situs:
 For Sony: http://developer.sonymobile.com/
@@ Line 172: / Line 171: @@
 For LG: http://www.lg.com/global/support/opensource/index
-Just download it from mentioned websites as per your device and extract it somewhere in your computer.
+Download dari situs tersebut untuk device yang kita miliki dan ekstrak ke folder di komputer kita.
-Now this is where you should put your focus. For building a kernel you need config file. There is two ways for it:
+==Memperoleh file config==
-    You can either get it from your phone with help of ADB (Android Debug Bridge) or
+Bagian ini adalah bagian yang paling penting dimana kita perlu memfokuskan diri. Untuk membuat kernel kita memerlukan file config. Ada beberapa cara untuk mendapatkannya:
-    You can get it from your kernel source code.
 I will show you both the ways of doing it so.