From: geoff@infradead.org (Geoff Levand)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64 entry point
Date: Thu, 15 May 2014 16:06:31 -0700 [thread overview]
Message-ID: <1400195191.12756.9.camel@smoke> (raw)
Hi,
There is some discrepancy between what booting.txt says and what our
linker script defines as the kernel entry point.
Here is booting.txt:
The primary CPU must jump directly to the first instruction of the
kernel image.
And the linker script:
ENTRY(stext)
Should we change booting.txt, or the linker script?
-Geoff
next reply other threads:[~2014-05-15 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 23:06 Geoff Levand [this message]
2014-05-16 9:01 ` arm64 entry point Will Deacon
2014-05-16 17:26 ` [PATCH] arm64: Fix linker script " Geoff Levand
2014-05-19 15:49 ` Will Deacon
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=1400195191.12756.9.camel@smoke \
--to=geoff@infradead.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.