Hi,
So I was building a ROM for a device supported by a mtk chipset and I wanted to change the prebuilt kernel from the device tree to a source-built kernel, so how to do that? I mean, I removed the TARGET_PREBUILT_KERNEL line from boardconfig but while compiling, it gives an error that the kernel is missing. What exactly to do? Is there any method by which I can change the prebuilt kernel?
Related
Hello everybody,
I have the Stock kernel for my device and I downlaoded the Cm-Kernel. Is there a way to create a patch containing all the Kerneltweaks from Cm-Kernel for the Stockkernel. I know how to handle diff, but I don't know which files are changed and which I should leave like they are. Or if its easier to patch the device specific configurations to the CM-Kernel?
These are the folders both Kernels contain:
Code:
arch crypto include kernel net security
block Documentation init lib README sound
drivers ipc MAINTAINERS REPORTING-BUGS tools
COPYING firmware Kbuild Makefile samples usr
CREDITS fs Kconfig mm scripts virt
chaoskoch said:
Hello everybody,
I have the Stock kernel for my device and I downlaoded the Cm-Kernel. Is there a way to create a patch containing all the Kerneltweaks from Cm-Kernel for the Stockkernel. I know how to handle diff, but I don't know which files are changed and which I should leave like they are. Or if its easier to patch the device specific configurations to the CM-Kernel?
These are the folders both Kernels contain:
Code:
arch crypto include kernel net security
block Documentation init lib README sound
drivers ipc MAINTAINERS REPORTING-BUGS tools
COPYING firmware Kbuild Makefile samples usr
CREDITS fs Kconfig mm scripts virt
Click to expand...
Click to collapse
If you are going to be using all the cm kernel tweaks anyway, why not just use the cm-kernel? Maybe there is something I am missing.
lithid-cm said:
If you are going to be using all the cm kernel tweaks anyway, why not just use the cm-kernel? Maybe there is something I am missing.
Click to expand...
Click to collapse
But in the Kernel are some device specific information and drivers,
is there a way to get them all in the CM-Kernel?
Or aren't there any and I just need the .config-file?
Hello,
I actually have successfully build some kernels. Mainly, this is the linux way:
- get kernel sources
- get hardware specific changes
- get the toolchain -> i'm using google prebuilt tree, with ARM tool chain 4.4.3 already compiled
- build with usual steps: def_config, configure, kernel, modules
All is ok.
Now, i found Android.mk files. Precisely, a previous kernel, with sensors related to my device, that i would like to port.
But here comes the trouble. I have hard time to do the link between Linux kernel for ARM and Android makefile. I don't see how it goes with my kernel, how i could compile this using the prebuilt tools i could grab from Google.
In short, how to include .mk files into a classic kernel ? What should i get in the end ? A module ? A replacement binary ? More precisely, what is exactly NDK and where it stands in the above layers ?
ARM Linux Kernel <--> Dalvik JVM <--> APK
Last, is it possible with Google prebuilt to compile the .mk without referencing your kernel ?
Thank you !
Thank you for your help
Damn ! Either the questions is too obvious, either it is too complex. Any help ?
Self reply: downloading the NDK is mandatory
- you can use your favorite toolchain, provided with the NDK
- you can embed the .mk into your application, for Eclipse / Android studio, it will use the NDK to compile
Hello,
I don't want to build kernel again, I would like to use already compiled zImage. (kernel compiled in a different directory which I use to build kernel)
How can I force build script to use my compiled zImage?
(I'm building CM10)
lozohcum said:
I don't want to build kernel again, I would like to use already compiled zImage. (kernel compiled in a different directory which I use to build kernel)
How can I force build script to use my compiled zImage?
(I'm building CM10)
Click to expand...
Click to collapse
I think you have to run mkbootimg manually to bundle your zImage with the ramdisk, then read this and use TARGET_PREBUILT_KERNEL in your BoardConfig.mk:
http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
HI, I'm trying to compile cyanogen's kernel for mako
however with the compiler I used to compile AOSP sources, cm won't compile without modification to source code.
Can anyone tell the toolchain used by CM for it's releases so I can do a successful complication without source code modification?
Anyone willing to tell the toolchain?
I found this page on enabling kernel page table dump in Android (https://wenboshen.org/posts/2018-09-09-page-table.html). For this I have to edit a defconfig and rebuild the kernel. I built my own AOSP (Android 9, blueline userdebug) but can't locate the defconfig for my device. In fact the arch/arm64/configs/ directory is missing.
How can I create a custom defconfig within the AOSP repo? Or do I have to download the kernel source for my device and rebuild/flash it?
In general what is the relation between AOSP and the kernel source? Does AOSP not build the kernel as part of it?