Hi guys,
I'm trying to build a Cyanogen's kernel source (eclair branch) for JAC's xROM.
This ROM has all the bits and pieces necessary for NCommander's camera fix to work, and on my 32B Dream, the camera works just fine with the 32B rom from JAC.
However, I want to use the rom on my 32A Sapphire, so I'm building my own 32A kernel, mashing that with JAC's ramdisk, and hoping to get a working device.
Here's where I'm up to. My build environment is all set up, I've sync'ed Cyanogen's kernel sources from his GIT, and pulled a working kernel config so that I can (theoretically) compile a kernel with the same options etc.
The build works just fine, and spits out a zImage which I can (with mkbootimage) combine with a ramdisk to make a boot.img, which I can flash to my boot partition on teh Sapphire and it works just fine.
Except the camera doesn't work. The screen just goes black and nothing happens.
I found a working 2.1 AOSP kernel ported to 32A, and by coincidence, it happened to be a Cyanogen build - 2.6.29.6-cm42. Using that kernel, and JAC's ramdisk, the device boots, and the camera works. It's this kernel that I extracted the kernel config from to build my own kernel.
I figured same config, same source tree, should result in same (or similar enough) kernel so the camera would work on my build too. But it doesn't.
Does anyone have any advice on how to build Cyanogen's eclair kernel so that Ncommander's camera fix will work?
Desperately seeking advice - this is really annoying me!
reply here, twitter me, or IM me - I'm on gtalk too if you're available for a quick chat there. just let me know and i'll PM you my gtalk address.
So, 94 people have viewed this and no one has any ideas?
Come on folks. There are devs out there using Cyanogen's kernel on Eclair builds, and the camera is working. Surely someone can spare me a minute or two to offer some advice on where my kernel build might be going wrong.
If anyone has downloaded the kernel source from Cyanogen's git hub (the eclair branch, in particular) and successfully used a kernel they've build on an eclair rom with working camera, I'd be really grateful if you could share the process you've followed, just so I can work out where I've gone wrong.
This is, after all, a development forum. Surely someone knows how to do this ...
patience young skywalker
apacheo said:
So, 94 people have viewed this and no one has any ideas?
This is, after all, a development forum. Surely someone knows how to do this ...
Click to expand...
Click to collapse
Well thats been an issue for a long time now, there are peolple who know and they might have even seen this thread. Unfortunately they dont care enough to help, even if this is development. I was one of those 94 views, wish I could help. Nobody is willing to help teach people make their own software.
bubonik said:
Unfortunately they dont care enough to help, even if this is development. I was one of those 94 views, wish I could help. Nobody is willing to help teach people make their own software.
Click to expand...
Click to collapse
You know, it really does seem that way.
I've asked respected devs on twitter, and not ONE OF THEM has bothered to respond.
The only advice I've had was from bcrook88, and to his credit, he didn't have much experience in building eclair kernels. At least he took the time to have a bit of a chat to see if he could help.
That's more than anyone else has offered.
It's really sad.
Even the iPhoney community is more accepting.
apacheo said:
It's really sad.
Even the iPhoney community is more accepting.
Click to expand...
Click to collapse
Yup you'll get better help and support than in a open-source community which is terrible. Asking for things from some devs is like trying to walk on water.
I dont know but maybe this can help you:
http://forum.xda-developers.com/showthread.php?t=566235
dawg, just don't worry about it.
Asswipe44 said:
dawg, just don't worry about it.
Click to expand...
Click to collapse
Easy to say - but I want a working camera, damnit
fetch AOSP from android.git. checkout eclair. fetch vendor/htc/dream-open, vendor/htc/sapphire-open, and hardware/msm7k from ncommander's gitorious. checkout origin/eclair. copy recursive libaudio* from AOSP hardware/msm7k to the new hardware/msm7k directory, replacing what is there. your fetching ncommander's source so you have a reference point for future use.
(assuming your using an x86 host and bash/ksh)
export CCOMPILER=PATH_TO_AOSP_SOURCE/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
fetch 2.6.29.6 'donut' kernel source.
copy your boot.img to the root of the kernel source dir.
scripts/extract-ikconfig boot.img >.config
make ARCH=arm CROSS_COMPILE=$CCOMPILER oldconfig
make clean; make ARCH=arm CROSS_COMPILE=$CCOMPILER
make ARCH=arm CROSS_COMPILE=$CCOMPILER INSTALL_MOD_PATH=./out/modules/ modules_install
(get squashfs-tools package)
cd out/modules
mksquashfs . ../modules.sqf -noappend
cd ../../
fetch this and unpack it:
http://android-dls.com/files/linux/split_bootimg.zip
./split_bootimg.pl boot.img
cp arch/arm/boot/zImage ./
(this util and more are found after you build AOSP, within out/host/linux-x86/bin)
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel zImage --ramdisk boot.img-ramdisk.gz -o boot-new.img
you can flash boot-new.img to boot and push modules.sqf to system/modules
your camera should work now with the hacked in drivers.
-pershoot
pershoot said:
fetch 2.6.29.6 'donut' kernel source.
...
your camera should work now with the hacked in drivers.
Click to expand...
Click to collapse
the donut branch, and not eclair? I've been trying with eclair, with no luck.
i'll try following these instructions and see how i go - i've been doing 90% of this, so i'll see how i go.
thanks so much for explaining it all. even if I have worked out most of this, seeing it black and white at least gives me a reference!
apacheo said:
the donut branch, and not eclair? I've been trying with eclair, with no luck.
i'll try following these instructions and see how i go - i've been doing 90% of this, so i'll see how i go.
thanks so much for explaining it all. even if I have worked out most of this, seeing it black and white at least gives me a reference!
Click to expand...
Click to collapse
ncommander's reverse engineered magic is based off of the donut kernel, 2.6.29.6 revision. they will not work if you use eclair (the msm_camera bits also will not build when using cm-kernel eclair branch, and need to be commented out), and or will not work out of the box with 2.6.32 (as an example).
pershoot said:
ncommander's reverse engineered magic is based off of the donut kernel, 2.6.29.6 revision.
Click to expand...
Click to collapse
well fsck.
i probably should have figured that out
my kernel's finished building now - i'll squishing up the modules etc. fingers crossed!
Alright its booted...
Here goes the Camera test...
OOO YEAH
pershoot, you rock.
Alright its booted...
Here goes the Camera test...
OOO YEAH
pershoot, you rock.
enjoy
-pershoot.
apacheo said:
the donut branch, and not eclair? I've been trying with eclair, with no luck.
i'll try following these instructions and see how i go - i've been doing 90% of this, so i'll see how i go.
thanks so much for explaining it all. even if I have worked out most of this, seeing it black and white at least gives me a reference!
Click to expand...
Click to collapse
haha yes, eclair branch still doesnt have its own camera persay
the camera we have on eclair is "hacked" like people said, from my understanding (please correct me if I am wrong) its source is mainly donut, if not all donut essentially
So after much debugging I figured this out today. And then I find this thread...
Anyways, the diff between donuts's msm_camera.c and the eclair one is quite big: some structure member names have changed, more logging, flash handling, some queuing code has changed. Still, it shouldn't be too hard to update NCommander's drivers, anyone wants to have a go? We might get official drivers soon, but having open source drivers is better.
The trouble with using a donut kernel is that the 3D Gallery doesn't work, still haven't quite figured why. Any ideas?
kapitan_petko said:
The trouble with using a donut kernel is that the 3D Gallery doesn't work, still haven't quite figured why. Any ideas?
Click to expand...
Click to collapse
Apparently the eclair kernel uses a different device for 3D acceleration (/dev/hw3dc). So it's either camera or 3D gallery...
pershoot said:
your camera should work now with the hacked in drivers.
-pershoot
Click to expand...
Click to collapse
Hey pershoot, thanks for taking the time to explain and walk through this. Very nice work, I would have been scratching my head for a very long time.
Related
oh my god!
http://developer.htc.com/
ps: sorry if it is already posted!
pps: it's kernel source of htc brand phone or not?
So, what now?
So what's the real benefit of that. Sorry for the noob-ish question...
nk02 said:
oh my god!
http://developer.htc.com/
ps: sorry if it is already posted!
pps: it's kernel source of htc brand phone or not?
Click to expand...
Click to collapse
WTF! Man this is fantastic, thanks!
You could always cook it your self!
This is only the binaries for the device. As cc said, the kernel you make yourself. What we need is the source for the proprietary parts to make things like bluetooth work on hero among other things
Quick, someone alert cyanogen!
*edit* **** ^
jubeh said:
This is only the binaries for the device. As cc said, the kernel you make yourself. What we need is the source for the proprietary parts to make things like bluetooth work on hero among other things
Click to expand...
Click to collapse
Damn I spoke before I checked the link. Ya it's just the plain old HTC kernel source and useless proprietary binaries. I thought it was going to be their entire source for their Android build. Crap, move along people. Nothing to see here
You can extract all of the proprietary binaries from Hero using the extract script included in dream-open when you repo sync!
shafty023 said:
Damn I spoke before I checked the link. Ya it's just the plain old HTC kernel source and useless proprietary binaries. I thought it was going to be their entire source for their Android build. Crap, move along people. Nothing to see here
Click to expand...
Click to collapse
On the contrary, it has the source for their previously-proprietary kernel bits required for the canadian dream and magic devices, which means it should now be possible to build custom kernels for those devices for true and proper root/customization without the need for the death-spl. This is something that we've been fighting them for.
Just gave the source a quick look through. All of the default kernel settings/commits you would pull down from git are absent, that is, nothing is really set. I'm gonna cook it really quick without any fussing around with it to see what happens.
Man to bad they dont have the hero source as well but thats great.
The kernel is in the oven right now. I literally only changed two things for better performance, other than that this thing is stock.
Implemented CFQ and SLUB.
lbcoder said:
On the contrary, it has the source for their previously-proprietary kernel bits required for the canadian dream and magic devices, which means it should now be possible to build custom kernels for those devices for true and proper root/customization without the need for the death-spl. This is something that we've been fighting them for.
Click to expand...
Click to collapse
As CC stated previously, these can be extracted using the htc script from those devices. I didn't see anything that we couldn't already grab (IE libhtc_ril.so)
ccyrowski said:
The kernel is in the oven right now. I literally only changed two things for better performance, other than that this thing is stock.
Implemented CFQ and SLUB.
Click to expand...
Click to collapse
Hmmm should be interesting to see what results you find.
I cooked the kernel, wlan.ko, and modules. Those are all the files you should need. I'm at work right now, but when I'm home ill throw in a ramdisk to make the boot.img.
Does anyone here know how to mkbootimg boot.img so I don't have to make a million of them for every ROM out there? Or at least I'll make one for a cupcake ROM and one for a HERO ROM
Sorry for the total noobness but does this mean we can have .odex in builds now?
shafty023 said:
As CC stated previously, these can be extracted using the htc script from those devices. I didn't see anything that we couldn't already grab (IE libhtc_ril.so)
Click to expand...
Click to collapse
You might want to read some of the retardedly long root-rogers-dream threads. There is indeed a bunch of kernel code that we can't extract/reverse engineer without a huge effort. Those files pulled by the extract scripts are NOT RELATED. The difference is in the actual kernel.
I TAKE ABSOLUTELY NO RESPONSIBILITY FOR WHAT THIS DOES TO YOU PHONE.
I HAVE NOT TESTED IT.
I WHIPED IT UP ASAP SO YALL COULD FUX WITH IT.
I imagine you'll get partially through the boot process then it will loop. The again, maybe it will work. Who knows. Please provide me with a logcat if you try this.
You cannot flash the zip file. You cannot fastboot flash the boot.img-kernel. You must mkbootimg boot.img-kernel and ramdisk.cpio.gz to make boot.img.
wlan.ko is for wifi and goes in /system/lib/modules
modules.sqf go in /system/modules
Enjoy.
http://demarcatedmedia.com/rom/stockkernel.zip
no brave souls eh?
I'd test it if I knew what you were talking about Don't have ubuntu up and running, creating a VM right now using virtualbox. I have no idea how to compile mkbootimg though.
Original Thread
Credits to TwistedUmbrella and Amon_RA for the kernel ofc!
Casper's Shadow - ZeroXd 5.1 w/ Amon_RA's v1.1.0 kernel [rapidshare]
For Ringtones and other "Extra Stuff" download Resources.zip from oringinal thread. Maybe on next update I'll include them already into the original ROM archive...
Note: Just install normally! No need to type anything into the terminal as the original thread states because this port replaces ramdisk and kernel so no need
Hi thanks for another fine release..aft trying out ur jac release and this rom.. i find this not as fast as the jac one..if u could improve on the jac rom it will surely be an incredible rom..really like the speed and lightness on the jac rom..thanks once again..
I only do the ports This is not my work. I merely repack the files for easier installation and for those that don't have linux
covertless said:
Hi thanks for another fine release..aft trying out ur jac release and this rom.. i find this not as fast as the jac one..if u could improve on the jac rom it will surely be an incredible rom..really like the speed and lightness on the jac rom..thanks once again..
Click to expand...
Click to collapse
HAHAHA, lol, HAHAHAHAHAHA. Wow, hahahahaha. Ok. Sorry. Ok, seriously... anyway... You might wanna throw the kernel on this
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.1r2.zip
MD5: 0d10525b55ed6c97b7741a70aa113cdb
Execute Terminal and enter the following commands:
rwsystem
magic
This configures the system to the specific device. This is until I finish automation.
LEDs have been restored to 93%
(and delete system/bin/magic and system/bin/sapphire, as they dont affect a swapped kernel)
I think it'll shut this kid up. Unless he has no idea what partitioning an sd card does, in which case this will still be slow. It's based on some newer source and some improved scripts and optimizing. Can't say its faster, but at least itll even out.
L10nH34Rt said:
I only do the ports This is not my work. I merely repack the files for easier installation and for those that don't have linux
Click to expand...
Click to collapse
Okay my bad, anyway what I meant to say was thank you for the effort in porting over for the 32a.
twistedumbrella said:
HAHAHA, lol, HAHAHAHAHAHA. Wow, hahahahaha. Ok. Sorry. Ok, seriously... anyway... You might wanna throw the kernel on this
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.1r2.zip
MD5: 0d10525b55ed6c97b7741a70aa113cdb
Execute Terminal and enter the following commands:
rwsystem
magic
This configures the system to the specific device. This is until I finish automation.
LEDs have been restored to 93%
(and delete system/bin/magic and system/bin/sapphire, as they dont affect a swapped kernel)
I think it'll shut this kid up. Unless he has no idea what partitioning an sd card does, in which case this will still be slow. It's based on some newer source and some improved scripts and optimizing. Can't say its faster, but at least itll even out.
Click to expand...
Click to collapse
Anyway twistedumbrella, are you as what your name describes? Your comments are uncalled for and not needed in this community. Please grow up and get a life. I am new here, so would appreciate if you could give positive feedbacks instead of insults.
@covertless: He is right though... On my magic this ROM is *MUCH* faster than the JACxHEROski one
@Twisted: Ok will throw the kernel and include full instructions based on your post here!
Thank you for your work!
p.s. If I delete /system/bin/magic and /system/bin/sapphire will we still be able to run rwsystem and then magic?
*L10nH34Rt: Great could you release the ported version when its done?
P.S. I am not saying he is wrong, anyway I appreciate that there are people like you and him contributing to this community by working hard on the dev of roms. Not sure as to why he had to assume that non programmers like me are "kids".
Sure I will later today when I get to my linux box
covertless said:
Hi thanks for another fine release..aft trying out ur jac release and this rom.. i find this not as fast as the jac one..if u could improve on the jac rom it will surely be an incredible rom..really like the speed and lightness on the jac rom..thanks once again..
Click to expand...
Click to collapse
Wait, even he says "jac rom"i think he is talkin about older zero releases which are using jac kernel vs new amonra kernel, or is he not? Because there is no hero port who can outperform xero's speed with proper adjustments atm.
Nyanna said:
Wait, even he says "jac rom"i think he is talkin about older zero releases which are using jac kernel vs new amonra kernel, or is he not? Because there is no hero port who can outperform xero's speed with proper adjustments atm.
Click to expand...
Click to collapse
I was referring to L10nH34Rt's port of the JACxHEROski-v1.7r2 w/ Amon_RA's 1.1.0 kernel.
http://forum.xda-developers.com/showthread.php?t=549873
Hey with this new kernel that has been really impressive to me
I want to work with any Devs out there to bring this kernel to them for testing
I think a lot of people would really like it since it has choices for CFS/BFS RHack/NoRHack
So, if any devs want to work with me on bringing this any build - email me
[email protected]
Hopefully, I want to create a kernel for everyone to use - I know CM's has been more popular for its features - but this one has the features plus a really good speed
I would really like to work with any Eclair Devs to improve the speed of this before I make my Eclair ROM (sooner or later - may need a break first for life lol)
I was really behind on this working on the kernel way too much - so 2wks behind
wesgarner said:
Hey with this new kernel that has been really impressive to me
I want to work with any Devs out there to bring this kernel to them for testing
I think a lot of people would really like it since it has choices for CFS/BFS RHack/NoRHack
So, if any devs want to work with me on bringing this any build - email me
[email protected]
Hopefully, I want to create a kernel for everyone to use - I know CM's has been more popular for its features - but this one has the features plus a really good speed
I would really like to work with any Eclair Devs to improve the speed of this before I make my Eclair ROM (sooner or later - may need a break first for life lol)
I was really behind on this working on the kernel way too much - so 2wks behind
Click to expand...
Click to collapse
are you saying that it has the same features as the CM kernel, but it's faster?
prince.siraj said:
are you saying that it has the same features as the CM kernel, but it's faster?
Click to expand...
Click to collapse
That's what it looks like.
Need this in a Hero ROM
Would love this for SuperD.....
hey i just tried out your kernel on eclair. i used your kernel from 2.6 cfs w/ ram hack on my custom speed demon build of eclair using manups ramdisk and i am unable to pass splash screen. prolly needs more implementation of eclair goodies
What files did you "transplant" to use the kernel on another build?
u must unpack the boot.img's then replace kernel
Hero_Over said:
u must unpack the boot.img's then replace kernel
Click to expand...
Click to collapse
THanks, Im gonna do some experimenting on a 1.6 build later
Anyone else trying this kernel on Eclair other then Herver?
I'm waiting to switch to Eclair until a fast/responsive kernel is implemented.
Tried BFS/RAMHACK with Manup's Eclair ROM, kernel loaded properly, ran quickly, only issue was that bluetooth didn't work.
My issue with all these different kernels out there, is that I'd like to see source code accessible, or at the very least, maybe attach the .config file, so I know what exactly has been changed.
Ok lol who wants for what ROM?
You have to grab a few things from it - such as the rootdir plus setup xbin if it doesn't use it
hi wes.
i would certainly like to help the cause and assist in improving upon things (where possible and if feasable), but i would really need to see the source and .config to make advancements.
is this available on your github?
you're handing these out pre-built? Do you have somewhere we could download the source?
Figured I'd test it, and figured it wouldn't work...
The kernel (CFS + ram hack) doesn't work as a direct drop-in on dwang.
wesgarner said:
Ok lol who wants for what ROM?
Click to expand...
Click to collapse
You should do one for hero/espresso.
wesgarner said:
Ok lol who wants for what ROM?
You have to grab a few things from it - such as the rootdir plus setup xbin if it doesn't use it
Click to expand...
Click to collapse
If you wanna help me, then
g'day Wes,
like the rest - I am curious to know if it possible to see the source and the .config? Is there anyway you could make this available? thanks in advance mate...
peace..
bump for update dammit. Donut is still ALive!
R3N0V4D0 said:
bump for update dammit. Donut is still ALive!
Click to expand...
Click to collapse
No it isn't, go back to sleep and don't be bumping ancient threads.
11/22/11 Update: Added "reboot bml8 recovery" patch for ROM Manager suppport.
11/8/11 Update: Updated keyfix kernel with the EI22 initramfs. Also, Samsung has placed the previous official (and now labeled EI22) source tarball on their opensource site.
10/24/11 Update: It appears that Samsung has removed the "official" Epic GB source tarball from their website. I've mirrored it for anyone interested in the original release. For anyone actually looking to build with the sources, you're probably better off using Rodderik's GitHub
10/19/11 Update: As everyone's found out by now, Samsung released official Epic GB sources last night. There's not that many changes to our device in the official source tree compared to the previous, but a few appear to be subtlely important (see abbreviated deltas). It still needs some work to get into a buildable state, but it does appear to work great on EH17!
I've updated most of my patches for GB, conveniently packaged together. I've also uploaded a new EH17 kernel that works on stock (rfs) EH17 ROMs and includes the keyboard fixes with optimized values, along with userdebug and kexec support. Feel free to give it a try.
Meanwhile Rodderik is updating his GitHub repo to include all these patches for folks to clone from, stay tuned.
Happy hacking!
So apparently when Samsung released the kernel sources to the Mesmerize's Gingerbread update a month-and-a-half ago, that source tree contained almost-buildable kernel sources for our device as well.
I've patched the sources (removed modemctl definition, added tfsr driver, compile right camera driver) to build for the Epic. I've also built a custom EH17 kernel combining these sources with the EH17 initramfs. It's essentially stock EH17 with ro.debugging=1, adbd always-spawning during recovery, and testkey signature verification. I'll get to porting over some other patches (like the dropped key fix) soon.
As for compatibility with EH17, the source tree itself appears to have been checked out on 8/30 and looks to include everything EH17 does. I ran "strings Image | sort -u" on both kernels to make sure there weren't any obvious strings/symbol differences between them. The ones that remain appear to be minor, but legitimate fixes.
Thanks to jt1134 & Rodderik for pointing out that the Mesmerize source released contained Epic code, and Tortel & ugothakd for testing.
GitHub repo, thanks Rodderik!
To build:
Grab SCH-I500_USCC_Opensource_Update3.zip SPH-D700_GB_Opensource.zip from opensource.samsung.com, extract.
Run "make mrproper" to get rid of atlas (Mesmerize) config junk.
Patch to complete Epic support.
Build with EH17 initramfs as usual, use victory_8G_defconfig for kernel configuration.
Mirror links:
Official GB sources: SPH-D700_GB_Opensource.zip (originally posted on opensource.samsung.com, since removed.)
Epic GB source patches: kernel-GB-3a-patches.tar.gz
Source-compiled, keyboard fix EI22 kernel: kernel-GB-3a.tar.md5
(URLs for Mesmerize tree patches removed, although they're still valid.)
Flashed this yesterday(11/13). Working good so far.
Edit: Oh, and first! Sorry iSaint
Sent from my SPH-D700 using Tapatalk
HAHAHAHA! Epic. I love you guys!
Yeah, um, I love you. <3 lol.
No. I was first. I tested it lol
[edit] actually, tortel was first. but that was before i got on board.
Hmmmm...who would of known part of our kernel source was right under our noses
Sent from my SPH-D700 using xda premium
It just occurred to me that, with this finding a lot of good can happen, as well as ICS tomorrow. Depending on timezone I should say.
Sweet. Hopefully this'll help cm7
Heart just stopped beating LOL!
What about stratosphere then?
Oh well nice work!
Sent from my SPH-D700
winning
bet samsung was just watching and waiting to see how long it took one of you/us to figure it out, lol.
this is wonderful news
Ceelos09 said:
Hmmmm...who would of known part of our kernel source was right under our noses
Click to expand...
Click to collapse
Ideally there would be one Samsung Android kernel source tree that would contain code for our device as well as all their others. However, I've been checking somewhat recently and code for Epic never appered in the GT-I9000 sources (which have been updated recently) nor in the Stratosphere ones.
It didn't occur to me to check the Mesmerize sources sooner, but as the only US device with an official GB release (still?) it shouldn't have been much of a surprise. It's also worth nothing that there appears to be GB sources for the Indulge in there as well. I'm not sure of their buildability though.
GREAT work mkasick.... everyone be SURE to thank him!
SWEET !!!
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Neckberg said:
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
I'm not sure, JT helped Decad3nce with CM 7 though and they both hacked the EH17 kernel to work for this. So hopefully it's something Decad3nce can use.
He said he was moving so he probably won't be back until tomorrow.
Neckberg said:
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
The main CM7 people are Decad3nce and jt and they haven't been on irc today.
this is exactly what we been needing...THANK YOU VERY MUCH mkasick!! You rock my friend!
Downloading now - going to see if I can compile a bootable kernel
Sent from my CyanogenMODed Epic
Neckberg said:
Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
I believe JT was the one who discovered the Mesmerize sources were pertinent to us. He might've been able to compile something, but at least Rodderik was stuck on the missing tfsr driver without the right debugging bits.
I discovered this worked somewhat haphazardly when Rodderik mentioned the Mesmerize sources to me. They booted the first time with EH17 on SD, but wouldn't boot from flash. Since I was able to get it to boot off SD, debugging was a good deal easier.
In any event, it's a drop-in replacement for the current kernel used by the Epic CM7 build, so I'm sure they'll make good use of it sooner or later.
Actually what I'm curious about is if the reboot problems still persist with this. I haven't had one yet, but they haven't been a problem with stock EH17 on my device either.
Just wondering what toolchain I should be using to compile the kernel for this phone.
I tried the arm-eabi-4.4.3 that comes built with the AOSP-SDK package however that does not seem to work correctly.
Right now I have both Arrrghhh's repo and the one Linus maintains on my machine. The only "internet" I have is from tethering my phone though so I am limited on what I can download and try.
BTW, I also have a few of the Android source repos "synced" already like CM, AOKP, & AOSP, I figured I would start with kernels though.
EDIT: Also I should mention that I have compiled kernels before, however only deb-pkg's for Ubuntu. Sooo just looking for a little cross-compiling help. :/
HAHA I feel like a noob now but nevermind.
Found here: forum.xda-developers.com/showthread.php?t=1748297 ; I just needed this github.com/DooMLoRD/android_prebuilt_toolchains.git
Thanks to Arrrghhh for the "maek" script left in his reop. I will be experimenting with different configs and version patches....
That script is sweet! Kanged from Shabbypenguin .
Enjoy!!
No doubt! I am happy! Thanks again!! If I get anything worthwhile patched in I could send you pull-requests if you like.
I was hung up on that for a long time, seems like linaro-4.6.2 works though.