am335x/omap3_beagle/omap4/omap5: Re-enable fdt_high relocation
The fdt_high variable controls how high into memory the FDT can be moved as part of booting the kernel. We had been disabling this feature as by default we move to the very top of memory which can often be part of highmem and so not visible to the kernel yet. However, in other cases the kernel BSS can overwrite the FDT at the location we use, and we wouldn't detect this case. The answer is to re-enable relocation, but ensure it will be in kernel-visible memory still. Signed-off-by: Tom Rini <trini@ti.com>
This commit is contained in:
parent
fb5de2bc3d
commit
b42972acef
|
@ -37,7 +37,7 @@
|
|||
#define CONFIG_EXTRA_ENV_SETTINGS \
|
||||
"loadaddr=0x80200000\0" \
|
||||
"fdtaddr=0x80F80000\0" \
|
||||
"fdt_high=0xffffffff\0" \
|
||||
"fdt_high=0xa0000000\0" \
|
||||
"boot_fdt=try\0" \
|
||||
"rdaddr=0x81000000\0" \
|
||||
"bootpart=0:2\0" \
|
||||
|
|
|
@ -193,7 +193,7 @@
|
|||
#define CONFIG_EXTRA_ENV_SETTINGS \
|
||||
"loadaddr=0x80200000\0" \
|
||||
"rdaddr=0x81000000\0" \
|
||||
"fdt_high=0xffffffff\0" \
|
||||
"fdt_high=0xa0000000\0" \
|
||||
"fdtaddr=0x80f80000\0" \
|
||||
"usbtty=cdc_acm\0" \
|
||||
"bootfile=uImage\0" \
|
||||
|
|
|
@ -133,7 +133,7 @@
|
|||
#define CONFIG_EXTRA_ENV_SETTINGS \
|
||||
"loadaddr=0x82000000\0" \
|
||||
"console=ttyO2,115200n8\0" \
|
||||
"fdt_high=0xffffffff\0" \
|
||||
"fdt_high=0xa0000000\0" \
|
||||
"fdtaddr=0x80f80000\0" \
|
||||
"fdtfile=undefined\0" \
|
||||
"bootpart=0:2\0" \
|
||||
|
|
|
@ -72,7 +72,7 @@
|
|||
#define CONFIG_EXTRA_ENV_SETTINGS \
|
||||
"loadaddr=0x80200000\0" \
|
||||
"fdtaddr=0x80F80000\0" \
|
||||
"fdt_high=0xffffffff\0" \
|
||||
"fdt_high=0xa0000000\0" \
|
||||
"rdaddr=0x81000000\0" \
|
||||
"console=" CONSOLEDEV ",115200n8\0" \
|
||||
"fdtfile=undefined\0" \
|
||||
|
|
Loading…
Reference in New Issue