Android OS Forum banner
1 - 6 of 6 Posts

·
Android Master
Joined
·
3,956 Posts
Discussion Starter · #1 ·
I know the source is available for our kernel, and I know we can run kexec .. is it just a matter of driver modules preventing us from a custom kernel using the 2.6.32.9 source?

If so, how can we as a whole help solve the problem and even work a newer kernel in? Not clear on the mechanics of how it all works with 2nd init, so an explanation would be great.
 

·
Android Master
Joined
·
3,956 Posts
Discussion Starter · #3 ·

·
Android Master
Joined
·
3,956 Posts
Discussion Starter · #5 ·
Lol!!
 

·
Android Master
Joined
·
3,956 Posts
Discussion Starter · #6 ·
Now that radio 13 is out there, maybe someone can find a way to get that working with kexec and a custom kernel
 

·
Android Master
Joined
·
3,956 Posts
Discussion Starter · #9 ·
"MoodMuzik said:
all your questions should probably be directed toward twitter.com/aliasxerog if you want answers
Yeah, I just hate to continually bug one person over it when there's thousands here that may also have insight.
 

·
Android Master
Joined
·
3,956 Posts
Discussion Starter · #13 ·
"Alemonator said:
Basically its a module
The way I took it was yes, it's a module that contains a separate kernel inside. Not unlike second init in that once it is called it takes over for the original kernel. That could be way off, though. It's been a while.
 
1 - 6 of 6 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top