All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] integrator: pass a Device Tree by default
Date: Tue, 22 Jan 2013 14:16:06 +0100	[thread overview]
Message-ID: <201301221416.06389.marex@denx.de> (raw)
In-Reply-To: <CACRpkdamc_4X-BLobAfN1HTbW7hAwAK2n8-F_QDP3Vrugh=atg@mail.gmail.com>

Dear Linus Walleij,

> On Tue, Jan 22, 2013 at 1:04 PM, Marek Vasut <marex@denx.de> wrote:
> >> On Sun, Jan 20, 2013 at 1:53 AM, Marek Vasut <marex@denx.de> wrote:
> >> > Shouldn't the load address be 0x8000 instead of 0x800 (it used to be
> >> > 0x7fc0) ?
> >> 
> >> 0x800 works fine, but honestly I don't know why Peter P ages ago chose
> >> the very odd address 0x7fc0.
> >> 
> >> But you know U-boot way better than me, and most things work fine it
> >> seems. What is a typical load address?
> > 
> > Heh, there ain't any "typical load address", the FDT binary is relocated
> > at the end of RAM just before boot anyway, so I'm ok with any address
> > you pick, just make it a sane one ;)
> 
> OK but 0x7fc0 was the load address for the kernel, so I was sort of
> wondering what a "typical" place to load the kernel would be, because
> 0x7fc0 seems quite arbitrarily chosen...

Indeed. I usually stick FDT far past the kernel, but that's just my preference I 
think.

> Yours,
> Linus Walleij

Best regards,
Marek Vasut

      reply	other threads:[~2013-01-22 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-20  0:49 [U-Boot] [PATCH] integrator: pass a Device Tree by default Linus Walleij
2013-01-20  0:53 ` Marek Vasut
2013-01-22  7:58   ` Linus Walleij
2013-01-22 12:04     ` Marek Vasut
2013-01-22 13:01       ` Linus Walleij
2013-01-22 13:16         ` Marek Vasut [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=201301221416.06389.marex@denx.de \
    --to=marex@denx.de \
    --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.