From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Avoiding reload on ARM U-BOOT
Date: Fri, 3 Feb 2012 09:15:22 +0100 [thread overview]
Message-ID: <201202030915.23060.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAN2=dsw9rAkzKftow5Opo5vpXFiUz90i7941+WfViwN_BwqAkA@mail.gmail.com>
> 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 <marek.vasut@gmail.com> 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
next prev parent reply other threads:[~2012-02-03 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 15:03 [U-Boot] Avoiding reload on ARM U-BOOT yehuda80
2012-02-02 19:34 ` Marek Vasut
[not found] ` <CAN2=dsw9rAkzKftow5Opo5vpXFiUz90i7941+WfViwN_BwqAkA@mail.gmail.com>
2012-02-03 8:15 ` Marek Vasut [this message]
2012-02-05 14:08 ` yehuda yitchak
2012-02-05 14:22 ` Marek Vasut
2012-02-05 15:09 ` Stefano Babic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201202030915.23060.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox