From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Fri, 3 Feb 2012 09:15:22 +0100 Subject: [U-Boot] Avoiding reload on ARM U-BOOT In-Reply-To: References: <33250726.post@talk.nabble.com> <201202022034.37200.marek.vasut@gmail.com> Message-ID: <201202030915.23060.marek.vasut@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de > 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. Though it still can't place the bootloader properly to the end of DRAM. > > in previous version there was a way to avoid this. i find it limiting that > there isn't a way in the new version. > > Why would i want to relocate the code anyway ? See above, to place it to the end of DRAM. > > Yehuda > > On Thu, Feb 2, 2012 at 11:34 AM, Marek Vasut wrote: > > > 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. And it's quite a quick process. So if you are manufacturing your > > soc with > > various size of RAM, you want the relocation to happen. What SoC is that > > anyway? > > > > > is there any clean way to avoid relocating the u-boot ? does the > > > various SPL configs have something to do with that ? > > > > Not really and you don't want this to happen. > > > > M > > > > > if yes which one should i define ? > > > > > > Thanks in advance > > > > > > Yehuda