On Tue, May 01, 2012 at 03:05:08PM -0500, Jon Hunter wrote:
From: Jon Hunter jon-hun...@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
Jon,
[snip]
--- a/include/configs/omap4_common.h
+++ b/include/configs/omap4_common.h
@@ -151,6 +151,7 @@
#define CONFIG_EXTRA_ENV_SETTINGS \
loadaddr=0x8200\0 \
console=ttyO2,115200n8\0 \
+ fdt_high=0x\0 \
Tested this on mainline and worked fine on
From: Jon Hunter jon-hun...@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
Hi Sricharan,
On 05/04/2012 06:20 AM, R, Sricharan wrote:
Jon,
[snip]
--- a/include/configs/omap4_common.h
+++ b/include/configs/omap4_common.h
@@ -151,6 +151,7 @@
#define CONFIG_EXTRA_ENV_SETTINGS \
loadaddr=0x8200\0 \
console=ttyO2,115200n8\0 \
+
From: Jon Hunter jon-hun...@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
5 matches
Mail list logo