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] RFC: U-Boot OneNAND IPL TEXT_BASE
Date: Sat, 1 May 2010 04:48:10 +0200	[thread overview]
Message-ID: <201005010448.10647.marek.vasut@gmail.com> (raw)

Hey,

I've been tinkering with OneNAND IPL in uboot. I found out it wan't to load 
itself to the address specified in board/$(BOARDDIR)/config.mk . That's fine in 
most cases, but in my case that wasn't possible.

In my case, SDRAM init didn't fit into the IPL, so I had to copy U-Boot into 
SRAM, then execute it and let it relocate itself into SDRAM. One more time:
IPL: OneNAND->SRAM
U-Boot: SRAM->SDRAM

It all works fine, but when compiling the IPL, I had to alter TEXT_BASE not to 
point into SDRAM but SRAM too (because of stack). I introduced a variable called 
IPL which allows using config.mk from (for example) onenand-
ipl/board/$(BOARDDIR)/config.mk rather than the board/$(BOARDDIR)/config.mk one, 
which is in my opinion a correct behaviour.

Any opinions?

Thanks in advance.

diff --git a/config.mk b/config.mk
index 73b5195..8639580 100644
--- a/config.mk
+++ b/config.mk
@@ -130,9 +130,13 @@ BOARDDIR = $(VENDOR)/$(BOARD)
 else
 BOARDDIR = $(BOARD)
 endif
+ifdef  IPL
+sinclude $(TOPDIR)/$(IPL)/board/$(BOARDDIR)/config.mk  # include IPL specific 
rules
+else
 ifdef  BOARD
 sinclude $(TOPDIR)/board/$(BOARDDIR)/config.mk # include board specific rules
 endif
+endif
 
 #########################################################################
 

             reply	other threads:[~2010-05-01  2:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-01  2:48 Marek Vasut [this message]
2010-05-02  3:54 ` [U-Boot] RFC: U-Boot OneNAND IPL TEXT_BASE Kyungmin Park
2010-05-02  6:39   ` Marek Vasut
2010-05-02 11:07     ` Kyungmin Park
2010-05-02 15:21       ` 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=201005010448.10647.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