* kernel_entry up front
@ 2008-07-11 4:08 Luke -Jr
2008-07-11 10:32 ` Will Newton
0 siblings, 1 reply; 2+ messages in thread
From: Luke -Jr @ 2008-07-11 4:08 UTC (permalink / raw)
To: Linux Kernel Mailing List
I need to get kernel_entry to the lowest memory region in the binary. This is
because a platform I am porting to does not support ELF, and always begins
execution at the first word of the firmware image. Alternatively, if there is
a simpler way to prepend the image with a jump to the kernel_entry symbol,
that could work as well.
Thanks,
Luke
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: kernel_entry up front
2008-07-11 4:08 kernel_entry up front Luke -Jr
@ 2008-07-11 10:32 ` Will Newton
0 siblings, 0 replies; 2+ messages in thread
From: Will Newton @ 2008-07-11 10:32 UTC (permalink / raw)
To: Luke -Jr; +Cc: Linux Kernel Mailing List
On Fri, Jul 11, 2008 at 5:08 AM, Luke -Jr <luke@dashjr.org> wrote:
> I need to get kernel_entry to the lowest memory region in the binary. This is
> because a platform I am porting to does not support ELF, and always begins
> execution at the first word of the firmware image. Alternatively, if there is
> a simpler way to prepend the image with a jump to the kernel_entry symbol,
> that could work as well.
The easiest way to do this is to put your entry point in a named
section (for example .text.head) then edit vmlinux.lds.S to put that
section at the correct place in your kernel image.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-07-11 10:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-11 4:08 kernel_entry up front Luke -Jr
2008-07-11 10:32 ` Will Newton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox