hey all,
just wondering...
- what is the current status for getting custom kernels running on the x10 mini / mini pro?
- has development of a kexec module or something similar begun based on code written for other phones?
- if so, does anybody know how far people have gotten? what difficulties are we facing at the moment in those regards?
i'm wondering because if nobody has started working on a kexec module then i thought i might try, but if someone is already working on it then i'd be glad to lend a hand if needed / if i can...
cheers,
uriah
uriahheep said:
hey all,
just wondering...
- what is the current status for getting custom kernels running on the x10 mini / mini pro?
- has development of a kexec module or something similar begun based on code written for other phones?
- if so, does anybody know how far people have gotten? what difficulties are we facing at the moment in those regards?
i'm wondering because if nobody has started working on a kexec module then i thought i might try, but if someone is already working on it then i'd be glad to lend a hand if needed / if i can...
cheers,
uriah
Click to expand...
Click to collapse
here is the development thread for bootloader bypassing (on x8, but our phones are "twined" )
it is a dev thread, so don't post anything unless you're a dev.
link is here
answers to your questions may be there
i cant put the link cause my post, but u can serarch this in google
"how to build a linux kernel" sony ericsson
is from the original dev SE team
burnice said:
i cant put the link cause my post, but u can serarch this in google
"how to build a linux kernel" sony ericsson
is from the original dev SE team
Click to expand...
Click to collapse
this link is only for open bootloader.
it is unuseful for now ^^
here is the link you are talking about: blogs.sonyericsson.com/wp/2011/05/06/how-to-build-a-linux-kernel/
wht z a kexec module?
death_syndrome said:
wht z a kexec module?
Click to expand...
Click to collapse
a kexec module is a kernel module which reconstructs the kexec functionality (which allows one to execute a kernel from within another kernel) that the linux kernel can have. usually kexec support needs to be built into the kernel (i.e. not a module), but by loading modules such as splboot (which is the kexec module that is being developed in the X8 bootloader bypassing thread based on work that was done for the X10) one can execute a kernel from within the current kernel even if kexec support wasn't built into it.
[EDIT] actually, splboot doesn't exactly reconstruct kexec support, but does something similar. see this post and the few that follow for more details.
hi.. i need some advice/guide regarding this matter..
first of all, i'm planning on compiling custom kernel myself for my ace. i've succesfully compiled a kernel on my debian box using kernel sourcecode from samsung and also applied bfs patch. but now i dont want to just stop here.
the problem is i dont know where to look for those undervolt patch, smartass governor patch, interactive governor patch etc etc. gooling for "android kenel patch/module" just bring me to precompiled kernel thread, not the source patch itself. so maybe anyone can guide me the right direction? thx before
an0nym0us_ said:
hi.. i need some advice/guide regarding this matter..
first of all, i'm planning on compiling custom kernel myself for my ace. i've succesfully compiled a kernel on my debian box using kernel sourcecode from samsung and also applied bfs patch. but now i dont want to just stop here.
the problem is i dont know where to look for those undervolt patch, smartass governor patch, interactive governor patch etc etc. gooling for "android kenel patch/module" just bring me to precompiled kernel thread, not the source patch itself. so maybe anyone can guide me the right direction? thx before
Click to expand...
Click to collapse
better to see the github site, lot of kernel source with many patching in there. and i think, for the much customized of samsung kernel, you can just patching, manual diffing will more better because samsung kernel is not vanillaish android kernel. much modification in there.
Sent from my ViewPad7 using XDA App
Custom kernel for the Ace on it's way..?
Just rambling here. In order to get ICS ported to the Venue, we need compatible kernel drivers. It appears, from what I can find on the 'net, that Qualcomm isn't releasing drivers for the QSD8250 for ICS. Looking around XDA, I see the HTC Desire (GSM), also based on the '8250, has a working ICS beta found here: http://forum.xda-developers.com/showthread.php?t=1403113. This appears to use a Tiamat kernel, http://tiamat-dev.com/tiamat_bravo/. Using the AOSP 4.0.x repository, the Dell info from http://opensource.dell.com/releases/venue/v4.06/ and the Tiamat kernel, is it possible to pull together an ICS port? I wish I had more experience with this type of stuff...
Dell used the CAF 8260 GB sources when building 4xx roms, they simply backported whatever they need to from their already working 3xx codebase for whatever was needed (i assume)
CAF itself dropped support for 8x50 in their GB codebases, but the 8x60 is close enough it didnt really matter ultimately.
Much of the drivers arnt even in the kernel, they're in the android userland which is Apache and not gpl, hence the driver issue.
Which ever method you (presumedly do) to get the kernel booting under ICS doesnt really matter, but the more difficult/time-consuming methods will ultimately be more useful for porting to newer kern versions.
Don't forget the Nexus One and, IIRC, the HD2 also use the 8250
I would think this would help too: http://www.xda-developers.com/android/qualcomm-releases-adreno-2xx-gpu-binaries-for-ics/
Too bad the development work is well outside my capabilities. Maybe our Korean friends are working on it though.
Guys.!!! Dell venue n dell streak 5got same rom n environment hardware too just diffrence is venue is Hdpi n dell streak is Mdpi .so why do nt we join hands n make ics work for dell or on other hand u can take advantage of our dell streak 5 formus there r few good roms like longhorn 2.8 with Hdpi support for dell Venue and Dcs 1.1.which supports both hdpi n mdpi just need to edit build.prop n may be kernel....whish u all safe cooking ...n Friends in need friend indeed ..
Max
Sent from my Dell Streak using xda premium
Sent from my Dell Streak using xda premium
Folks, I can see that Qualcomm released Adreno 200 drivers for ICS several months ago (Mar) (https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources).
Information in the above page also says that, the drivers has been tested on CAF M8960AAAAANLYA1030. As I noticed, whenever we get the source code from Code Aurora, there is also a kernel directory included. Do you think that we can start from that kernel to port ICS to Venue?
chacona said:
Folks, I can see that Qualcomm released Adreno 200 drivers for ICS several months ago (Mar) (https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources).
Information in the above page also says that, the drivers has been tested on CAF M8960AAAAANLYA1030. As I noticed, whenever we get the source code from Code Aurora, there is also a kernel directory included. Do you think that we can start from that kernel to port ICS to Venue?
Click to expand...
Click to collapse
Yes we can,
But I aint that good into dev
This mobile has what it requires to run ICS
The kernel itself ultimately doesnt matter, as long as it has the right code changes merged in.
The current S5 ICS kernel's lineage is:
S5/405 (dell) -> Phoenix kernel/GB (n0p) -> Phoenix/cm7.2 (hPa) ?-> Phoenix/cm9 (hPa) -> Phoenix/AOSP (kibuuka)
Only the final step involved merging in any changes to make it work with ics, ultimately it's based mostly on the phoenix GB kernel which itself is based on the S5's 405 kernel
S5 405 = S5 408 = V 406 = V 408, they're all the same kernel (with ifdefs/configs for the S5/V).
I'd imagine getting a V kernel to boot ICS period is 85% of the work as the S5's froyo/GB kernels can directly boot V froyo/gb roms, and the reverse would likely hold.
The kernel 405/6/7/8 from Dell can be built successfully, however there are known issues such as after charging, we won't be able to boot the kernel up. I do not have a Streak, so I wonder whether those issues are fixed well in Phoenix kernel Manii? Can you show me how to get the source for the latest phoenix kernel that you're using with your Streak AOSP? Maybe I will try to build with Venue myself to see how things work!
phoenix kernel/ICS - Github
It's currently in the process of being merged back in.
You could try diffing S5 405 with V 406 and seeing what's changed in the source, they're nearly identical, but I dont expect them to be bit identical
TheManii said:
phoenix kernel/ICS - Github
It's currently in the process of being merged back in.
You could try diffing S5 405 with V 406 and seeing what's changed in the source, they're nearly identical, but I dont expect them to be bit identical
Click to expand...
Click to collapse
Sounds interesting, that's exactly what I did in my custom overclocked kernel. However, I will be able to save some time by using their kernel directly. In fact, I think that 405/407 kernel is not very different from 406 since my build for 405 also ran on DV too.
I will try with their "master"/experimental14 branch kernel first (to CM 7.2.0). Thanks for your information!
chacona said:
I will try with their "master"/experimental14 branch kernel first (to CM 7.2.0). Thanks for your information!
Click to expand...
Click to collapse
Will be waste of time as only streak-specific file is board-qsd8x50_austin.c, other changes are device-independent.
Changes that essential to run ics with hwa:
kgsl3.8 - kernel-side drivers are in drivers/video/msm - direct drop in instead of one that's shipped with stock 405 kernel
include/linux/msm-kgsl.h - to make kgsl3.8 build
(not really)*streak-specific*changes to arch/arm/mach-msm/board-qsd8x50_austin.c - changes in hardware init routines needful for kgsl3.8 (updated data structures, powerrail). In short - do a diff for board-qsd8x50_austin.c between Phoenix and ics branches to find out what's changed - to be honest - changes are generic for qualcomm devices, so direct copy/paste of changes into your device's board file will do the job
Other patches that were applied to ics branch are optional (cpu governors, io schedulers, netfilter specific changes (these are only needed if you need ics' mobile data usage collecting/limits features)) or affect streak-specific drivers only (and are not ics-specific).
So, in short - update your device's board file and use ics branch - that would be enough.
kibuuka said:
So, in short - update your device's board file and use ics branch - that would be enough.
Click to expand...
Click to collapse
Do you think I can start with the stock kernel, download the ICS tree including the kernel, then do the diff/merge between device's board file from ICS kernel to Dell kernel? After that, the original Dell kernel is patched with new stuffs for ICS, and can be used with ICS ROM?
i can also provide you with all patches made for streak against aosp source tree for shortening your mileage and instructions for a quickstart (my streak is broken at the moment, so i've suspended my development activities and got spare time for that)
please mention kernel for streak's ics is being built separately at the moment (i've got plans incorporating it in aosp build process, but it will take some time)
when i've messed with streak kernel making it ics-friendly i've realised that most of stuff can be made cross-compatible between two devices.
It's 95% the kernel, the only thing left is to turn off the rotation patch and swap out the BCM4325 for BCM4239 drivers.
On stock 3/4xx i can directly load venue roms on my S5 and only wifi is broken. (with a S5 kernel) Everything else works.
TheManii said:
It's 95% the kernel, the only thing left is to turn off the rotation patch and swap out the BCM4325 for BCM4239 drivers.
Click to expand...
Click to collapse
rotation is triggerable through kernel configuration menu. check.
as of wifi - is there any known-to-be-trustable list of hardware components for venue?
The V is just an S5 without the hdmi and whatever provides usb hosting.
The only other notable change is the wifi chip.
All the other sensors are compatable, and so is the modem+ril.
(I was able to get 3g working, but not wifi due to the chip being different)
I dont think anyone has done a (good quality) teardown on the V though.
Most I can offer is to pull details android gives back while it's on.
I'm guessing that's how CM7.2 was ported, since hPa didnt actually own a V,
he just took his S5 build, and flicked a few switches.
(it helped a lot that CM7.2 doesnt need any kernel changes to boot, it's just the stock 408 one with a modded ramdisk)
He only had access to a V for like a day or so.
kibuuka said:
i can also provide you with all patches made for streak against aosp source tree for shortening your mileage and instructions for a quickstart (my streak is broken at the moment, so i've suspended my development activities and got spare time for that)
please mention kernel for streak's ics is being built separately at the moment (i've got plans incorporating it in aosp build process, but it will take some time)
when i've messed with streak kernel making it ics-friendly i've realised that most of stuff can be made cross-compatible between two devices.
Click to expand...
Click to collapse
Hi Kibuuka, that sounds good, could you please share?
One more thing I would like to ask is, the stock kernels 405/407 and 406 have issues regarding power (sometime I can see the issue that after charging, screen goes black and we can only quit that situation by removing the battery). How did you address it? (I notice that your kernel works well on my CM7, without that issue - or is just simply because it has not happened yet?)
n0p did enormous amount of work addressing sleep of death issue (which, i believe is one you refer to), so dsc kernels (opposed to stock ones) are free of this bug. Ask him for details (i wasn't involved to dsc development at the point he managed to fix it) as he's best source of information on SoD issue fix you could find
As of aosp patchset - will upload it during weekends.
For whatever it's worth, as soon as we get a working ICS level kernel, I plan on porting TWRP and CWM-touch.
Those require ICS kernels (or rather it's a great deal more difficult to make them run on GB kernels) and I cant port them until then.
I've already gotten TWRP and CWM-touch working on the S7, and plan on porting TWRP to the S10 now.
Edit: come to think of it, I actually have TWRP running on a 5xx kernel (which is HC), i'll try simply porting and seeing what happens
Hi Guys
Today i've a basic question i think
Actually we can found Two Custom Kernel For this Phone (Desire X)
- The Kernel From Atiss
and
- The Nexus Kernel
How choose the appropriate Kernel ? What's work differently on the Atiss Kernel in front of the Nexus Kernel.
My actual knowledge about the kernel is the experience with Linux ( kernel pae manage less memory than standard kernel rt kernel for specific usage like Midi controlers ... )
Actually i'm running with the atiss kernel and run my device at 1.2ghz and everything run fine with a stock rom. it's specially for this possibilities and use the profile consumption of the phone. (on demand , performance, etc etc)
I hope than this post will be so clear.
Thanks in Advance
NeXusKERNEL supports ZRAM, write protection disabled and all that fun stuff...
Flowed from my HTC branded muffin...
zram like on kernel linux ? zram is able to compress ram less used and no use the swap technic ?
Write protection disable it s for be able to modify system files ?
My kernel is almost the same as atis kernel. Just tweak of 2 or 4 options. It's not substantially different from the original, so I didn't post it in development thread.
Sent from my HTC Desire X using xda app-developers app