What .ko's from kernel build?
I just successfully built a kernel with my phone over nfs (wifi). I used gcc-armhf
or rather to be specific, when it complained I set 'CROSS_COMPILER=/usr/bin/
', cleaned, and retried. Everything seems to have went fine, and as expected I have the zImage
and the modules are scattered around, but theres a list on stdout
I can use to copy them somewhere.
1.) Which kernel object files do I need?
2.) I will look at the device/samsung/d2spr/extract-files.sh
file to see where I should put them, but where should I put the ones that may have been created from the config changes and are not listed?
My first couple of trys failed due to the kernel being too large, so I changed some things to modules that I think can wait to load or set up an init script. I also didn't use mkbootimg
, I used abootimg
, that may have been why, not too sure. I used unmkbootimg
and saved the stdout
to a file this time and built the kernel on my phone, still, those are some questions I still have.
Edit: Another way to ask this question...
3.) Do I need to replace the 'blobs' that I got from the official CM ROM with the ones I just built?
4.) Do the modules I built contain the proprietary code to run the hardware, or where some (wifi driver for instance) 'filled' in with 'dummy code'?
Note: The zImage built was 3699216 bytes or about 3.6 MB. The zImage I need to replace is "Kernel size 3907440" or roughly 3.9MB, things are looking good, for once!
"Wise man say, 'Forgiveness is divine,
but never pay full price for late pizza'."
Some Usefull links:
// Good read on the Android specificities of the kernel
// Info on Binder and ashmem and how to share memory!