diff options
| author | Jon Hunter <jon-hunter@ti.com> | 2012-05-01 10:05:08 +0000 |
|---|---|---|
| committer | Albert ARIBAUD <albert.u.boot@aribaud.net> | 2012-05-15 08:31:41 +0200 |
| commit | c176dd0442c40d4e98c86848091f628707f9c50a (patch) | |
| tree | 56525b2ccf47bf795f3410694ef1e0b58c0130ef /arch/arm/cpu/arm1136 | |
| parent | 2d622b03f8d6dd47889ead0a4f5924c02a421df7 (diff) | |
| download | u-boot-imx-c176dd0442c40d4e98c86848091f628707f9c50a.zip u-boot-imx-c176dd0442c40d4e98c86848091f628707f9c50a.tar.gz u-boot-imx-c176dd0442c40d4e98c86848091f628707f9c50a.tar.bz2 | |
OMAP4: Set fdt_high for OMAP4 devices to enable booting with Device Tree
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>
Diffstat (limited to 'arch/arm/cpu/arm1136')
0 files changed, 0 insertions, 0 deletions