Hello again
Sorry for slipping the u-boot list e-mail address
i understand the benefit of relocating u-boot to the end of DRAM but in
systems where boot time is critical this redundant copy is undesirable.
anyway i understand there is no official way of avoiding it.
One more question i have is
Hello again
Sorry for slipping the u-boot list e-mail address
i understand the benefit of relocating u-boot to the end of DRAM but in
systems where boot time is critical this redundant copy is undesirable.
anyway i understand there is no official way of avoiding it.
You can boot linux
On 05/02/2012 15:22, Marek Vasut wrote:
Hello again
Sorry for slipping the u-boot list e-mail address
i understand the benefit of relocating u-boot to the end of DRAM but in
systems where boot time is critical this redundant copy is undesirable.
anyway i understand there is no official way
Hello Marek
ALWAYS CC U-BOOT ML
Thank you for your answer
My SOC (Marvells Armada Controller) uses a bootrom code to copy to
initialize the DRAM and to copy the u-boot image. so the entire DRAM init
and copy sequence in u-boot is redundant.
I see. I know about this soc's bootrom.
something to do with that ?
if yes which one should i define ?
Thanks in advance
Yehuda
--
View this message in context:
http://old.nabble.com/Avoiding-reload-on-ARM-U-BOOT-tp33250726p33250726.html
Sent from the Uboot - Users mailing list archive at Nabble.com
Hello everyone
im trying to port u-boot 2011-09 to a new board with an arm based SOC
i found that u-boot will always relocate the code even if it is placed
already in DDR which is the case with my SOC.
The u-boot is always relocated to the end of the DRAM, which is likely what you
want.
6 matches
Mail list logo
