public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] OneNAND: Introduce CONFIG_SYS_IPL_LOAD_ADDR
Date: Sat,  2 Oct 2010 19:33:58 +0200	[thread overview]
Message-ID: <1286040839-3215-3-git-send-email-marek.vasut@gmail.com> (raw)
In-Reply-To: <1286040839-3215-1-git-send-email-marek.vasut@gmail.com>

This allows to specify where the OneNAND IPL should load the U-Boot binary. The
purpose of CONFIG_SYS_LOAD_ADDR is different I believe.

On PXA, this is needed with OneNAND memories that expose only first 1kb of data,
which is insufficient for SDRAM init. U-Boot can then be copied into SRAM.

Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
---
 include/configs/apollon.h  |    1 +
 onenand_ipl/onenand_boot.c |    4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/include/configs/apollon.h b/include/configs/apollon.h
index c1295de..d34e24d 100644
--- a/include/configs/apollon.h
+++ b/include/configs/apollon.h
@@ -199,6 +199,7 @@
 
 /* default load address */
 #define	CONFIG_SYS_LOAD_ADDR	(OMAP2420_SDRC_CS0)
+#define	CONFIG_SYS_IPL_LOAD_ADDR	(OMAP2420_SDRC_CS0)
 
 /* The 2420 has 12 GP timers, they can be driven by the SysClk (12/13/19.2)
  * or by 32KHz clk, or from external sig. This rate is divided by a local
diff --git a/onenand_ipl/onenand_boot.c b/onenand_ipl/onenand_boot.c
index 22baebb..2a0c7ce 100644
--- a/onenand_ipl/onenand_boot.c
+++ b/onenand_ipl/onenand_boot.c
@@ -33,11 +33,11 @@ void start_oneboot(void)
 {
 	uchar *buf;
 
-	buf = (uchar *) CONFIG_SYS_LOAD_ADDR;
+	buf = (uchar *) CONFIG_SYS_IPL_LOAD_ADDR;
 
 	onenand_read_block(buf);
 
-	((init_fnc_t *)CONFIG_SYS_LOAD_ADDR)();
+	((init_fnc_t *)CONFIG_SYS_IPL_LOAD_ADDR)();
 
 	/* should never come here */
 }
-- 
1.7.1

  parent reply	other threads:[~2010-10-02 17:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-02 17:33 [U-Boot] [PATCH 1/4] OneNAND: Move largepage_memorybased Marek Vasut
2010-10-02 17:33 ` [U-Boot] [PATCH 2/4] OneNAND: Fixup command table on reloc Marek Vasut
2010-10-02 18:28   ` Minkyu Kang
2010-10-02 18:59     ` Marek Vasut
2010-10-02 19:31       ` Minkyu Kang
2010-10-03 18:21       ` Wolfgang Denk
2010-10-03 19:24         ` Marek Vasut
2010-10-03 21:16           ` Wolfgang Denk
2010-10-03 11:19   ` Sergei Shtylyov
2010-10-03 14:25     ` Marek Vasut
2010-10-03 18:39       ` Wolfgang Denk
2010-10-02 17:33 ` Marek Vasut [this message]
2010-10-03  6:40   ` [U-Boot] [PATCH 3/4] OneNAND: Introduce CONFIG_SYS_IPL_LOAD_ADDR Kyungmin Park
2010-10-03 14:25     ` Marek Vasut
2010-10-02 17:33 ` [U-Boot] [PATCH 4/4] OneNAND: Use generic_onenand_read_page in IPL Marek Vasut
2010-10-03  6:40   ` Kyungmin Park
2010-10-03 14:27     ` Marek Vasut
2010-10-03 23:33       ` Marek Vasut
2010-10-03 23:45         ` Kyungmin Park
2010-10-04  0:24           ` Marek Vasut
2010-10-04  6:05             ` Wolfgang Denk
2010-10-14 21:15           ` Marek Vasut
2010-10-04 18:09   ` Scott Wood
2010-10-04  0:23 ` [U-Boot] [PATCH 1/4] OneNAND: Move largepage_memorybased Marek Vasut
2010-10-04 17:59 ` Scott Wood
2010-10-04 21:15   ` Marek Vasut
2010-10-04 21:18     ` Scott Wood
2010-10-04 22:31       ` Marek Vasut
2010-10-05  2:05         ` Kyungmin Park
2010-10-05  2:36           ` Marek Vasut

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=1286040839-3215-3-git-send-email-marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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