openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Troy Lee <troy_lee@aspeedtech.com>
To: <leetroy@gmail.com>, <openbmc@lists.ozlabs.org>, <joel@jms.id.au>
Subject: [PATCH u-boot v2019.04-aspeed-openbmc v1 2/2] ast2600: Provide u-boot FIT image boot from RAM offset
Date: Wed, 23 Jun 2021 11:57:55 +0800	[thread overview]
Message-ID: <20210623035755.32742-2-troy_lee@aspeedtech.com> (raw)
In-Reply-To: <20210623035755.32742-1-troy_lee@aspeedtech.com>

If BOOT_DEVICE_RAM is selected, CONFIG_SPL_LOAD_FIT_ADDRESS will be
required in loader spl/spl_ram.c, and the offset is 64KiB.

Signed-off-by: Troy Lee <troy_lee@aspeedtech.com>
---
 include/configs/evb_ast2600_spl.h   | 1 +
 include/configs/evb_ast2600a1_spl.h | 1 +
 2 files changed, 2 insertions(+)

diff --git a/include/configs/evb_ast2600_spl.h b/include/configs/evb_ast2600_spl.h
index a39988820a..f4f1b46d89 100644
--- a/include/configs/evb_ast2600_spl.h
+++ b/include/configs/evb_ast2600_spl.h
@@ -29,6 +29,7 @@
 #define CONFIG_SPL_STACK		0x10016000
 #define CONFIG_SPL_BSS_START_ADDR	0x90000000
 #define CONFIG_SPL_BSS_MAX_SIZE		0x00100000
+#define CONFIG_SPL_LOAD_FIT_ADDRESS     0x00010000
 
 #define CONFIG_SUPPORT_EMMC_BOOT
 
diff --git a/include/configs/evb_ast2600a1_spl.h b/include/configs/evb_ast2600a1_spl.h
index a39988820a..f4f1b46d89 100644
--- a/include/configs/evb_ast2600a1_spl.h
+++ b/include/configs/evb_ast2600a1_spl.h
@@ -29,6 +29,7 @@
 #define CONFIG_SPL_STACK		0x10016000
 #define CONFIG_SPL_BSS_START_ADDR	0x90000000
 #define CONFIG_SPL_BSS_MAX_SIZE		0x00100000
+#define CONFIG_SPL_LOAD_FIT_ADDRESS     0x00010000
 
 #define CONFIG_SUPPORT_EMMC_BOOT
 
-- 
2.17.1


      reply	other threads:[~2021-06-23  3:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23  3:57 [PATCH u-boot v2019.04-aspeed-openbmc v1 1/2] ast2600: spl: Fixes boot from RAM device Troy Lee
2021-06-23  3:57 ` Troy Lee [this message]

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=20210623035755.32742-2-troy_lee@aspeedtech.com \
    --to=troy_lee@aspeedtech.com \
    --cc=joel@jms.id.au \
    --cc=leetroy@gmail.com \
    --cc=openbmc@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).