From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 2/3] ARM: i.MX: Add max_load_size option to boards that will need it
Date: Tue, 20 Nov 2018 09:40:59 +0100 [thread overview]
Message-ID: <20181120084100.8737-3-s.hauer@pengutronix.de> (raw)
In-Reply-To: <20181120084100.8737-1-s.hauer@pengutronix.de>
The max_load_size option makes sure that only the portion of the image
is loaded to SRAM that fits into it.
Note this does not cover the whole available SRAM area for all boards,
for the bigger SRAM areas only a part is chosen that is enough to fit
the initial loader in.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
| 1 +
| 1 +
.../flash-header-technexion-wandboard.imxcfg | 1 +
| 1 +
4 files changed, 4 insertions(+)
--git a/arch/arm/boards/cm-fx6/flash-header-mx6-cm-fx6.imxcfg b/arch/arm/boards/cm-fx6/flash-header-mx6-cm-fx6.imxcfg
index 400a870154..9e8dce5877 100644
--- a/arch/arm/boards/cm-fx6/flash-header-mx6-cm-fx6.imxcfg
+++ b/arch/arm/boards/cm-fx6/flash-header-mx6-cm-fx6.imxcfg
@@ -1,3 +1,4 @@
soc imx6
loadaddr 0x00907000
+max_load_size 0x11000
dcdofs 0x400
--git a/arch/arm/boards/nxp-imx8mq-evk/flash-header-imx8mq-evk.imxcfg b/arch/arm/boards/nxp-imx8mq-evk/flash-header-imx8mq-evk.imxcfg
index a12c28fceb..14e4a595a0 100644
--- a/arch/arm/boards/nxp-imx8mq-evk/flash-header-imx8mq-evk.imxcfg
+++ b/arch/arm/boards/nxp-imx8mq-evk/flash-header-imx8mq-evk.imxcfg
@@ -1,4 +1,5 @@
soc imx8mq
loadaddr 0x007E1000
+max_load_size 0x10000
dcdofs 0x400
diff --git a/arch/arm/boards/technexion-wandboard/flash-header-technexion-wandboard.imxcfg b/arch/arm/boards/technexion-wandboard/flash-header-technexion-wandboard.imxcfg
index 33621117d4..68cb08e200 100644
--- a/arch/arm/boards/technexion-wandboard/flash-header-technexion-wandboard.imxcfg
+++ b/arch/arm/boards/technexion-wandboard/flash-header-technexion-wandboard.imxcfg
@@ -1,3 +1,4 @@
loadaddr 0x00907000
soc imx6
+max_load_size 0x11000
dcdofs 0x400
--git a/arch/arm/boards/zii-imx6q-rdu2/flash-header-rdu2.imxcfg b/arch/arm/boards/zii-imx6q-rdu2/flash-header-rdu2.imxcfg
index 400a870154..9e8dce5877 100644
--- a/arch/arm/boards/zii-imx6q-rdu2/flash-header-rdu2.imxcfg
+++ b/arch/arm/boards/zii-imx6q-rdu2/flash-header-rdu2.imxcfg
@@ -1,3 +1,4 @@
soc imx6
loadaddr 0x00907000
+max_load_size 0x11000
dcdofs 0x400
--
2.19.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-11-20 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 8:40 [PATCH 0/3] ARM: images: Use piggydata Sascha Hauer
2018-11-20 8:40 ` [PATCH 1/3] scripts: imx-image: Add support for max_load_size option Sascha Hauer
2018-11-20 8:40 ` Sascha Hauer [this message]
2018-11-30 6:11 ` [PATCH 2/3] ARM: i.MX: Add max_load_size option to boards that will need it Andrey Smirnov
2018-11-30 7:35 ` Sascha Hauer
2018-12-01 0:34 ` Andrey Smirnov
2018-11-20 8:41 ` [PATCH 3/3] ARM: images: use piggydata Sascha Hauer
2019-01-14 16:34 ` [PATCH 0/3] ARM: images: Use piggydata Roland Hieber
2019-01-14 17:22 ` Sam Ravnborg
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=20181120084100.8737-3-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox