Re: [U-Boot] [PATCH] OMAP4: Set fdt_high for OMAP4 devices to enable booting with Device Tree
On Tue, May 01, 2012 at 03:05:08PM -0500, Jon Hunter wrote: > From: Jon Hunter > > 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 0x (to prevent the copy) or 0xac00 (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 > Cc: Sandeep Paulraj > Cc: Tom Rini > Signed-off-by: Jon Hunter Applied to u-boot-ti/master, thanks. -- Tom ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] OMAP4: Set fdt_high for OMAP4 devices to enable booting with Device Tree
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" \ >> + "fdt_high=0x\0" \ > > Tested this on mainline and worked fine on 4430SDP. > > Tested the same on u-boot-arm, but did not work there. > Not sure what i am missing. Thanks. I have not tried uboot-arm branch. I am guess that DT booting does not work on the uboot-arm branch with or without this patch. Correct? BTW, I just resent the original patch to the ML as the first version did not seem to make it. Cheers Jon ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] [PATCH] OMAP4: Set fdt_high for OMAP4 devices to enable booting with Device Tree
From: Jon Hunter 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 0x (to prevent the copy) or 0xac00 (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 Cc: Sandeep Paulraj Cc: Tom Rini Signed-off-by: Jon Hunter --- include/configs/omap4_common.h |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/include/configs/omap4_common.h b/include/configs/omap4_common.h index a989721..d31cbb5 100644 --- 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" \ "usbtty=cdc_acm\0" \ "vram=16M\0" \ "mmcdev=0\0" \ -- 1.7.5.4 ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] OMAP4: Set fdt_high for OMAP4 devices to enable booting with Device Tree
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 4430SDP. Tested the same on u-boot-arm, but did not work there. Not sure what i am missing. Thanks, Sricharan ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] [PATCH] OMAP4: Set fdt_high for OMAP4 devices to enable booting with Device Tree
From: Jon Hunter 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 0x (to prevent the copy) or 0xac00 (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 Cc: Sandeep Paulraj Cc: Tom Rini Signed-off-by: Jon Hunter --- include/configs/omap4_common.h |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/include/configs/omap4_common.h b/include/configs/omap4_common.h index a989721..d31cbb5 100644 --- 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" \ "usbtty=cdc_acm\0" \ "vram=16M\0" \ "mmcdev=0\0" \ -- 1.7.5.4 ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
