[KERNEL][AOSP/TW][27 Dec] War Kernel r3 // colder than ever

freedmm

Senior Member
Feb 23, 2014
67
17
28
ANTALYA
I don't understand your question
sorry for bad english. im trying to compile a rom using your kernel source. and im getting errors saying this "/home/er/liq/kernel/samsung/raw/drivers/gpu/mali400/r3p2/mali/Kbuild:53: *** Runtime PM is incompatible with non-GPL license. Stop." or " *** Linux Device integration is incompatible with non-GPL license***
how can i find out the error reason?
 

GeeckoDev

Senior Member
Feb 26, 2013
458
3,331
0
sorry for bad english. im trying to compile a rom using your kernel source. and im getting errors saying this "/home/er/liq/kernel/samsung/raw/drivers/gpu/mali400/r3p2/mali/Kbuild:53: *** Runtime PM is incompatible with non-GPL license. Stop." or " *** Linux Device integration is incompatible with non-GPL license***
how can i find out the error reason?
Oh that's a weird error you have there. Just look at Kbuild, there's a check for Mali license files. For some reason the GPL file drivers/gpu/mali400/r3p2/mali/linux/license/gpl/mali_kernel_license.h is not found so that triggers it. You can remove the check safely I guess. Have you modified anything?

If you want to build from source you'll also have to add boot.cpio and recovery.cpio in usr/galaxys2_initramfs_files/ extracted from NightOwl. EDIT: you won't need them since you're building for the rom, okay
 
Last edited:

freedmm

Senior Member
Feb 23, 2014
67
17
28
ANTALYA
Oh that's a weird error you have there. Just look at Kbuild, there's a check for Mali license files. For some reason the GPL file drivers/gpu/mali400/r3p2/mali/linux/license/gpl/mali_kernel_license.h is not found so that triggers it. You can remove the check safely I guess. Have you modified anything?

If you want to build from source you'll also have to add boot.cpio and recovery.cpio in usr/galaxys2_initramfs_files/ extracted from NightOwl. EDIT: you won't need them since you're building for the rom, okay
i only add .cpio files in usr/ that you said too. i didnt modify anything another. im using .cpio files for twrp recovery of bauner's. so i will remove the check. thanks for the help.
 

GeeckoDev

Senior Member
Feb 26, 2013
458
3,331
0
Just for the kicks: it's possible to boot our phone with a reduced screen resolution. The touchscreen doesn't match so it's completely useless.

1280x720 (S3/Note2)


800x480 (S2)
 
  • Like
Reactions: bauner

FabreFaction

Senior Member
Oct 22, 2009
935
692
0
www.endoftheinternet.com
So, can anyone report on the battery life for War r2?
Looks good to me.
I have been running the kernel on Bauners L ROM for a few days without any problems.
I'm getting a solid days usage.
Not as good as my previous ROM, KitKat, but good.
If I plug in at anything above 20% I'm happy.
Been averaging around 30%.
On KitKat it was 40% max.
I can't compare to RAW1, but very happy with RAW2.
Cheers @geekodev

Sent from my GT-N7000 using Tapatalk
 
Last edited:

ahmed afwaan

Member
Nov 11, 2015
16
0
0
im on nightowl cyanogenmod 12.1 20151030 version ,using this kernel since last three day's ,the problem with this kernel is phone get switch off certain times and have to manually start the phone what could be the problem?
 
Last edited:

GeeckoDev

Senior Member
Feb 26, 2013
458
3,331
0
im on nightowl cyanogenmod 12.1 20151030 version ,using this kernel since last three day's ,the problem with this kernel is phone get switch off certain times and have to manually start the phone what could be the problem?
Is it happening with War r1? Also do you know your phone's voltage group?

EDIT: @bauner I spotted a typo in the Mali platform file exynos4_pmm.c that sets the GPU at 200MHz with a very low voltage when the clocks are enabled (when it goes out of sleep I guess). That could be the cause of some instabilities. It was introduced when we migrated to r3p2 drivers.
 
Last edited:

ahmed afwaan

Member
Nov 11, 2015
16
0
0
Is it happening with War r1? Also do you know your phone's voltage group?

EDIT: @bauner I spotted a typo in the Mali platform file exynos4_pmm.c that sets the GPU at 200MHz with a very low voltage when the clocks are enabled (when it goes out of sleep I guess). That could be the cause of some instabilities. It was introduced when we migrated to r3p2 drivers.

ya with both kernels war r1,r2....i dont know voltage group of my phone!
btw what is phone voltage group?
 
Last edited:

bauner

Retired Recognized Developer
Jan 23, 2008
4,726
10,330
263
Near Nürnberg
Is it happening with War r1? Also do you know your phone's voltage group?

EDIT: @bauner I spotted a typo in the Mali platform file exynos4_pmm.c that sets the GPU at 200MHz with a very low voltage when the clocks are enabled (when it goes out of sleep I guess). That could be the cause of some instabilities. It was introduced when we migrated to r3p2 drivers.
It is also the same in r3p1... But maybe we should try
Code:
#if defined(CONFIG_CPU_EXYNOS4212) || defined(CONFIG_CPU_EXYNOS4412)
mali_runtime_resume_table mali_runtime_resume = {266, 900000, 1};
#else
mali_runtime_resume_table mali_runtime_resume = {267, 1000000, 1};
#endif
 

GeeckoDev

Senior Member
Feb 26, 2013
458
3,331
0
It is also the same in r3p1... But maybe we should try
Code:
#if defined(CONFIG_CPU_EXYNOS4212) || defined(CONFIG_CPU_EXYNOS4412)
mali_runtime_resume_table mali_runtime_resume = {266, 900000, 1};
#else
mali_runtime_resume_table mali_runtime_resume = {267, 1000000, 1};
#endif
Keep in mind that r3p1 drivers have never been shipped in any 4210 device. JB was using r2p4 ;) pegasus-m400 platform is meant for 4x12 devices, otherwise it's orion-m400.

In r2p4 the lowest step (160MHz) is set on resume.
 
  • Like
Reactions: bauner