Database Info

[Q] kernel

Hi,
I am trying to extract the kernel from mmcblk0p20 using unpack-bootimg.pl
from this post: http://forum.xda-developers.com/showpost.php?p=2885020&postcount=1
I can get a valid ramdisk out of it but the kernel is not a gz file as it should be.
Any hint?

Etn40ff said:
Hi,
I am trying to extract the kernel from mmcblk0p20 using unpack-bootimg.pl
from this post: http://forum.xda-developers.com/showpost.php?p=2885020&postcount=1
I can get a valid ramdisk out of it but the kernel is not a gz file as it should be.
Any hint?
Click to expand...
Click to collapse
The kernel is not exactly a "gzipped" file because the first part of it has bootloader code that provides a mechanism to uncompress the remaining part of the kernel (which uses a form of gzip provided by a micro zlib).
More importantly, what are you trying to accomplish? The "kernel" image that comes from split_bootimg.pl (or such) is the actual file you use to re-pack, etc. Unless of course you're trying to decompile the kernel for reverse engineering purposes, but that would be pointless and you wouldn't be asking this question if that were the case.
If you're trying to get the kernel config, use extract-ikconfig from the 'scripts' directory in the Linux source tree. You have to invoke it by cd'ing into the Linux source directory and doing:
Code:
./scripts/extract-ikconfig /path/to/your/kernel-file &> /where/you/want/the/resulting-config
(you can't cd into 'scripts' and have it work).
Enjoy.

As you say unpacking the kernel to get the configuration is pointless: I could get it on htcdev without any effort.
I just had a boring night and I tried to kill it repacking my own flavour of android.
I was not able to make it boot so I started guessing which problem I was having; the kernel seemed a reasonable candidate (I was convinced that I was stripping the header away from it when unpacking)

how could you acquire that kernel? last time I checked there was no source?

You need the kernel source before a kernel can be made. Thats the sucky part.
Sent from my myTouch_4G_Slide using xda premium

Undeadk9 said:
You need the kernel source before a kernel can be made. Thats the sucky part.
Click to expand...
Click to collapse
Eh? No. A kernel exists, just in binary form. HTC has yet to release the source code, but unless you plan to modify parts of it, there's not much point.

nbetcher said:
Eh? No. A kernel exists, just in binary form. HTC has yet to release the source code, but unless you plan to modify parts of it, there's not much point.
Click to expand...
Click to collapse
A kernel source is no problem, I got it from android github.
The issue is the mods htc made and added, and the tools around it they used to compile.
I would like to compile my own, to optimize (did it on linux too).
If anyone can explain me simple how to use the binary kernel, I am happy too for now, if that makes me able to compile CM7

Anyone? Can't be too hard since a lot of folks pulled it of?
I have a lot of technical experience, just need some android specific info

I know nothing bout kernels. They scare me. I'll stick to ROM making.
Sent from my MyTouch 4G Slide using xda premium

OpenMinded said:
A kernel source is no problem, I got it from android github.
The issue is the mods htc made and added, and the tools around it they used to compile.
I would like to compile my own, to optimize (did it on linux too).
If anyone can explain me simple how to use the binary kernel, I am happy too for now, if that makes me able to compile CM7
Click to expand...
Click to collapse
It's not quite that simple. They don't just 'mod' the kernel, they add device support to it. The upstream Linux kernel does not support the latest and greatest Qualcomm-based devices, so HTC uses their own repository based on Codeaurora (http://www.codeaurora.org) which is downstream from Qualcomm. Confused yet?
Point being: Linux will not run properly on our device until we have either the HTC Sensation source, Doubleshot source, or someone sifts through and pieces together all of the various sources needed from Codeaurora.
To use the binary form, just use boot.img from our device's HBOOT image.

nbetcher said:
It's not quite that simple. They don't just 'mod' the kernel, they add device support to it. The upstream Linux kernel does not support the latest and greatest Qualcomm-based devices, so HTC uses their own repository based on Codeaurora (http://www.codeaurora.org) which is downstream from Qualcomm. Confused yet?
Point being: Linux will not run properly on our device until we have either the HTC Sensation source, Doubleshot source, or someone sifts through and pieces together all of the various sources needed from Codeaurora.
To use the binary form, just use boot.img from our device's HBOOT image.
Click to expand...
Click to collapse
Thank you for the explanation.
I have been compiling kernels on linux, I know we need drivers and that HTC patches the kernel. I did not know about codeaurora, thanks .
The HTC Sensation kernel source is on the HTC website:
http://developer.htc.com
I was wondering undead, how do you compile other ROMS? You just strip what is not needed? I thought you know how tot strip just the kernel, since you made a senseless rom.
I will try using the boot.img, thanks.
Does that mean porting a Sense rom would only require swapping the boot.img from another Sense 2.0/3.0 rom?
Thanks for the info

LOL. No its still the sense base and uses the stock boot.img from the stock ROM. It's still HTC at its core. Like I said I know 0 'zero' about kernels.
Sent from my MyTouch 4G Slide using xda premium

Undeadk9 said:
LOL. No its still the sense base and uses the stock boot.img from the stock ROM. It's still HTC at its core. Like I said I know 0 'zero' about kernels.
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
point taken . I think I just made a working zip containing only the stock kernel.
If I have time, I will try to put that kernel in a AOSP rom for the Sensation and see what that does. may take some time...

does any1 know how to mod the device checking of a rom?
i get an error 7, found it is because of the device check.
I modded the update script and binary from the Senation Alpha cm7 and got that error, which seems to point to a different model of phone.
I would like to work around it and see if the kernel works with cm7

Quick question on kernel compiling NS4G

Hey, I just got a quick question
When compiling a CM7 kernel for the NS4g, do i use samsung-kernel-crespo or is there a samsung-kernel-crespo4g? thats all i need to know =]

Crespo4g
Sent from my HTC Sensation 4G using XDA App

mathkid95 said:
Crespo4g
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
ok, thanks =]
PS. Not seeing Crespo4G in the CM github? and git is still down right? where can i get a clean source? (lol, i gues i have one other question XP)

Well on the gingy source I do
lunch
Then select crespo.but for u its 4g haha
Sent from my HTC Sensation 4G using XDA App

mathkid95 said:
Well on the gingy source I do
lunch
Then select crespo.but for u its 4g haha
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
ok, so its done similar to building the CM7 rom then? Havent worked with CM source in a while, been using the Samsung sources for my vibrant =P

I have never built cm7 in my life lol
I do know its "bacon"
But just look up building cm7 on Google and the wiki page it comes up with rocks
Sent from my HTC Sensation 4G using XDA App

For cm I do
. build/envsetup.sh && brunch crespo4g

snandlal said:
For cm I do
. build/envsetup.sh && brunch crespo4g
Click to expand...
Click to collapse
Ok, I was under the impression that was how to build CM7 itself. For the kernel is it the same? Or do I need to search for a copy of the source from before git got hacked....with the vibrant I could just DL the source from supercurio or Samsung {when I first started working on it}, with NS4g Idk... I'm assuming crespo kernel source won't work, but then again I haven't worked with the nexus phones ever so idk.
Sent from my SGH-T959 using Tapatalk

This is the correct kernel source for nexus s and 4g. It produces the zImage. zImage + Ramdisk = boot.img
https://github.com/CyanogenMod/samsung-kernel-crespo
The commands are:
export PATH=$PATH:/home/YOUR LINUX USERNAME/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/ (You can put this command in bash.rc so you don't have to type it everytime you compile)
make ARCH=arm herring_defconfig (This command writes the herring_defconfig in configs)
make -j4 ARCH=arm CROSS_COMPILE=arm-eabi- (This command actually produces the zImage)

snandlal said:
This is the correct kernel source for nexus s and 4g. It produces the zImage. zImage + Ramdisk = boot.img
https://github.com/CyanogenMod/samsung-kernel-crespo
The commands are:
export PATH=$PATH:/home/YOUR LINUX USERNAME/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/ (You can put this command in bash.rc so you don't have to type it everytime you compile)
make ARCH=arm herring_defconfig (This command writes the herring_defconfig in configs)
make -j4 ARCH=arm CROSS_COMPILE=arm-eabi- (This command actually produces the zImage)
Click to expand...
Click to collapse
thanks =] I just needed the source and i wasnt sure if that was for both (i know how to compile it ^^)
PS. to anyone who comes across this thread, you can just edit the makefile so you dont have to type all that =]

ok...well I'm at a loss here....compiled the kernel like normal and installed using the anykernel script and i cant get the kernel I compile to boot. Even if I just compile the kernel source with no changes it doesnt boot.....any ideas? =/ i cant find any reason for it to not boot. Its got no changes from the CM keel source and all i did was compile it and merge it into he boot.img
(never had problems on SGS kernels =3)
EDIT: may also be tat my keyboard isnt working properly.....typos can cause a few problems =3...will check

[Q] Cant Get custom kernel to boot [SOLVED]

I've built it like I've always built my 2.3 kernel and I cant even get a stock kernel I compile to boot
you guys think it might be my CC? I've been using Sourcery G++ Lite 2011.03-42 for ARM EABI for a year almost and hasnt had any problems
I'm using supercurios kernel source also btw
any ideas?

ECOTOX said:
I've built it like I've always built my 2.3 kernel and I cant even get a stock kernel I compile to boot
you guys think it might be my CC? I've been using Sourcery G++ Lite 2011.03-42 for ARM EABI for a year almost and hasnt had any problems
I'm using supercurios kernel source also btw
any ideas?
Click to expand...
Click to collapse
"adb shell cat /proc/kmsg" output while it's trying to boot may be helpful.

I don't even get to that point, stops at Google logo and gives me nothing
PS I'm building for ICS (forgot to mention that)
Sent from my Nexus S 4G using Tapatalk

I'm not really sure. I have built from supercurio's source so I know it's not that.
Are you using this source (https://github.com/project-voodoo/linux_samsung)
Are you on the correct branch?
Have you made any changes?
Are you fastbooting the boot.img or using the anykernel script?

Hostile89 said:
I'm not really sure. I have built from supercurio's source so I know it's not that.
Are you using this source (https://github.com/project-voodoo/linux_samsung)
Are you on the correct branch?
Have you made any changes?
Are you fastbooting the boot.img or using the anykernel script?
Click to expand...
Click to collapse
No changes
Same source
Correct branch
Any kernel script
Only thing I haven't changed is CC =\
Sent from my Nexus S 4G using Tapatalk

ECOTOX said:
No changes
Same source
Correct branch
Any kernel script
Only thing I haven't changed is CC =\
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I have only ever used the one google supplies so I would say try that. It's the only thing I can think of

Hostile89 said:
I have only ever used the one google supplies so I would say try that. It's the only thing I can think of
Click to expand...
Click to collapse
Me too...I'll give a diff CC a try
Sent from my Nexus S 4G using Tapatalk

Solution
it was the CC, i used the default one and it worked.
apparently according to Ezekeel you need to add -mno-unalligned-access to the kbuild flags for the newer TC from CS
so if your using code sourcery add that to the build flags or just use the default toolchain

[Q] Compiling Kernel - Help

Hi all,
I wanted to try to compile my own kernel for my HTC but I'm kinda stuck...
I'm following this tutorial (sry for spaces, can't post link) wiki. cyanogenmod. com/wiki/Building_Kernel_from_source#Download_Kernel_Source_Code
but the kernel source seems broken, I had to fix two files
Code:
# modified: arch/arm/mach-msm/acpuclock-7x30.c
# modified: arch/arm/mach-msm/acpuclock.h
and now I'm getting this error:
Code:
make[1]: *** No rule to make target `arch/arm/mach-msm/board-surf7x30.o', needed by `arch/arm/mach-msm/built-in.o'. Stop.
make: *** [arch/arm/mach-msm] Error 2
Can anyone guide me a bit? Also should I take CyanogenMod Kernel source or the one from htcdev? Whats the diference?
Any help appreciated
Thanks

Add a line for board-surf7x30.o in /arch/arm/mach-msm/Kconfig along with others
Sent from my HTC Desire S

amidabuddha said:
Add a line for board-surf7x30.o in /arch/arm/mach-msm/Kconfig along with others
Sent from my HTC Desire S
Click to expand...
Click to collapse
You mean I should add a block for the board-surf7x30.o and then disable it when running the config so it don't get compiled/touched at all?

So after disabling quite a few features I got the HTC kernel compiled, but flashing it on the phone just results in a blank screen - adb is working though.
The CM kernel still fails with
Code:
make[1]: *** No rule to make target `arch/arm/mach-msm/board-surf7x30.o', needed by `arch/arm/mach-msm/built-in.o'. Stop.
make: *** [arch/arm/mach-msm] Error 2
There is no board-surf7x30.c or .s and I can't change/disable the board type in the config... Is this a problem with the cm kernel? Also why are so many configurations not compiling - even on the official HTC kernel? It seems the makefile has entries for files that are missing. Shouldn't the kernel compile regardless of the configuration?

sciepy said:
So after disabling quite a few features I got the HTC kernel compiled, but flashing it on the phone just results in a blank screen - adb is working though.
The CM kernel still fails with
Code:
make[1]: *** No rule to make target `arch/arm/mach-msm/board-surf7x30.o', needed by `arch/arm/mach-msm/built-in.o'. Stop.
make: *** [arch/arm/mach-msm] Error 2
There is no board-surf7x30.c or .s and I can't change/disable the board type in the config... Is this a problem with the cm kernel? Also why are so many configurations not compiling - even on the official HTC kernel? It seems the makefile has entries for files that are missing. Shouldn't the kernel compile regardless of the configuration?
Click to expand...
Click to collapse
If you link me the source I will take a look
EDIT: are you trying to compile another device's kernel for saga? If so it will deffinately not work.
If you want a kernel for CM7 this is the source that you can use.
For CM9 and CM10 ther is no stable kernel ATM, but for CM10 you can take Andromadus source as a base.
For Sense just download the source (Android 2.3 or 4 whichever you need) from HTCdev.com, they are ready to compile
But you you want only to overclock there are already such kernels made by others for Desire S. You can find them in the INDEX thread

amidabuddha said:
If you link me the source I will take a look
EDIT: are you trying to compile another device's kernel for saga? If so it will deffinately not work.
Click to expand...
Click to collapse
Why is that? Because of the different devices/drivers?
The arm/mach-xxx folders are for the different chipsets, msm beeing the one of the saga, right?
I was building this one: github.com/CyanogenMod/cm-kernel
amidabuddha said:
If you want a kernel for CM7 this is the source that you can use.
For CM9 and CM10 ther is no stable kernel ATM, but for CM10 you can take Andromadus source as a base.
For Sense just download the source (Android 2.3 or 4 whichever you need) from HTCdev.com, they are ready to compile
Click to expand...
Click to collapse
Ok cool, thanks! Gonna play with those a bit, the CM7 kernel seems to compile so far
amidabuddha said:
But you you want only to overclock there are already such kernels made by others for Desire S. You can find them in the INDEX thread
Click to expand...
Click to collapse
No, I want to compile it to kinda get an idea of how it works

Ok, compiled kernel is working for the CM7, I'll look into the newer roms the next days. Thanks for help!

[KERNEL] vz-oc-linaro kernel v4: CM10.1 overclocking kernel - Linaro build

Introduction
This is a replacement kernel for CyanogenMod 10 and 10.1 evita builds. The kernel is designed to be as close as possible to the stock CyanogenMod kernel with a few improvements.
Linaro toolchain:
The kernel is compiled with the latest Linaro toolchain based on gcc 4.7 rather than the default Android toolchain. This may provide performance improvements in some situations. I have made a few patches applied to make it compatible with gcc 4.7.
Overclock:
The highest frequency now available under Settings -> Performance with these kernels is,
Code:
CPU: 1782 MHz 1.25 V
L2: 1350 MHz 1.15 V
BUS: 532 MHz
I've also included a modified thermald.conf in the flashable zip.
Refresh rate:
I've reverted the refresh rate to the original value from the sense source code (57 Hz). This works better when "Disable HW overlays" is selected.
Downloading and installing
Download the flashable zip,
cm10.1_vz-oc-linaro.4.zip MD5=7233ccffa17fa16a2dc6292ecf755fb4
mega.co.nz
ubuntuone.com
Older versions:
cm10.1_vz-oc-linaro.3.zip MD5=5e0efdfd0390f3f923090a574d142808
mega.co.nz
ubuntuone.com
cm10.1_vz-oc.2.zip MD5=cf2c4ee8ba09627e598b78dcea225d39
cm10.1_vz-oc-linaro.2.zip MD5=2931cc59515949fa461a89ea17c99328
vz-oc.1.zip MD5=2f1740d67cd1d5c02a7ac5489bafe7a0
vz-oc.2.zip MD5=4e4d444130e8eb71c27cc23fed65fc88
vz-oc-linaro.1.zip MD5=ca674641e05595e64698afda8aa02943
vz-oc-linaro.2.zip MD5=2b01472d00e069c53f934c30b49475d1
cm10.1_vz-oc.1.zip MD5=576db9e99b2289dae7fc5b548a0d61b4
cm10.1_vz-oc-linaro.1.zip MD5=1a5f3b50608e6b44da50829b2c04ec5c
If you have HBOOT earlier than 1.14 or have S-OFF, then you can just flash the zip from recovery. This will flash the kernel as well as all required modules and thermald.conf. Otherwise, HBOOT 1.14 users will need to extract the boot.img, enter bootloader mode and run
Code:
fastboot flash boot boot.img
Then you will also need to flash the zip to get modules and themald.conf.
Compatability
cm10.1_vz-oc-linaro.4 is compatible with CM10.1 UNOFFICIAL build from 16/04/2013 onwards.
cm10.1_vz-oc-linaro.3 is compatible with CM10.1 NIGHTLY build from 01/03/2013 onwards.
cm10.1_vz-oc.2 (and linaro) are compatible with CM10.1 NIGHTLY build from 19/02/2013 only.
cm10.1_vz-oc.1 (and linaro) are compatible with CM10.1 UNOFFICIAL build from 06/02/2013 only.
vz-oc.2 (and linaro) are compatible with CM10 NIGHTLY builds from 26/12/2012 to 13/01/2013.
vz-oc.1 (and linaro) are compatible with CM10 NIGHTLY builds from 28/11/2012 to 25/12/2012.
Future development
I hope to introduce GPU overclocking soon and there will be updated builds as
soon as changes come into the main CyanogenMod repo.
Building the kernel
For those who would like to build the kernel themselves, here are some basic
instructions. First you will need to acquire some tools. You can get the default
toolchain from the CM10 source code at,
Code:
system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/
Otherwise, if you want to use the Linaro toolchain, you can get it at
Linaro toolchain
You will also need a working boot image to get the ramdisk from. You can build
mkbootimg using these instructions
building mkbootimg
Finally, you can get split_bootimg_pl from William Encks site
download split_bootimg_pl
Clone the repo and change to your desired branch
Code:
git clone https://github.com/vanja-zecevic/android_kernel_htc_msm8960.git
git checkout jellybean-oc
Now export an environmental variable pointing to your desired toolchain
Code:
export CCOMPILER=$PATH_TO_TOOLCHAIN/bin/arm-eabi-
Copy the config file, run menuconfig once and start the build replacing -j12
with your desired number of threads
Code:
cp ./config-oc ./.config
make ARCH=arm SUBARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
make ARCH=arm SUBARCH=arm CROSS_COMPILE=$CCOMPILER -j12
Extract a ramdisk from a working boot image and repack with your freshly built
kernel using the following command for cm10,
Code:
./split_bootimg_pl ./boot.img
./mkbootimg --base 0x80400000 --ramdiskaddr 0x81800000 \
--cmdline 'console=ttyHSL0,115200,n8' \
--kernel arch/arm/boot/zImage --ramdisk boot.img-ramdisk.gz \
-o boot_vz-oc.img
cm10.1 will need the following cmdline
Code:
--cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom'
You are ready to flash your new kernel!
Contact
I hope you enjoy using this kernel! Please also visit the github page for this project for alternative download links and for the source code.
GitHub
Cheers,
Vanja

Looks good will give it a shot next time I'm on a CM10 based ROM. Will this only work on CM10 or will it work with other AOSP builds too?
Sent from my HTC One X using Tapatalk 2

1. Could you post flash able zips for the majority of us who can flash these in recovery?
2. Very few users including myself have issues with kernels without stock voltage values. The device will just not boot, any way to have separate versions without different voltages just to rule that issue out when people ask why their device won't boot?
Sent from my One X using Tapatalk 2

superchilpil said:
1. Could you post flash able zips for the majority of us who can flash these in recovery?
2. Very few users including myself have issues with kernels without stock voltage values. The device will just not boot, any way to have separate versions without different voltages just to rule that issue out when people ask why their device won't boot?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
+1 thank you
Straight talked from my HOX!

I like the idea of a stockish CM10 OC kernel, Me myself i underclock. I would give this a go see how it holds up. the increase in clock speed is usually a nice thing to have even if not used. Also a 2.0GHz version would be awesome too.

Nice job!
Sent from my Nexus 7

ChummyDays said:
Fastboot flash boot boot.img
Sent from my One X using Tapatalk
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Re read my post, I know how to use fastboot
Sent from my One X using Tapatalk 2

Thanks for the feedback people!
I'm currently running HBOOT 1.14, so I will need to downgrade to 1.09 before I can make/test flashable kernel zips. I think I will get around to this in the next week.
I will also look into some other requests.
Is anyone running the kernel? Are you happy with it? Any benchmarks?

rohan32 said:
Nice job!
Click to expand...
Click to collapse
Thanks Rohan, I was inspired by your work!

Quick question: Sweep2Wake support?
I know OP stated 'as close to stock as possible,' searched thread for 'sweep' and turned up nuffin, so I'm just curious. Glad to see another kernel option (and prospective CM10 material!).

superchilpil said:
1. Could you post flash able zips for the majority of us who can flash these in recovery?
2. Very few users including myself have issues with kernels without stock voltage values. The device will just not boot, any way to have separate versions without different voltages just to rule that issue out when people ask why their device won't boot?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I don't plan on maintaining them, but if newer versions come out, just rename to boot.img and swap out the file in the zips:
With Linaro toolchain
without Linaro toolchain
Vanja, if you want these gone, let me know.

hands on CM boot screen animation
running stable build cm10, and like the title says, hangs on boot screen animation. Do you have to configure the thermald.conf first?
thanks

taylor.fowler said:
I don't plan on maintaining them, but if newer versions come out, just rename to boot.img and swap out the file in the zips:
Click to expand...
Click to collapse
Thanks Taylor! I've included zips now.

nespid said:
running stable build cm10, and like the title says, hangs on boot screen animation. Do you have to configure the thermald.conf first?
thanks
Click to expand...
Click to collapse
Hi nespid, unfortunately, these kernels currently only support builds from 28/11/2012 onward. I've re-written the "Compatibility" section to make that more clear.
I will put up a build compatible with the "stable" build in a few days if you like.

vanja_z said:
Hi nespid, unfortunately, these kernels currently only support builds from 28/11/2012 onward. I've re-written the "Compatibility" section to make that more clear.
I will put up a build compatible with the "stable" build in a few days if you like.
Click to expand...
Click to collapse
That would be absolutely great!
Thank you!
Sent from my HTC One X+ using xda app-developers app

just wondering ,when and if are you goin make one for cm10.1? because the one for cm10 just flatout smokes :good! really makes your phone move!! :good:

Re: [KERNEL] vz-oc kernel: CM10 overclocking, normal & Linaro builds
Any feedback on battery life with this one? And how does it play with No Frills CPU and such?
Thanks for the hard work!
Sent from my CM10ified Beast (a.k.a. HTC One XL)

I've put up cm10.1 kernels!
ps. cm10.0 stable kernel is coming soon, I haven't forgotten, sorry for the delay

vanja_z said:
I've put up cm10.1 kernels!
ps. cm10.0 stable kernel is coming soon, I haven't forgotten, sorry for the delay
Click to expand...
Click to collapse
That's awesome, I will be testing this soon. I know it was asked before but I'm also very interested to know, any plans on implementing sweep2wake? After using it for even a little bit it spoils you, it really is an awesome feature. Otherwise thank you for your hard work, I'll leave feedback in a couple days after testing!

Thanks much, got the kernel running on CM10.1 with 1.14 hboot no problems. Modified thermald.conf and seems to allow oc to stick thus far.
great work,
dbd
UPDATE: this kernel is working wonderfully with cm10.1. +1 for linaro toolchain.