FORUMS
Remove All Ads from XDA

[dev][kernel][kexec]

186 posts
Thanks Meter: 235
 
By delewer, Senior Member on 23rd October 2013, 06:40 AM
Post Reply Email Thread
18th October 2017, 03:08 AM |#241  
capt_planit's Avatar
Member
Thanks Meter: 17
 
More
Capt Necropost here. I have confusing behavior exhibited between v10 and v11. When trying to load the same kernel v10 says: kexec-zImage-arm : ----------------------------
INFO : Segment[0] - Start : 0x40001000 - length : 0x1000 - end : 0x40002000
INFO : Segment[1] - Start : 0x40008000 - length : 0x4a7000 - end : 0x404af000
Then accepts kexec -e and shuts down. While v11 says: INFO : Segment[0] - BUF - Start : 0x400ce008 - length : 0x4a6774
INFO : Segment[0] - MEM - Start : 0x40000000 - length : 0x4a7000 - end : 0x404a7000
Overlapping memory segments at 0x404a7000
And buggers off. The code responsible looks virtually identical to me. Any ghostly advice (just in time for Halloween). tyia c_p
 
 
25th October 2017, 10:20 PM |#242  
Junior Member
Thanks Meter: 0
 
More
I've been looking at this thread a lot over the years. And wish I could do something, but I've never coded.. Where should I start and what should I learn to help? I'd like to dedicate a lot of time on this.
26th October 2017, 01:10 AM |#243  
capt_planit's Avatar
Member
Thanks Meter: 17
 
More
@chuckbtotheo 1) linux (there is cygwin too) 2) gcc that matches the version used to compile your kernel *Note* you must set your project environment or you will probably use the wrong gcc 3) kexec-tools source 4) kexec_load module source. Mostly you build these yourself but there are precompiled versions floating around on xda. If you look through all the threads dealing with kexec on xda you will find out pretty much all you need to get going. Good luck. c_p
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes