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
17th November 2013, 04:05 PM |#61  
Olivier's Avatar
Forum Moderator / Recognized Developer
Flag Linz
Thanks Meter: 6,880
 
Donate to Me
More
Ok, good.
But just out of curiosity, what has been done here, here and here? Didn't they just take CM ramdisk and somehow boot it?
 
 
17th November 2013, 05:24 PM |#62  
delewer's Avatar
OP Senior Member
Flag Paris
Thanks Meter: 235
 
More
I read the new sources (15/11/2013) deliver by sony (on official site)
14.1.G.2.259

It's a new kernel.

I don't know what sony have added for we (thx to them), but i read a function i don't use yet :

Commands to rdtag : (see misc/rdtags.c)

And i can send commands to rdtag entries

have you test theses fonctions ?
It's similar to my driver ?!

Code:
 # cat /proc/rdtags
Usage: <tag name/command> [tag data]
command may be one of the following:
 * clear
 * delete <tag name>
if you :
Code:
echo tag read >/proc/rdtag
This create a new file in rdtags folder name "tag" and contain "read"

Code:
echo clear >/proc/rdtag
delete all files in rdtags folder

If you enter a bad command, you have this in dmesg :
Code:
<3>[22105.446841] rdtags rdtags: Incorrect format, please supply a string of format: <tag name> <tag data>
After a crash, you have a lot of information added in rdtags folder

I see what is for... and if it is usefull for our kexec...
The Following 4 Users Say Thank You to delewer For This Useful Post: [ View ] Gift delewer Ad-Free
17th November 2013, 06:04 PM |#63  
Shaky156's Avatar
Senior Member
Thanks Meter: 2,567
 
Donate to Me
More
Quote:
Originally Posted by delewer

I read the new sources (15/11/2013) deliver by sony (on official site)
14.1.G.2.259

It's a new kernel.

I don't know what sony have added for we (thx to them), but i read a function i don't use yet :

Commands to rdtag : (see misc/rdtags.c)

And i can send commands to rdtag entries

have you test theses fonctions ?
It's similar to my driver ?!

Code:
 # cat /proc/rdtags
Usage: <tag name/command> [tag data]
command may be one of the following:
 * clear
 * delete <tag name>
if you :
Code:
echo tag read >/proc/rdtag
This create a new file in rdtags folder name "tag" and contain "read"

Code:
echo clear >/proc/rdtag
delete all files in rdtags folder

If you enter a bad command, you have this in dmesg :
Code:
<3>[22105.446841] rdtags rdtags: Incorrect format, please supply a string of format: <tag name> <tag data>
After a crash, you have a lot of information added in rdtags folder

I see what is for... and if it is usefull for our kexec...

Hi, youve replaced OP, also rdtags is atags, passes bootoader info, not sure if it is passes the information which we require, but highest priority for it to work on LB is to get it running on the stock kernel
The Following 2 Users Say Thank You to Shaky156 For This Useful Post: [ View ] Gift Shaky156 Ad-Free
18th November 2013, 07:09 PM |#64  
Senior Member
Flag Porto
Thanks Meter: 968
 
Donate to Me
More
You probably already know about this... But can this help?
Compatibility patch: https://gist.github.com/4458581
This patch only makes the kernel bootable via kexec, ie. it can't be the host kernel. This was made for Ubuntu kernel (and it was accepted), because I did not want to drag the whole patch in there. If your kernel is for Android ROMs, you should use the full patch.
Original post: http://forum.xda-developers.com/show....php?t=2104706
23rd November 2013, 11:12 AM |#65  
Knucklessg1's Avatar
Senior Member
Thanks Meter: 104
 
More
That article sure looked promising.
25th November 2013, 03:25 AM |#66  
Senior Member
Flag Melbourne
Thanks Meter: 105
 
More
Quote:
Originally Posted by delewer

Last Update : November, 23, 2013
Hi,
For few days now, i haven't no more kernel panic with my kexec.
I have fixed few stuffs into sources, and add a lot.

These adds are, to include a "dt.img" image file into kexec load process.

This image file is a "device_tree" image to match hardware to software.

So, i assume to don't include atags into boot process, but pass bootloader informations by this DT.
I have programmed a little scan memory to found dynamicly all magic tags, because i found 3 device_tree into memory (magic is "0xd00dfeed").
These 2 device_tree are echo from first and nice structure.

The boot process need to have informations from this DT, and need all informations to initialize hardware (no HDW initialisation by the kernel)
I must first fix issues ; Regroup zImage and dt.img into memory to load a solid bloc to kexec_load module to boot into, and second, fix an offset i can't explain, 0x800 in memory causing misalignment memory

Keep tuned..

Excellent work Delewer!

So is it currently functional but with bugs or does it still need work before others can start testing it?

Are your tests at the moment with Sony stock kernel (i,e, DooMKernel) or with AOSP kernel (i.e. CM kernel running CM10 or equivalent)?
25th November 2013, 11:45 AM |#67  
delewer's Avatar
OP Senior Member
Flag Paris
Thanks Meter: 235
 
More
Quote:
Originally Posted by ikenley

Excellent work Delewer!

So is it currently functional but with bugs or does it still need work before others can start testing it?

Are your tests at the moment with Sony stock kernel (i,e, DooMKernel) or with AOSP kernel (i.e. CM kernel running CM10 or equivalent)?

It's not a fonctionnal kexec ; all i see in my sources say it work, but it is not yet, it's frustating to me to be so close.

I test only with DoomKernel, to be sure when ok, to see it is.
When ok, aosp will be kexeced immediatly after... for sure !!!

Most important for now it's to have log from new kernel to debug the first crash ; if i have a log, we win the battle.
The Following 10 Users Say Thank You to delewer For This Useful Post: [ View ] Gift delewer Ad-Free
25th November 2013, 02:25 PM |#68  
Shaky156's Avatar
Senior Member
Thanks Meter: 2,567
 
Donate to Me
More
Quote:
Originally Posted by delewer

It's not a fonctionnal kexec ; all i see in my sources say it work, but it is not yet, it's frustating to me to be so close.

I test only with DoomKernel, to be sure when ok, to see it is.
When ok, aosp will be kexeced immediatly after... for sure !!!

Most important for now it's to have log from new kernel to debug the first crash ; if i have a log, we win the battle.

Messaged you the method ive described/said is a little different, no more dt.img
The Following 3 Users Say Thank You to Shaky156 For This Useful Post: [ View ] Gift Shaky156 Ad-Free
26th November 2013, 03:20 PM |#69  
Galcactus's Avatar
Senior Member
Flag Colchester
Thanks Meter: 105
 
More
Will you document the process you used to create a functional kexec?

Just asking so that I may use the method (with your permission and appropriate credits) to create kexec for Xperia T.

Looking forward to your next update/news flash


Quote:
Originally Posted by delewer

It's not a fonctionnal kexec ; all i see in my sources say it work, but it is not yet, it's frustating to me to be so close.

I test only with DoomKernel, to be sure when ok, to see it is.
When ok, aosp will be kexeced immediatly after... for sure !!!

Most important for now it's to have log from new kernel to debug the first crash ; if i have a log, we win the battle.

The Following User Says Thank You to Galcactus For This Useful Post: [ View ] Gift Galcactus Ad-Free
28th November 2013, 02:45 PM |#70  
olokos's Avatar
Recognized Developer / Recognized Contributor
Flag Warsaw
Thanks Meter: 2,478
 
Donate to Me
More
I just wanted to say that doomkernel is NOT a stock kernel...
Good job

Wysyłane z mojego R800i za pomocą Tapatalk 2
28th November 2013, 03:33 PM |#71  
Olivier's Avatar
Forum Moderator / Recognized Developer
Flag Linz
Thanks Meter: 6,880
 
Donate to Me
More
It is a stock kernel, but not a stock boot.img.

Gesendet von meinem LT26i mit Tapatalk
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