From: Scott Wood <oss@buserror.net>
To: Simon Glass <sjg@chromium.org>,
U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tim Harvey <tharvey@gateworks.com>,
Albert Aribaud <albert.u.boot@aribaud.net>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v3 2/3] arm: Add an __image_copy_start symbol for ARMv8
Date: Wed, 04 Aug 2021 14:52:34 -0500 [thread overview]
Message-ID: <22eb78079a4f99f2966c99a59872b439de0a2237.camel@buserror.net> (raw)
In-Reply-To: <20210801205951.2202789-2-sjg@chromium.org>
On Sun, 2021-08-01 at 14:59 -0600, Simon Glass wrote:
> 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>
> ---
> I have copied Scott Wood who originally added the line about the
> __image_copy_start in the hope that he can decide if we should remove it.
It's been a long time since I looked at this stuff, but __image_copy_start is
used for relocation and that code does not seem to be in the SPL, so the
*(.__image_copy_start) was probably just a copy-and-paste leftover from the
main SPL that can go away.
Of course, that doesn't resolve the binman issue. :-)
> 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*)
If for whatever reason you did need to define the symbol this way, shouldn't
it be after the alignment?
-Scott
next prev parent reply other threads:[~2021-08-04 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 20:59 [PATCH v3 1/3] imx8: ls1028a: Drop raw image support Simon Glass
2021-08-01 20:59 ` [PATCH v3 2/3] arm: Add an __image_copy_start symbol for ARMv8 Simon Glass
2021-08-04 19:52 ` Scott Wood [this message]
2021-08-05 19:20 ` Simon Glass
2021-09-25 15:46 ` Simon Glass
2021-09-25 22:35 ` Scott Wood
2021-09-26 15:54 ` Simon Glass
2021-08-01 20:59 ` [PATCH v3 3/3] binman: Show an error if __image_copy_start is missing Simon Glass
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=22eb78079a4f99f2966c99a59872b439de0a2237.camel@buserror.net \
--to=oss@buserror.net \
--cc=albert.u.boot@aribaud.net \
--cc=sjg@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).