From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] rockchip: config: sync the ENV offset from rockchip legacy U-Boot
Date: Tue, 31 Oct 2017 15:52:19 +0800 [thread overview]
Message-ID: <1509436340-12872-1-git-send-email-kever.yang@rock-chips.com> (raw)
Using the ENV offset from rockchip legacy U-Boot for all SoCs,
the offset is 4MB-32KB
Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
---
include/configs/rockchip-common.h | 15 +++------------
1 file changed, 3 insertions(+), 12 deletions(-)
diff --git a/include/configs/rockchip-common.h b/include/configs/rockchip-common.h
index 96b5fce..3fc1b71 100644
--- a/include/configs/rockchip-common.h
+++ b/include/configs/rockchip-common.h
@@ -61,19 +61,10 @@
#endif
-#if CONFIG_IS_ENABLED(ROCKCHIP_BACK_TO_BROM)
-/* SPL @ 32k for 34k
- * u-boot directly after @ 68k for 400k or so
- * ENV @ 992k
- */
-#define CONFIG_ENV_OFFSET ((1024-32) * 1024)
-#else
-/* SPL @ 32k for ~36k
- * ENV @ 96k
- * u-boot @ 128K
+/*
+ * Rockchip SoCs use fixed ENV 32KB@(4MB-32KB)
*/
-#define CONFIG_ENV_OFFSET (96 * 1024)
-#endif
+#define CONFIG_ENV_OFFSET (SZ_4M - SZ_32K)
#define CONFIG_DISPLAY_BOARDINFO_LATE
--
1.9.1
next reply other threads:[~2017-10-31 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 7:52 Kever Yang [this message]
2017-10-31 7:52 ` [U-Boot] [PATCH 2/2] rockchip: config: use common CONFIG_ENV_SIZE for all SoCs Kever Yang
2017-11-06 17:28 ` [U-Boot] [U-Boot, " Philipp Tomsich
2017-11-06 17:29 ` Philipp Tomsich
2017-11-06 17:47 ` Philipp Tomsich
2017-11-03 9:45 ` [U-Boot] [PATCH 1/2] rockchip: config: sync the ENV offset from rockchip legacy U-Boot Dr. Philipp Tomsich
2017-11-06 9:57 ` Kever Yang
2017-11-06 17:28 ` [U-Boot] [U-Boot, " Philipp Tomsich
2017-11-06 17:29 ` Philipp Tomsich
2017-11-06 17:47 ` Philipp Tomsich
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=1509436340-12872-1-git-send-email-kever.yang@rock-chips.com \
--to=kever.yang@rock-chips.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.