From: Fabio Estevam <festevam@gmail.com>
To: trini@konsulko.com
Cc: marex@denx.de, u-boot@lists.denx.de,
francesco.dolcini@toradex.com, Fabio Estevam <festevam@denx.de>
Subject: [PATCH v2 2/3] microblaze: u-boot-spl.lds: Pass _image_binary_end
Date: Fri, 30 Jun 2023 23:30:52 -0300 [thread overview]
Message-ID: <20230701023053.747972-2-festevam@gmail.com> (raw)
In-Reply-To: <20230701023053.747972-1-festevam@gmail.com>
From: Fabio Estevam <festevam@denx.de>
Pass _image_binary_end to make a standard way to indicate the end
of the text section in SPL.
The motivation for this is to have a uniform way to handle
the SPL boundary checks.
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Changes since v1:
- Newly introduced to avoid build failure.
arch/microblaze/cpu/u-boot-spl.lds | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/microblaze/cpu/u-boot-spl.lds b/arch/microblaze/cpu/u-boot-spl.lds
index 4ac5a21524c5..597095195cae 100644
--- a/arch/microblaze/cpu/u-boot-spl.lds
+++ b/arch/microblaze/cpu/u-boot-spl.lds
@@ -54,6 +54,7 @@ SECTIONS
__bss_end = .;
}
_end = . ;
+ _image_binary_end = .;
}
#if defined(CONFIG_SPL_MAX_FOOTPRINT)
--
2.34.1
next prev parent reply other threads:[~2023-07-01 2:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 2:30 [PATCH v2 1/3] sunxi: u-boot-spl.lds: Pass _image_binary_end Fabio Estevam
2023-07-01 2:30 ` Fabio Estevam [this message]
2023-07-01 13:06 ` [PATCH v2 2/3] microblaze: " Marek Vasut
2023-07-03 18:28 ` Tom Rini
2023-07-01 2:30 ` [PATCH v2 3/3] spl: spl_legacy: Fix spl_end address Fabio Estevam
2023-07-01 13:11 ` Marek Vasut
2023-07-03 18:28 ` Tom Rini
2023-07-01 13:06 ` [PATCH v2 1/3] sunxi: u-boot-spl.lds: Pass _image_binary_end Marek Vasut
2023-07-03 18:27 ` Tom Rini
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=20230701023053.747972-2-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=festevam@denx.de \
--cc=francesco.dolcini@toradex.com \
--cc=marex@denx.de \
--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