Message ID | 1438985565-32734-1-git-send-email-swarren@wwwdotorg.org |
---|---|
State | Accepted |
Delegated to: | Tom Warren |
Headers | show |
On 7 August 2015 at 16:12, Stephen Warren <swarren@wwwdotorg.org> wrote: > From: Stephen Warren <swarren@nvidia.com> > > The new value is the most likely value where the kernel wants to end up > at run-time. Selecting this value as the load address likely avoids the > need to copy the kernel image from the actual load address to the desired > load address. Note that this isn't guaranteed since the kernel may wish > to run at an arbitrary location. In that case, U-Boot will still relocate > the image according to its wishes; this change is a performance > optimization, not a hard-coding of the final image location. > > Signed-off-by: Stephen Warren <swarren@nvidia.com> > --- > include/configs/tegra210-common.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Simon Glass <sjg@chromium.org>
diff --git a/include/configs/tegra210-common.h b/include/configs/tegra210-common.h index d95056c00261..e6c815212d7b 100644 --- a/include/configs/tegra210-common.h +++ b/include/configs/tegra210-common.h @@ -55,7 +55,7 @@ * ramdisk_addr_r simply shouldn't overlap anything else. Choosing 33M allows * for the FDT/DTB to be up to 1M, which is hopefully plenty. */ -#define CONFIG_LOADADDR 0x81000000 +#define CONFIG_LOADADDR 0x80080000 #define MEM_LAYOUT_ENV_SETTINGS \ "scriptaddr=0x90000000\0" \ "pxefile_addr_r=0x90100000\0" \