public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] One basic U-boot question
Date: Wed, 12 Dec 2012 15:36:37 -0600	[thread overview]
Message-ID: <1355348197.28445.9@snotra> (raw)
In-Reply-To: <50C83C42.5090307@ronetix.at> (from martin@ronetix.at on Wed Dec 12 02:11:46 2012)

On 12/12/2012 02:11:46 AM, Martin Peevski wrote:
>     Hello, I have the following question. It is about the adresses  
> where the U-boot and  Linux Kernel are copyed in the SDRAM from NAND.
> 
>     In my board config file I have:
>     #define CONFIG_SYS_LOAD_ADDR        0x22000000    /* load address  
> */
>     Is that the load address of the U-boot?

No, it's the default address to load the kernel (or other image).  Note  
that this is where the uImage goes, not where the kernel gets  
uncompressed to (which is specified in the uImage header).

U-Boot is loaded near the top of SDRAM (or the portion of SDRAM that  
U-Boot has mapped).

BTW, you should use a subject line that is more specific to your  
question, such as "What is CONFIG_SYS_LOAD_ADDR?" or "Where does the  
kernel get loaded with <command name>?".  "One basic U-Boot question"  
doesn't give any clues to people skimming the list to see if it's the  
sort of question they might have the answer to.

>     Also where is defined the load address of the Kernel because may  
> be I need to leave more free space about the Kernel and RootFS?

CONFIG_SYS_LOAD_ADDR is the default, but you can and should override it  
in the arguments to the command doing the loading.

-Scott

      reply	other threads:[~2012-12-12 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12  8:11 [U-Boot] One basic U-boot question Martin Peevski
2012-12-12 21:36 ` Scott Wood [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=1355348197.28445.9@snotra \
    --to=scottwood@freescale.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