figuring out ramdisk_offset,tags_offset,etc. in case of larger kernel than vendor kernel

78 views
Skip to first unread message

jrw

unread,
Apr 21, 2020, 1:11:02 PM4/21/20
to android-porting
Hi,

im trying to boot a selfcompiled Kernel but i'm stuck at the start. It seems the bootloader does not find the the ramdisk to continue the boot sequence.
I compiled my kernel with KASAN and it's not booting.
is there a way to properly figure out the changes in offsets i have to come up with when i build a different kernel which is larger in size than the normal one?
When we have like a default set of offsets, how do i know which offsets i have to change? i tried to increase the offset for the ramdisk due to the larger kernel but did not succeed.
Can i find out where the tags_offset should be in the image itself? are there some identifiers i can use?

pagesize=2048
base=0x10000000
kernel_offset
=0x00008000
ramdisk_offset
=0x01000000
second_offset
=0x00f00000
tags_offset
=0x00000100

Thanks a lot
Reply all
Reply to author
Forward
0 new messages