Database Info

[KERNEL] TigerTael's 32A Magic/Sapphire kernel patch [Updated 9th Oct]

This thread is for my personal kernel patches that I use to patch the main android kernel source to be able to build a working kernel for 32A Magic/Sapphire devices. Various people have chipped in during the development of this, please see the old thread for details.
The old dev thread is located here: http://forum.xda-developers.com/showthread.php?t=548061
Who is this for?
Anyone that builds kernels for HTC 32A Magic/Sapphire devices and has experience patching, configuring and building kernels for the ARM architecture. This thread is not intended as a guide for beginners.
Please do not ask how to build a kernel or how to configure a kernel.
Why?
It is true that HTC have released their kernel sources here, but one would have to use this exact source and would be unable to simply build a patch to make a 2.6.29 kernel due to the numerous differences in the HTC kernel source. One could not also just rely on pulling a new kernel snapshot from the main GIT tree. This patch intends to patch the kernel from the main msm branch with as little changes as possible.
What do you need?
Get the latest snapshot here (currently c7f8bcecb06b937c45dd0e342450a3218b286b8d.tgz)
Do not try and patch HTC's Kernel Source.
Notes:
For the time being, this patch works properly for both 2.6.27 and the 2.6.29 branch.
You will not be able to build kernels for 32B devices after you use this patch. Please keep a separate copy of your kernel for 32B devices.
[NEW] Built a 2.6.29 kernel from cyanogens /proc/config.gz, everything seems to be working fine.
The Files:
Kernel Patch 2.6.27 TT V3
Example Kernel:
32A Cyanogen 2.6.29 (v4.0.4 - stable version, updated 8/28) with wlan.ko - ONLY FOR USE WITH 4.0.4 CYANOGEN ROM (Cyanogen contains extra modules on his ROM for this kernel)
There seems to be a bug in 4.0.4 ROM where wifi tethering is not working. I have reverted back to 4.0.3 with the above kernel and all is working fine including tethering.
32A Cyanogen 2.6.29 (v4.1.1) with wlan.ko - ONLY FOR USE WITH 4.1.1 CYANOGEN ROM (Built from cyanogen github w 4.0.4 config)
Multi-touch is working in the browser.
32A Cyanogen 2.6.29 (v4.1.5) with wlan.ko - ONLY FOR USE WITH 4.1.5 CYANOGEN ROM (Built from cyanogen github w/4.1.5 config)
Cyanogen says he will be changing the scheduler to BFS soon.
32A Cyanogen 2.6.29 (v4.1.6) with wlan.ko - ONLY FOR USE WITH 4.1.6 CYANOGEN ROM (Built from cyanogen github w/4.1.6 config)
Includes BFS scheduler. Wow, browser flies.
32A Cyanogen 2.6.29 (v4.1.7) with wlan.ko - ONLY FOR USE WITH 4.1.7 CYANOGEN ROM (Built from cyanogen github w/4.1.7 config)
Haven't really tested this completely but seems fine.
32A Cyanogen 2.6.29 (v4.1.8) with wlan.ko - ONLY FOR USE WITH 4.1.8 CYANOGEN ROM (Built from cyanogen github w/4.1.8 config)
Camera working, Camcorder not working.
32A Cyanogen 2.6.29 (v4.1.9.2) with wlan.ko - ONLY FOR USE WITH 4.1.9.2 CYANOGEN ROM (Built from cyanogen github w/4.1.9.2 config)
Everything appears to be working properly
32A Cyanogen 2.6.29 (v4.1.11.1) with wlan.ko - ONLY FOR USE WITH 4.1.11.1 CYANOGEN ROM (Built from cyanogen github w/4.1.11.1 config)
Everything appears fine.
ROM boot images:
V2.1 eViL hero 2.9.5x (2.6.29, BFS, SLUB) 32A only (apply as update) - THIS IS EXPERIMENTAL. Any bugs, let me know.
Bluetooth,Wlan,Gps - working. (Not sure about headset but bluetooth turns on)
Graphic intensive apps - Working (Armadillo roll works, Gears gets 60fps)
Camera working this time
eViL hero 2.9.9 (2.6.29, SLUB, Anticipatory) 32A only (apply as update)
Seems to work properly!
Hero Volume Fix:
Hero Volume Fix (tested on eViL Hero) (Do a backup first and then test) -- Apply as update
Disclaimer:
These patches are experimental and should not be used for mission critical operations without extensive testing. I nor anyone else, will be held responsible for the use of these patches. If any damage or loss is experienced due to these patches, these are at your own risk. You will not be reimbursed by anyone for any amount what-so-ever.

Changelog:
V3
Added comments to changed values - may help to find errors in the future.
Changed Makefile.boot back to V1 to be the same as official HTC Source - (initrd_phys-y := 0x19A00000)
Changed EBI_SIZE to the same size as the HTC released kernel source.
Changed VMALLOC to the same size as the HTC released kernel source.
V2
Changed Makefile.boot - changed to initrd_phys-y := 0x1A200000 (credit to rayman84)

Great work. Looking forward to this.
I will have to learn how to compile a kernel now.

Tigertael..in the prevous thread u said..
Bluetooth and led working..
* SDCard
* Memory - (All memory)
* Camera - (Special thanks to zinx @ Freenode!)
* GPU1 - (Pretty sure this is right)
* ADSP - (Pretty sure this is right)
* MDP - (Untested)
* LED's - working fine.
* GPS -working fine.
* Bluetooth - working fine.
* WLAN - Working 100%
Click to expand...
Click to collapse
Does this mean if a Hero Cooker use this kernel then Bluetooth and Led Problem will be fix?

lesjaw said:
Tigertael..in the prevous thread u said..
Bluetooth and led working..
Does this mean if a Hero Cooker use this kernel then Bluetooth and Led Problem will be fix?
Click to expand...
Click to collapse
Unfortunately no. That was running on a stock ROM, not a Hero ROM.
The problem with Hero is the binaries that it was built upon was meant purely for the Hero. It's not known currently if you can correct this with a kernel, although I suspect you might be able to but only with the Hero sources for the kernel.
Even then it's a mission.

lesjaw said:
Tigertael..in the prevous thread u said..
Bluetooth and led working..
Does this mean if a Hero Cooker use this kernel then Bluetooth and Led Problem will be fix?
Click to expand...
Click to collapse
This means that bluetooth and the leds work correctly with a cupcake based rom. The Hero roms still have issues which will probably only be resolved when (if) the Hero source is released.

What in Cyanogen's kernel is working?
If multitouch is finally working, I love you

WaterMan! said:
What in Cyanogen's kernel is working?
If multitouch is finally working, I love you
Click to expand...
Click to collapse
I didn't even know Cyanogen had multitouch capable apps in his ROM.
If he does, he might've had to use kernel patches of his own and if this is so, he hasn't shared them with me.

Name display
How it s possible to add a caller name display in the rom as we know fido and rogers support this option thanks

roriii said:
How it s possible to add a caller name display in the rom as we know fido and rogers support this option thanks
Click to expand...
Click to collapse
This is a paid carrier feature, nothing to do with the ROM.
Clinton

TigerTael said:
I didn't even know Cyanogen had multitouch capable apps in his ROM.
If he does, he might've had to use kernel patches of his own and if this is so, he hasn't shared them with me.
Click to expand...
Click to collapse
I think the multitoch is more from some Android changes than kernel's , I read somewhere that The Kernel has already multitouch enabled, I fyou recall, it worked fine with Hero ROMs and stock kernel for Magic.

shwan_3 said:
I think the multitoch is more from some Android changes than kernel's , I read somewhere that The Kernel has already multitouch enabled, I fyou recall, it worked fine with Hero ROMs and stock kernel for Magic.
Click to expand...
Click to collapse
I do recall and I'm inclined to agree with you.

TigerTael said:
I do recall and I'm inclined to agree with you.
Click to expand...
Click to collapse
I can't say that my stock Magic (Vodacom) had multitouch enabled... It is enabled in Hero roms but that is in someway due to the HTC closed-source framework. The Magic (and Dream) kernels had no specific way of interpreting multitouch data without a kernel hack or modified dalvikvm).
http://lukehutch.wordpress.com/2009/01/25/get-multi-touch-support-on-your-t-mobile-g1-today/

Not only does the framework/kernel have to support multitouch, but the applications too.

That's true

Hi, I'm using your kernel 2.6.29 (from Cyanogen) in the bcook's porting of Cyanogen 4.0.4 (http://forum.xda-developers.com/showthread.php?t=544854). It works great but I don't understand why the multitouch doesn't work. It requires support by both the applications and kernel: the Cyanogen's browser package has multitouch (all the Dream and Magic 32B people use it) and your kernel should inherit it.
How did you compile it? Did you use, as base, the original kernel by Cyanogen from his git repository? Did you use his config file?
Thanks.

Actually, multi-touch IS working on the new kernel I built for 4.1.1

TigerTael said:
Actually, multi-touch IS working on the new kernel I built for 4.1.1
Click to expand...
Click to collapse
Do you mean that it is not working with the browser package in 4.0.4 or that you rebuild/fixed the kernel just for 4.1.1?
Can you provide a kernel for Cyanogen 4.0.4 (stable) with a working multitouch? I would keep my phone on the stable releases of Cyanogen. Thanks.

You can use the 4.1.1 kernel with 4.0.4 and multi-touch should work fine as well as all your other features. HOWEVER, please note that I could not get tether working in 4.0.4 or 4.1.1.
I am using 4.0.3 with 4.1.1 kernel, tether works, etc.

I'm using the new kernel from 4.1.1 in my Cyanogen 4.0.4 (I don't care about tethering): multitouch works well in the browser. Do you know if in Cyanogen there are other applications that support multitouch? Gallery don't.
The next step is to unify the kernel with the official one by Cyanogen (with some kind of board recognition on the boot phase) so we can just use the same official image.
Thanks to all!

[PORT][EBI1/32A]WG-Build Y.R1 - 02/01/10

For Sapphire EBI1/32A users
All credits goes to Wesgarner and the people who his works based on.. (cyanogen etc.)
Original Thread: http://forum.xda-developers.com/showthread.php?t=592466
Now, the real stuffs-
EBI1 CFS Kernel (01/01/10): Here
EBI1 BFS Kernel (02/01/10): Here
Instructions
Nandroid BACKUP!
Wipe/Clear
Install WG Build Y R1 (thread link above)
Install EBI1 Port (link above)
Boot and wait~
Enjoy, folks!

Thanks your work

downloading the rom now.....great and thanks , mate!!
arctu said:
For Sapphire EBI1/32A users
All credits goes to Wesgarner and the people who his works based on.. (cyanogen etc.)
Original Thread: http://forum.xda-developers.com/showthread.php?t=592466
Now, the real stuffs-
EBI1 CFS Kernel (01/01/10): Here
EBI1 BFS Kernel (02/01/10): Here
Instructions
Nandroid BACKUP!
Wipe/Clear
Install WG Build Y R1 (thread link above)
Install EBI1 Port (link above)
Boot and wait~
Enjoy, folks!
Click to expand...
Click to collapse

Good work man, I'll try it!!

imho, it's one of the featured smoothest rom besides CM. try it with BFS kernel.

Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.

Thanks a lot for the hard work. Will try it out mate

no many issues so far, everything seems to work well.

arctu said:
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Click to expand...
Click to collapse
Thank you. this is just what I was looking for. I was using bcrook's CM port in earlier versions and was doing ok(only some FCs in the first boot).
and since build Y I can't user bcrook's port with app2sd and swap..maybe something to do with the new kernel.
I did post in that thread if there is a 32A port prior the release, but guess too many people are just too excited for the new release and overlooked my post..anyway
please don't discontinue it, I am sure many people will like to run WG build on their 32A Sapphire.
just wondering, I saw your other thread MAGIC Port, can we use that with ANY dream/32B ROM? and more importantly, is is stable? (I saw an big red ALPHA..)
if so, can we also use that with WG-Build?
so you can take a rest now, then?

arctu said:
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Click to expand...
Click to collapse
Thanks for porting, this rom seems sexy. Lol. Aniwae, pls continue! Since it would be great to have this rom widely used on 32A radios.

@haozheng91
MAGIC Port is stable actually.
But no, for WG Build and few other roms, even though it ports properly, it doesn't do a full port. For Cyanogen Mod, WG Build Y, Enomether etc. they use custom kernels. When you use my magic port, well, it does work, but it's not using the intended kernel which the ROM creator compiled.
But anyway, your problem was you're using CM Port over WG Build Y.. that's incorrect because of the different ramdisk (the rom init script). Hence the A2SD failed.
---
the rom is stable so far for me. i'm loving it and the smoothness.
so far, no FC. though, BFS does drain battery.

What's the difference between CFS & BFS?

multitouch
wipe
flash WG-Build Y.R1 - CFS with RAM Hack
flash wgbuildy_ebi1_signed.zip - CFS kernel
everything is going well, but multitouch doesnt work ...

BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Naturally, smoother UI but drains a little more battery.
@coltcha:
CFS somehow doesn't work. Try BFS. I'll recompile the kernel once wesgarner release another version.

Does this ROM include the radio image that will brick a 32A magic?

BFS drains more battery.. that's good to know.
if Cyanogen Mod and WG Build use different kernel, then what are some ROMs we can use your magic port? Cyanogen Mod is one of the most popular ROMs there..
what about any of the Eclair ROMs?
I have heard that BFS is supposed to be a little faster..but WG recommands CFS as BFS is not as stable or something.. as for the battery, I always have to recharge everyday, so can't really tell the difference between different ROM or kernel...

hikki2000 said:
Does this ROM include the radio image that will brick a 32A magic?
Click to expand...
Click to collapse
it doesnt.
@haozheng91
like i said, it'll work on any 32B roms.
it's just not a full port for cases of roms with custom kernel. so... if you go on to the dream forums, if the ROM dev say he compiled his own kernel... you will just not benefit from the custom kernel enhancement. that's all.
though, most of the time, the custom kernel isn't much of a benefit as they're usually just variants of existing kernels with different build configs. you'll also see that most devs tend to us CM kernel... especially eugene eclair roms and some senseui roms.

arctu said:
it doesnt.
Click to expand...
Click to collapse
So it is safe for me to flash the ROM and then apply your port file, with my current SPL and Radio? Thanks.

yes. it should be. but then again, flash at your own risk, i or the rom dev aren't responsible if you brick your phone.

arctu said:
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Click to expand...
Click to collapse
No No, buddy, please keep up your good work, we are glad to see the diversities.

[32A][6.35][Kernel][EXPERIMENTAL] Cyanogenmod 5 :: Doesn't work

For Cyanogenmod 5 test builds
Kernel version 2.6.29.6 ToastCFH
Following up this thread: http://forum.xda-developers.com/showthread.php?t=685613
Very experimental and untested at the moment. This kernel was new for GSM Hero, and I just tweaked the config a little bit because the GSM Hero kernel has had a history of being able to run on 32A Magics with new radio.
Radio 6.35 series is needed to boot this (in theory)
It would be same as this config without perflock: http://pastebin.com/cKkBNtKJ
Compiled wlan.ko using CM5 kernel and ROM sources
Packed via Koush Anykernel in case you want to experiment.
Threw in OC+UV for good measure. SetCPU would work if this thing even boots.
CONFIG_LOCALVERSION="-cyanogenmod" so that CM5 can even possibly boot?
Edit: It's up now

What are the OC freq? Btw gj

OC freq are not important at the moment. I would like to know if this even boots.
Basically no overclock unless explicitly enabled. That's the last thing I'm worried about right now.

xaueious said:
OC freq are not important at the moment. I would like to know if this even boots.
Basically no overclock unless explicitly enabled. That's the last thing I'm worried about right now.
Click to expand...
Click to collapse
will let you know in 5-10 minutes

no response on boot when flashed over test 6 on new radio ;(
no logcat either came through...

Can someone look at the .config and see if there might be anything wrong with it?
http://pastebin.com/cKkBNtKJ
For comparison:
Cursorsense config
http://github.com/cursordroid/HTC-CCR-Kernel/blob/master/kernel-2.6.27/CCR32A-0.2a-config
Unmodded GSM Hero .29 config:
http://github.com/toastcfh/CdMa-HeRoC-2.6.29/blob/master/.config

xaueious said:
Can someone look at the .config and see if there might be anything wrong with it?
http://pastebin.com/cKkBNtKJ
For comparison:
Cursorsense config
http://github.com/cursordroid/HTC-CCR-Kernel/blob/master/kernel-2.6.27/CCR32A-0.2a-config
Unmodded GSM Hero .29 config:
http://github.com/toastcfh/CdMa-HeRoC-2.6.29/blob/master/.config
Click to expand...
Click to collapse
maybe ask bcrook or pershoot to see if they have any input

I'll try this myself when I get a chance.
Doesn't look like there's anything missing...
Should at least get a logcat.

xaueious said:
I'll try this myself when I get a chance.
Doesn't look like there's anything missing...
Should at least get a logcat.
Click to expand...
Click to collapse
you forgot the eabi1 option for 32a

carz12 said:
you forgot the eabi1 option for 32a
Click to expand...
Click to collapse
Yeah, I think you're right, but that might not be the case for these kernels, depending on how they're originally designed to boot. It might have the EBI1=y config "implied" in the source already.
Worth a shot, but add these lines
CONFIG_MSM_AMSS_VERSION=6355
CONFIG_MSM_AMSS_VERSION_6355=y
CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1=y
in the kernel config.

Is mkbootimg offset the same for new radio as it was for the old one? Might give this kernel a shot later...

cursordroid said:
Yeah, I think you're right, but that might not be the case for these kernels, depending on how they're originally designed to boot. It might have the EBI1=y config "implied" in the source already.
Worth a shot, but add these lines
CONFIG_MSM_AMSS_VERSION=6355
CONFIG_MSM_AMSS_VERSION_6355=y
CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1=y
in the kernel config.
Click to expand...
Click to collapse
The EBI1 option was added by a community dev. I'm sure this isn't a config option right now.
The kernel boots on the GSM Hero already, so shouldn't it boot the same for 32A Magic? GSM Hero implies 256MB support.
Something else missing?
mkbootimg is same for these kernels. If we use Koush AnyKernel there's no need to even go there.
Cursordroid can you give us the gist of your experience with mixing GSM Hero ROMs on 32A new radio?

[REQ] superFroyo for 32a

superFroyo v2.8.2 guys please port these rom for 32a device

we hope they will and i believe they will

Did you bother asking the developer?

gonna take some time for this to happen lol

Binary100100 said:
Did you bother asking the developer?
Click to expand...
Click to collapse
I asked one giant_rider is testing with some kernel function of this rom. But I wish some developer patches (as bcrook) created a patch for old radios

flash the Rom
flash port

davidcal said:
flash the Rom
flash port
Click to expand...
Click to collapse
work ??????

fonsigno said:
work ??????
Click to expand...
Click to collapse
Perfectly well

Well I don't think anybody should do any special port for any G1/32B roms.
I you wish to flash any of the roms in g1 section, the only thing you need to do is flash one of pershoot/bcrook/dumfuq 32A kernels on top of it and it will work just fine. Just make sure you flash the correct kernel version according to the rom base CM version.

In my opinion there is not a significant benefit to porting SuperFroyo since we now have other Froyo roms (without sense ui) that....
(1) Run on 32a 3.22 and 6.35 radios
(2) Have JIT working
(3) Have overclock kernels available up to ~700+ MHz
(4) Have Spareparts, CyanogenMod Settings and SetCPU for tweaking rom performance
These roms can now easily get 4.0-5.0 in Linpack and are stable.
Out of curiousity, I ported SuperFroyo a few days ago. The performance tweaks in SupSetup were not capatible with the .32 Sanpei kernel that was available for the 32a 6.35 radio at the time I did the port. We recently have the .34 kernel for the 32a 6.35 radio (thanks to carz12 and Switch33). I will update the ported SuperFroyo with the .34 kernel for the 32a 6.35 radio tonight or tomorrow hopefully. I don't think the result will be better than the other Froyo roms we have now, but I am happy to post a link if people want it.

thank you brother giant_rider for your hard work to give us the happiness
thanks you again giant

giant_rider said:
In my opinion there is not a significant benefit to porting SuperFroyo since we now have other Froyo roms (without sense ui) that....
(1) Run on 32a 3.22 and 6.35 radios
(2) Have JIT working
(3) Have overclock kernels available up to ~700+ MHz
(4) Have Spareparts, CyanogenMod Settings and SetCPU for tweaking rom performance
These roms can now easily get 4.0-5.0 in Linpack and are stable.
Out of curiousity, I ported SuperFroyo a few days ago. The performance tweaks in SupSetup were not capatible with the .32 Sanpei kernel that was available for the 32a 6.35 radio at the time I did the port. We recently have the .34 kernel for the 32a 6.35 radio (thanks to carz12 and Switch33). I will update the ported SuperFroyo with the .34 kernel for the 32a 6.35 radio tonight or tomorrow hopefully. I don't think the result will be better than the other Froyo roms we have now, but I am happy to post a link if people want it.
Click to expand...
Click to collapse
Hey giant_rider, I want link.
Thanks

giant please post the link

Here is a link to a ported SuperFroyo rom.
It is running Sanpei's .32 kernel for 32a 6.35 radio.
Some of the features in SupSetup are not enabled because they are not compatible with the kernel the way it is set up.
http://rapidshare.com/files/408904656/SuperFroyo2.4_32a_NR_v0.2.zip.html
I have been unable to get this rom to boot properly using the carz / switch .34 kernel. You can try flashing that kernel over this rom from recovery if you like. I think all of the settings in SupSetup could be enabled with the .34 kernel.
I am still sceptical whether this rom will be any better than the ones we have for 32a 6.35 or 3.22.
For a fast lite rom, I suggest you try flashing Switch's Fusebox Froyo, then install SetCPU and up the max CPU to 652 or 691 MHz. I did this tonight and got linpack of 4.6 and my phone is stable.

giant_rider,
Thanks

[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