[U-Boot] [u-boot][PATCH] omap3_beagle: Fix device tree boot

[Roger Quadros]

Tom,

On 06/03/15 18:28, Tom Rini wrote:
> On Fri, Mar 06, 2015 at 05:34:24PM +0200, Roger Quadros wrote:
> 
>> Don't redefine fdtaddr and other values that are already defined in
>> ti_armv7_common.h. The value of fdtaddr in ti_armv7_common.h is
>> more appropriate as it allows a larger kernel image to be loaded.
>>
>> With this change, I'm able to boot linux-4.0-rc1 with device tree blob.
>>
>> Signed-off-by: Roger Quadros <rogerq at ti.com>
>> ---
>>  include/configs/omap3_beagle.h | 4 +---
>>  1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h
>> index f25a940..3ea9b08 100644
>> --- a/include/configs/omap3_beagle.h
>> +++ b/include/configs/omap3_beagle.h
>> @@ -129,10 +129,8 @@
>>  							/* devices */
>>  
>>  #define CONFIG_EXTRA_ENV_SETTINGS \
>> -	"loadaddr=0x80200000\0" \
>> -	"rdaddr=0x81000000\0" \
>> +	DEFAULT_LINUX_BOOT_ENV \
>>  	"fdt_high=0xffffffff\0" \
>> -	"fdtaddr=0x80f80000\0" \
>>  	"usbtty=cdc_acm\0" \
>>  	"bootfile=uImage\0" \
>>  	"ramdisk=ramdisk.gz\0" \
> 
> With DEFAULT_LINUX_BOOT_ENV the bootm_size variable makes sure that we
> relocate the DT within the area that the kernel will see and we don't
> need fdt_high being set either.
> 

I tried without fdt_high and the board wasn't booting. So we're still missing
something for the omap3_beagle w.r.t that.
Any clues?

cheers,
-roger