From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: "Tim Harvey" <tharvey@gateworks.com>,
"Simon Glass" <sjg@chromium.org>,
"Albert Aribaud" <albert.u.boot@aribaud.net>,
"Marek Behún" <marek.behun@nic.cz>,
"Tom Rini" <trini@konsulko.com>
Subject: [PATCH v2 2/3] arm: Add an __image_copy_start symbol for ARMv8
Date: Sun, 25 Jul 2021 10:54:15 -0600 [thread overview]
Message-ID: <20210725165416.470735-2-sjg@chromium.org> (raw)
In-Reply-To: <20210725165416.470735-1-sjg@chromium.org>
This symbol is needed for binman to locate the start of the image. Add it.
Note: the existing line to bring in the .__image_copy_start symbol does
not appear to do anything.
Signed-off-by: Simon Glass <sjg@chromium.org>
---
Changes in v2:
- Add new patch to add an __image_copy_start symbol for ARMv8
arch/arm/cpu/armv8/u-boot-spl.lds | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/cpu/armv8/u-boot-spl.lds b/arch/arm/cpu/armv8/u-boot-spl.lds
index 9edb662b094..2827a07590d 100644
--- a/arch/arm/cpu/armv8/u-boot-spl.lds
+++ b/arch/arm/cpu/armv8/u-boot-spl.lds
@@ -22,6 +22,7 @@ ENTRY(_start)
SECTIONS
{
.text : {
+ __image_copy_start = .;
. = ALIGN(8);
*(.__image_copy_start)
CPUDIR/start.o (.text*)
--
2.32.0.432.gabb21c7263-goog
next prev parent reply other threads:[~2021-07-25 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 16:54 [PATCH v2 1/3] imx8: Drop raw image support Simon Glass
2021-07-25 16:54 ` Simon Glass [this message]
2021-07-26 18:20 ` [PATCH v2 2/3] arm: Add an __image_copy_start symbol for ARMv8 Tim Harvey
2021-07-28 2:46 ` Simon Glass
2021-07-25 16:54 ` [PATCH v2 3/3] binman: Show an error if __image_copy_start is missing Simon Glass
2021-07-26 18:36 ` Tim Harvey
2021-07-26 7:33 ` [PATCH v2 1/3] imx8: Drop raw image support Michael Walle
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=20210725165416.470735-2-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=albert.u.boot@aribaud.net \
--cc=marek.behun@nic.cz \
--cc=tharvey@gateworks.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.