From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Wed, 25 Feb 2015 16:31:50 -0700
Subject: [U-Boot] [PATCH 20/20] tegra: config: nyan-big: Add options
 required by Chrome OS boot
In-Reply-To: <1424212195-7501-21-git-send-email-sjg@chromium.org>
References: <1424212195-7501-1-git-send-email-sjg@chromium.org>
 <1424212195-7501-21-git-send-email-sjg@chromium.org>
Message-ID: <54EE5B66.7040003@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 02/17/2015 03:29 PM, Simon Glass wrote:
> We need to match the device tree in the FIT with the U-Boot model so we
> can automatically select the right device tree. Also adjust the load address
> so that the device tree is not in the way when a zImage kernel tries to
> extract itself.

We don't tend to use LOADADDR in any of the default boot scripts any 
more. Rather, we explicitly load files to a "semantic" location 
indicated by one of the following variables in tegra124-common.h:

#define MEM_LAYOUT_ENV_SETTINGS \
         "scriptaddr=0x90000000\0" \
         "pxefile_addr_r=0x90100000\0" \
         "kernel_addr_r=0x81000000\0" \
         "fdt_addr_r=0x82000000\0" \
         "ramdisk_addr_r=0x82100000\0"

Perhaps the ChromeOS boot scripts could be adjusted to use one/some of 
those variables?

If the value of CONFIG_LOADADDR isn't appropriate, perhaps we should fix 
it for all Tegra SoCs/boards?