yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Sk.D:
Hey, I am also facing similar error here, "no rule to make target menuconfig

skd@skd-HP-Casablanca-H710:~$ cd android
skd@skd-HP-Casablanca-H710:~/android$ cd kernel
bash: cd: kernel: No such file or directory
skd@skd-HP-Casablanca-H710:~/android$ cd kernels
skd@skd-HP-Casablanca-H710:~/android/kernels$ export ARCH=arm
skd@skd-HP-Casablanca-H710:~/android/kernels$ export CROSS_COMPILE=~/android/kernel/toolchains/arm-eabi-linaro-4.6.2/bin/arm-eabi-
skd@skd-HP-Casablanca-H710:~/android/kernels$ cp mediatek/config/mt6582/autoconfig/kconfig/platform .config
skd@skd-HP-Casablanca-H710:~/android/kernels$ make A120_defconfig
make: *** No rule to make target `A120_defconfig'. Stop.
skd@skd-HP-Casablanca-H710:~/android/kernels$ make menuconfig
make: *** No rule to make target `menuconfig'. Stop.
skd@skd-HP-Casablanca-H710:~/android/kernels$

[MENTION=5321417]MasterAwesome[/MENTION] : Help??

[MENTION=5480061]Santhosh M[/MENTION] : :( ????????

I did some changes and now Im getting this error

skd@skd-HP-Casablanca-H710:~$ cd android
skd@skd-HP-Casablanca-H710:~/android$ cd kernels
skd@skd-HP-Casablanca-H710:~/android/kernels$ export ARCH=arm
skd@skd-HP-Casablanca-H710:~/android/kernels$ export CROSS_COMPILE=~/android/kernels/toolchains/arm-eabi-linaro-4.6.2/bin/arm-eabi-
skd@skd-HP-Casablanca-H710:~/android/kernels$ cp mediatek/config/devicename/autoconfig/kconfig/platform .config
cp: cannot stat ‘mediatek/config/devicename/autoconfig/kconfig/platform’: No such file or directory
skd@skd-HP-Casablanca-H710:~/android/kernels$ cp mediatek/config/mt6582/autoconfig/kconfig/platform .config
skd@skd-HP-Casablanca-H710:~/android/kernels$ cd kernel
skd@skd-HP-Casablanca-H710:~/android/kernels/kernel$ make A120_defconfig
/home/skd/android/kernels/kernel/../mediatek/build/Makefile:13: *** TARGET_PRODUCT/PROJECT is not set. Stop.
skd@skd-HP-Casablanca-H710:~/android/kernels/kernel$ make menuconfig
[Miscellaneous Android Development] patraanjan23:
I was facing the same problem. For make error just change your directory inside the 'kernel' folder. For 2nd problem use export TARGET_PRODUCT=devicename.

Sent from my Micromax A106
[Miscellaneous Android Development] andrman1:
can you briefly explain what to do for first problem I can't understand. [no rule to make menuconfig]

thanks
[Miscellaneous Android Development] patraanjan23:
There are 2 folders. 'kernel' n 'mediatek'. When using make 'cd' into the 'kernel' folder. As the make files are there! So "cd kernel" then use "make menuconfig" n then "make".

Sent from my Micromax A106
[Miscellaneous Android Development] boka18:
Hello! I have HTC Desire 310 (mt6582) and so far there aren't any Custom kernels nor Roms, so I'm trying to do something about it, but it's not going very well for me. I need someone to give me a step by step guide for how to make a Kernel with SELinux support, etc..

I have the kernel source but im not really experienced about that. If anyone want's to volunteer and build Custom Kernel so we can port CyanogenMod (since there is CM for mt6582).

If someone has time and will, do not hesitate to PM me.

Cheers!
[Miscellaneous Android Development] cyclon1978:
Looks like acer e3 kernel... why not use kitkat source? See github.com/cyclon1978/e380....

Kitkat acer kernel has all modules build in, dont know about jb variant...

Gesendet von meinem E380 mit Tapatalk
[Miscellaneous Android Development] chiragjn:
Actually it is Acer E2 kernel from here : https://github.com/JujuXIII/android_kernel_acer_v370

Yeah I understood few hours after posting that Kitkat has all modules built in.Thanks again.

Actually my mt6589 device has no kernel source.I found a Acer E2 kitkat rom which booted up on my device(I didn't even change the boot.img) and lcd is working and touch panel is not working.So I am thinking to modify the kernel source according to my device.

About Phone> Kernel Version > JujuXIII.

I compiled a fresh kernel from JujuXIII's github :https://github.com/JujuXIII/android_kernel_acer_v370 just to see if it boots so that I know if this source is appropriate for modification

But I am not able to boot the new kernel.I used the same ramdisk and same rom just changed the kernel, but the new kernel doesn't boot, just gets stuck at bootlogo and never proceeds to bootanimation.

I have hit a wall and don't know where to proceed.

Edit :

I got a kernel booting which i compiled from older sources.

But the problem now is my display backlight stays on all the time.
[MENTION=5321417]MasterAwesome[/MENTION] any idea what should i do to solve this?
[Miscellaneous Android Development] kien_vip:
hey everyone, i am newbie with kernel compile. i edit my xxx_defconfig as below to set sio default scheduler:

but. after "make xxx_defconfig", the .config revert back like this:

than, i can manual edit .config by hand. that is safe and compiler will work correctly ?
[Miscellaneous Android Development] Papdya:
I hav a mt6577 device.. Can i use other phones source offers mt6577 to build a kernel for my device?
[Miscellaneous Android Development] Tech N You:
[MENTION=5321417]MasterAwesome[/MENTION] thank you for this amazing guide.

I'll be trying it later, but need one help.

Like tweaking kernel adding support like OTG and overclocking how can we do that?

Any news on that?

Thanx for this awesome Tut
[Miscellaneous Android Development] MasterAwesome:
Firstly, thank you, it means a lot.

Technically speaking, all the kernel features are just source c files which are included in the makefile when building and you use this feature from android and use the kernel as a way of communication. I'm not very familiar with specific tweaks but as a general rule the method is same.

So the feature you want to add must be included in the makefile and compiled and accessed from the OS
[Miscellaneous Android Development] Tech N You:
That was all I needed! A big score Thanks again [MENTION=5321417]MasterAwesome[/MENTION] :good: :cool::laugh:
[Miscellaneous Android Development] kenkitt:
#

# Automatically generated make config: don't edit

# Linux kernel version: 2.6.35.7

# Tue Dec 16 15:53:27 2014

Well, I had to download the entire ALPS build environment.

Then download your devices kernel and build it using build.sh , after configuring the environment in the kernel dir.

Afterwards copy the generated kernel...bin file into the baoxue_mytqe-master/kernel/ dir and rename it to kernel_baoxue.bin

then run

./target_build bootimage

you will get your boot.img in /baoxue_mytqe-master/out/target/product/baoxue/boot.image

that's all, I did , but i'll have to look into it deeply to understand what is going on.

Any am a little dissappointed that nobody showed how to do this, or even offered to help.

But I guess the best way is the hardway , compiling it a hundred times, only to figure out that arm-android-eabi doesn't work I found this after trying the original arm-eabi-

If you get s bootloop, try building with the stock .confi from the downloaded source then proceed.
[Miscellaneous Android Development] Cod3AlchemisT:
Hey I am compiling kernel for first time...

I am getting following error:

mugdha@mugdha-Vostro-2520:~$ export TARGET_BUILD_VARIANT=user TARGET_PRODUCT=mt6589 MTK_ROOT_CUSTOM=../mediatek/custom/ TARGET_KERNEL_VERSION=mt6589&&export PATH=~/toolchain/arm-eabi-4.6/bin:$PATH&&export CROSS_COMPILE=arm-eabi-&&export ARCH=arm
mugdha@mugdha-Vostro-2520:~$ cd Kernel
mugdha@mugdha-Vostro-2520:~/Kernel$ cp mediatek/config/mt6589/autoconfig/kconfig/platform .config
mugdha@mugdha-Vostro-2520:~/Kernel$ cd kernel
mugdha@mugdha-Vostro-2520:~/Kernel/kernel$ make menuconfig
HOSTCC scripts/basic/fixdep
/bin/sh: 1: ccache: not found
make[1]: *** [scripts/basic/fixdep] Error 127
make: *** [scripts_basic] Error 2
mugdha@mugdha-Vostro-2520:~/Kernel/kernel$

What is causing it? :(
[Miscellaneous Android Development] MasterAwesome:
sudo apt-get install ccache.
[Miscellaneous Android Development] Cod3AlchemisT:
Thank You for your quick reply.

Now I am presented with following errors:

mugdha@mugdha-Vostro-2520:~/Kernel/kernel$ export TARGET_BUILD_VARIANT=user TARGET_PRODUCT=mt6589 MTK_ROOT_CUSTOM=../mediatek/custom/ TARGET_KERNEL_VERSION=mt6589 &&export PATH=~/toolchain/arm-eabi-4.6/bin:$PATH&&export CROSS_COMPILE=arm-eabi-&&export ARCH=arm
mugdha@mugdha-Vostro-2520:~/Kernel/kernel$ cp ~/Kernel/mediatek/config/mt6589/autoconfig/kconfig/platform .config
mugdha@mugdha-Vostro-2520:~/Kernel/kernel$ make menuconfig
scripts/kconfig/mconf Kconfig
../mediatek/kernel/Kconfig:8:warning: environment variable ARCH_MTK_PLATFORM undefined
../mediatek/kernel/Kconfig:15: can't open file "../mediatek/platform//kernel/Kconfig/Platform"
make[1]: *** [menuconfig] Error 1
make: *** [menuconfig] Error 2
mugdha@mugdha-Vostro-2520:~/Kernel/kernel$ make zImage
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
../mediatek/kernel/Kconfig:8:warning: environment variable ARCH_MTK_PLATFORM undefined
../mediatek/kernel/Kconfig:15: can't open file "../mediatek/platform//kernel/Kconfig/Platform"
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.

It seems to me that "mt6589" is missing in ../mediatek/platform//kernel/Kconfig/Platform i.e it should be ../mediatek/platform/mt6589/kernel/Kconfig/Platform

Please advice...Thanks!
[Miscellaneous Android Development] MasterAwesome:
That is because the Environment variable "ARCH_MTK_PLATFORM" is not set. export it via the terminal. something like

export ARCH_MTK_PLATFORM=MT****

since the KConfig will specify the directory and drivers it will build using this variable

config ARCH_MTK_PLATFORM
string
option env="ARCH_MTK_PLATFORM"
[B][I][I]source "../mediatek/platform/$ARCH_MTK_PLATFORM/kernel/Kconfig/Platform"
source "../mediatek/platform/$ARCH_MTK_PLATFORM/kernel/Kconfig/Kernel"
source "../mediatek/platform/$ARCH_MTK_PLATFORM/kernel/Kconfig/Board"
source "../mediatek/platform/$ARCH_MTK_PLATFORM/kernel/Kconfig/Drivers"[/I][/I][/B]

endif
[Miscellaneous Android Development] Cod3AlchemisT:
Thank you!!! That did solve the error.... but now i have new ones:

mugdha@mugdha-Vostro-2520:~$ export TARGET_BUILD_VARIANT=user TARGET_PRODUCT=mt6589 MTK_ROOT_CUSTOM=../mediatek/custom/ TARGET_KERNEL_VERSION=mt6589 &&export PATH=~/toolchain/arm-eabi-4.6/bin:$PATH&&export CROSS_COMPILE=arm-eabi-&&export ARCH=arm
mugdha@mugdha-Vostro-2520:~$ cd Kernel
mugdha@mugdha-Vostro-2520:~/Kernel$ cp mediatek/config/mt6589/autoconfig/kconfig/platform .config
mugdha@mugdha-Vostro-2520:~/Kernel$ cd kernel
mugdha@mugdha-Vostro-2520:~/Kernel/kernel$ export ARCH_MTK_PLATFORM=MT6589
mugdha@mugdha-Vostro-2520:~/Kernel/kernel$ make menuconfig
scripts/kconfig/mconf Kconfig
../mediatek/kernel/Kconfig:15: can't open file "../mediatek/platform/MT6589/kernel/Kconfig/Platform"
make[1]: *** [menuconfig] Error 1
make: *** [menuconfig] Error 2
mugdha@mugdha-Vostro-2520:~/Kernel/kernel$ make zImage
scripts/kconfig/conf --silentoldconfig Kconfig
../mediatek/kernel/Kconfig:15: can't open file "../mediatek/platform/MT6589/kernel/Kconfig/Platform"
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
[Miscellaneous Android Development] MasterAwesome:
Umm.. I see you've copied my exports from the original post. It's fine except for the mtk custom root. You need to link it to your custom folder. Sometimes it's in the folder some times it isn't.
[Miscellaneous Android Development] Nihal @A-JAX:
Hi ,

What is causing this error ? I'm not able to debug. Please help master
[Miscellaneous Android Development] MasterAwesome:
Source is providing an unknown tag 'EL' which is not in the scope, grep the kconfigs and delete it.
[Miscellaneous Android Development] remzej:
Hello [MENTION=5321417]MasterAwesome[/MENTION]

I recompiled the Aquaris 5 HD KitKat kernel source from https://github.com/bq/aquaris-5HD and it was successful. But it doesn't boot up my device. I already used the ramdisk from stock boot.img of Aquaris 5 HD KitKat firmware that boots up my device. What seems to be the problem? I'm thinking maybe the released kernel source code was outdated or maybe not the same config that the working boot.img was built.

Thanks

REMZEJ
[Miscellaneous Android Development] I.nfraR.ed:
I have a question about KK.

I've already compiled KK kernel (real 3.4.67 kernel and mediatek platform code). The kernel works with cwm recovery 6.0.5, KK roms install fine, but I don't get past the first logo.

Do I need to compile lk as well or I can live with the stock one?

Also when trying to boot, adb doesn't see the device at all. It goes into bootloop in a while.

Any idea how to debug?

The problem is there's no original KK for Lenovo A820 and I don't have a reference point. For JB we could try to replace libs, etc.

Thanks for the threads btw, they gave me a good starting point in the beginning when I was a total noob.
[Miscellaneous Android Development] MasterAwesome:
Kmsg is your friend use it to identify your problem..debug it via recovery. log files are under /proc
[Miscellaneous Android Development] remzej:
[MENTION=5321417]MasterAwesome[/MENTION] I'm new in Kernel development mean totally noob hehehe. My compiled boot.img doesn't allow my device to boot up its stuck at bootlogo and cannot access adb shell. I can still boot into recovery mode because it uses the working kernel.
[Miscellaneous Android Development] MasterAwesome:
Go to recovery pull out a file called last_kmsg or kmsg from the folder "/proc"
[Miscellaneous Android Development] I.nfraR.ed:
Yes, but that's the kernel messages, while I think my problem is lk (little kernel). Kernel is reposnding well while in recovery.

And I don't have last_kmsg.

It does not go past first logo. First logo is the logo.bin, then the logo of the lk.bin and the third one is when android is booting.

So I don't get to the second logo.

How to compile lk.bin? :(
[Miscellaneous Android Development] I.nfraR.ed:
Could that be the problem?

I don't see other errors.

Shouldn't fat (mmcblk0p8 block) be 0?

<3>[ 0.840120] (3)[67:mmcqd/0][MSDC] msdc0 -> Address offset in USER REGION(Capacity 3728 MB) is 0x1f00 <- msdc_cal_offset() : L<2935> PID<mmcqd/0><0x43>
<6>[ 0.842133] (3)[5:kworker/u:0] mmcblk0: p1 < p5 p6 p7 p8 > p2 p3 p4
<4>[ 0.842164] (3)[5:kworker/u:0]add_partition==[mmcblk0:p1]==start = 1024,size = 2
<4>[ 0.842274] (3)[5:kworker/u:0]add_partition==[mmcblk0:p2]==start = 26624,size = 20480
<4>[ 0.842397] (3)[5:kworker/u:0]add_partition==[mmcblk0:p3]==start = 47104,size = 20480
<4>[ 0.842493] (3)[5:kworker/u:0]add_partition==[mmcblk0:p4]==start = 93184,size = 12288
<4>[ 0.842580] (3)[5:kworker/u:0]add_partition==[mmcblk0:p5]==start = 134144,size = 1331200
<4>[ 0.842673] (3)[5:kworker/u:0]add_partition==[mmcblk0:p6]==start = 1465344,size = 258048
<4>[ 0.842760] (3)[5:kworker/u:0]add_partition==[mmcblk0:p7]==start = 1723392,size = 5242880
<4>[ 0.842854] (3)[5:kworker/u:0]mmcblk0: p8 size 4288002047 extends beyond EOD, truncated
<4>[ 0.842876] (3)[5:kworker/u:0]add_partition==[mmcblk0:p8]==start = 6966272,size = 617728
<6>[ 0.843832] (3)[5:kworker/u:0] mmcblk0boot1: unknown partition table
<6>[ 0.844524] (3)[5:kworker/u:0] mmcblk0boot0: unknown partition table
<6>[ 0.844711] (3)[5:kworker/u:0]emmc_create_sys_symlink: target=/dev/block/mmcblk0p1, name=/emmc@ebr1
<6>[ 0.844787] (3)[5:kworker/u:0]emmc_create_sys_symlink: target=/dev/block/mmcblk0p2, name=/emmc@protect_f
<6>[ 0.844838] (3)[5:kworker/u:0]emmc_create_sys_symlink: target=/dev/block/mmcblk0p3, name=/emmc@protect_s
<6>[ 0.844892] (3)[5:kworker/u:0]emmc_create_sys_symlink: target=/dev/block/mmcblk0p4, name=/emmc@sec_ro
<6>[ 0.844941] (3)[5:kworker/u:0]emmc_create_sys_symlink: target=/dev/block/mmcblk0p5, name=/emmc@android
<6>[ 0.844989] (3)[5:kworker/u:0]emmc_create_sys_symlink: target=/dev/block/mmcblk0p6, name=/emmc@cache
<6>[ 0.845038] (3)[5:kworker/u:0]emmc_create_sys_symlink: target=/dev/block/mmcblk0p7, name=/emmc@usrdata
<6>[ 0.845087] (3)[5:kworker/u:0]emmc_create_sys_symlink: target=/dev/block/mmcblk0p8, name=/emmc@fat
<3>[ 0.845161] (3)[5:kworker/u:0]msdc1 -> Card insert<1> Block bad card<0> <- msdc_ops_get_cd() : L<6140> PID<kworker/u:0><0x5>
[Miscellaneous Android Development] MasterAwesome:
Depends on your partition list... Might be, check if all the file systems needed for booting the os is added to the kernel.
[Miscellaneous Android Development] I.nfraR.ed:
Some differences in generated scatter and original one.

Generated

CACHE 0x42f80000
USRDATA 0x4ad80000
__NODL_FAT 0x8ad80000

original

CACHE 0x29f80000
USRDATA 0x31f80000
__NODL_FAT 0x5c780000

Yet another question. If I disable SELinux and use JB ramdisk, I should be able to boot the kernel on JB rom, right?
[Miscellaneous Android Development] remzej:
[MENTION=5321417]MasterAwesome[/MENTION] i can't access adb when I'm in recovery mode. When I type adb devices I can see my device as offline. Using cat /proc/last_kmsg2 doesn't work. I'm using PhilTouch custom recovery. Do I need to flash the stock recovery?
[Miscellaneous Android Development] MasterAwesome:
Yes, disable Se Linux and try it.

You're on Linux right?
[Miscellaneous Android Development] remzej:
Yes I'm using ubuntu 10 64Bit. I tried the adb shell using windows app VTS.
[Miscellaneous Android Development] I.nfraR.ed:
Try

sudo killall adb
sudo adb devices
[Miscellaneous Android Development] remzej:
I will setup first the Android SDK on my ubuntu 64 bit system. See my attachment when I type adb devices on my windows 8.1 64 bit system when my phone is in recovery mode.
[Miscellaneous Android Development] hajasgellert:
you need to mount USB device in "mounts and storage>mount USB storage" in your recovery
[Miscellaneous Android Development] MasterAwesome:
That's not what he is looking for.

And you need to add the lsusb output vendor id to the rules list and recognize it using the rule. USB rules are found in /etc/udev/rules.d
[Miscellaneous Android Development] Santhosh M:
This source is fine. I have compiled it for a guy who said he had a clone of it. As far as i remember it booted. The kernel source is fine. You have the same device or the clone of it ?

I presume in my mind you might have forgot a step which might be the reason for yours not booting. Could u PM me the compilation method so that i can help you out :)
[Miscellaneous Android Development] superdragonpt:
You need to compile it as USER.

Regards
[Miscellaneous Android Development] MasterAwesome:
Long time no see [MENTION=5238428]superdragonpt[/MENTION]... How are you? :P
[Miscellaneous Android Development] remzej:
Yes Sir I recompiled it as user using this commands:

./mk -t -o=TARGET_BUILD_VARIANT=user lcsh89_wet_kk new k

and also

TARGET_BUILD_VARIANT=user ./makeMtk lcsh89_wet_kk n k

Compiled it successfully but after merging the zImage to ramdisk and flashed it on my device it doesn't boot up just stuck at bq logo.
[Miscellaneous Android Development] superdragonpt:
You need to fix The GPU platform driver, in order to be compiled as USER.

Then you use those build commands to compiled an USER build

Also, check the drvgen, you may need to update it, or change some configs...

Xeers

Very busy ;)
[Miscellaneous Android Development] remzej:
Stock KitKat firmware already works fine on my device Sir. I also tried recompiling without changing any configs but still not booting my device. I just need to recompile the kernel for the main camera to work on my device.
[Miscellaneous Android Development] I.nfraR.ed:
Did you add the mediatek header?
[Miscellaneous Android Development] I.nfraR.ed:
Sucess!

First ever KitKat on Lenovo A820!

I'm so happy :D

I want to thank again for these guides that gave me a good start.

Also I have learned a lot from [MENTION=5439876]Dr-Shadow[/MENTION]'s repos for MT6589. Many thanks to him as well, even if we don't know eachother and I don't write here (xda) often, because almost all of my noobish questions don't get answer,

like I'm invisible, exception being this thread and [MENTION=5321417]MasterAwesome[/MENTION].
[Miscellaneous Android Development] remzej:
Yes I already patched the header using mkimage zImage KERNEL > new_zImage

My device won't boot up in normal mode using the new_zImage + stock_ramdisk (new_boot.img). So to test the new_zImage, I unpacked my CWM recovery and I repacked it with new_zImage + recovery-ramdisk and it boots up in recovery mode.
[Miscellaneous Android Development] I.nfraR.ed:
Actually I'm using the same Aquaris 5HD source and you don't need to manually add the MTK header.

Which toolchain do you use?

I have succeeded with arm-linux-androideabi-4.7 , but haven't tried another toolchain yet.

You might try it and see if it works. I was using arm-eabi 4.8 before and that might have been part of the problem.

Actually I don't know what made my kernel boot, because I have fixed a lot of things, one of them was the partition table, based on the original scatter file I have.

My original device kernel tree is an old JB4.1.

I had the same symptoms though - it works with the recovery, however does not show the second logo and goes into bootloop. ADB was not seeing the device.

Btw, is the KK rom stable for this device? I want to find as clean as possible AOSP-based 4.4 rom, without any (major) bugs.

Don't want to port another port...

I will cleanup the source and upload it to my repo tomorrow.

I haven't changed much in the original source yet, so you might be able to just build it from my source after changing the target device.
[Miscellaneous Android Development] remzej:
Yes and we used the same toolchain for recompiling the kernel source. I also fixed the partition table and matched it exactly with the original scatter file. May I ask did you add the line "CONFIG_KERNEL_XZ=y" in /aquaris-5HD/mediatek/config/lcsh89_wet_kk/autoconfig/kconfig/project file?
[Miscellaneous Android Development] I.nfraR.ed:
No, I have it in the mt6589 platform config file, but yes - I had to "XZ" it to fit in the recovery.

I have attached my platform file.
[Miscellaneous Android Development] remzej:
I will compare your platform.txt with mine to see any differences and try to make changes then will try to recompile again to test if it will boot my device. What is the file size of your compiled zImage?
[Miscellaneous Android Development] MasterAwesome:
Congrats mate. Happy to help
[Miscellaneous Android Development] MasterAwesome:
Since so many of you are asking new recovery related issues, I have decided to make a "making a recovery" guide soon.

Regards
[Miscellaneous Android Development] MasterAwesome:
Hi, what exactly are you trying to compile, a kernel to work with a recovery or a boot.img?
[Miscellaneous Android Development] remzej:
I'm trying to compile a working kernel for boot.img to boot up my device Sir.
[Miscellaneous Android Development] I.nfraR.ed:
3,4 MB (3405152 bytes)

The good thing is I managed to boot one rom for P780 from the first try after kernel fixes, so I'm now sure it boots fine.

Couple of things don't work as expected, but I will fix them.

Wi-Fi, audio, touchscreen, buttons, GPS - all works. Proximity and acceleration sensor don't work at the moment, but they have wrong drivers (not sure why). Something with my configs I guess.