From: "Will Newton" <will.newton@gmail.com>
To: "Luke -Jr" <luke@dashjr.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: kernel_entry up front
Date: Fri, 11 Jul 2008 11:32:01 +0100 [thread overview]
Message-ID: <87a5b0800807110332y65ea8c15g2feaa8806b1f1d85@mail.gmail.com> (raw)
In-Reply-To: <200807102308.48706.luke@dashjr.org>
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.
prev parent reply other threads:[~2008-07-11 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 4:08 Luke -Jr
2008-07-11 10:32 ` Will Newton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5b0800807110332y65ea8c15g2feaa8806b1f1d85@mail.gmail.com \
--to=will.newton@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@dashjr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®