public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP4: Set fdt_high for OMAP4 devices to enable booting with Device Tree
Date: Mon, 14 May 2012 09:48:25 -0700	[thread overview]
Message-ID: <20120514164825.GD10008@bill-the-cat> (raw)
In-Reply-To: <1335902708-10788-1-git-send-email-jon-hunter@ti.com>

On Tue, May 01, 2012 at 03:05:08PM -0500, Jon Hunter wrote:
> From: Jon Hunter <jon-hunter@ti.com>
> 
> For OMAP4 boards, such as the panda-es, that have 1GB of memory the linux
> kernel fails to locate the device tree blob on boot. The reason being is that
> u-boot is copying the DT blob to the upper part of RAM when booting the kernel
> and the kernel is unable to access the blob. By setting the fdt_high variable
> to either 0xffffffff (to prevent the copy) or 0xac000000 (704MB boundary
> of memory for OMAP4) the kernel is able to locate the DT blob and boot.
> 
> Based upon following patch by Dirk Behme set the fdt_high variable to allow
> booting with device tree on OMAP4 boards.
> 
> "7e9603e i.mx6q: configs: Add fdt_high and initrd_high variables"
> 
> Cc: Sricharan R <r.sricharan@ti.com>
> Cc: Sandeep Paulraj <s-paulraj@ti.com>
> Cc: Tom Rini <trini@ti.com>
> Signed-off-by: Jon Hunter <jon-hunter@ti.com>

Applied to u-boot-ti/master, thanks.

-- 
Tom

  reply	other threads:[~2012-05-14 16:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01 20:05 [U-Boot] [PATCH] OMAP4: Set fdt_high for OMAP4 devices to enable booting with Device Tree Jon Hunter
2012-05-14 16:48 ` Tom Rini [this message]
     [not found] <1335902462-10724-1-git-send-email-jon-hunter@ti.com>
2012-05-04 11:20 ` R, Sricharan
2012-05-04 14:05   ` Jon Hunter
  -- strict thread matches above, loose matches on Subject: below --
2012-05-04 14:01 Jon Hunter

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=20120514164825.GD10008@bill-the-cat \
    --to=trini@ti.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