public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Where to put a large bootloader-supplied device tree on ARM ?
Date: Fri, 13 Jul 2012 08:45:26 +0200	[thread overview]
Message-ID: <20120713084526.5f680de3@lilith> (raw)
In-Reply-To: <4FFF79B6.6040508@gmail.com>

Hi Rob,

On Thu, 12 Jul 2012 20:28:22 -0500, Rob Herring <robherring2@gmail.com> wrote:
> On 07/12/2012 04:47 PM, Wolfgang Denk wrote:
> > Dear Albert ARIBAUD,
> > 
> > In message <20120712233801.0411daa7@lilith> you wrote:
> >>
> >> If I'm not mistaken, yes U-Boot loads itself as high as it can, and I don't
> >> know about the FDT, but no, U-Boot does not "like" to load initrd "just
> >> below that": it loads initrd where the boot commands tell it to, and the
> >> boot commands are written by board developers. Nothing in U-Boot forces
> >> initrd to be loaded as high as possible.
> 
> u-boot loads the initrd where you tell it, then bootm relocates it for
> some reason.
> >>
> >> That leaves the question of the FDT, though -- I'm not familiar enough
> >> with it (yet) to tell if it is always located just under U-Boot or if
> >> its placement is controllable by board commands.
> > 
> > You can always just set the "fdt_high" and "initrd_high" evironment
> > variables to restrict the positioning of initrd and FDT in RAM; see
> > the README for details.
> 
> Yes, I'm aware of all this, but this is not the default behavior and the
> default behavior will not work in this case. It also has another bug
> related to the relocation that I fixed:
> 
> http://www.mail-archive.com/u-boot at lists.denx.de/msg86475.html
> 
> Rob

As for the default behavior, this becomes a board config issue, not a
U-Boot issue.

Regarding the patch, as a bugfix it will go in u-boot-arm/master
for 2012.07.

With all this, do we have the overall issue covered?

Amicalement,
-- 
Albert.

      reply	other threads:[~2012-07-13  6:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1341325365-21393-1-git-send-email-andrew@lunn.ch>
     [not found] ` <201207051454.24475.arnd@arndb.de>
     [not found]   ` <20120705161600.GA28860@lunn.ch>
     [not found]     ` <201207062008.23952.arnd@arndb.de>
     [not found]       ` <20120706210009.GC11470@lunn.ch>
     [not found]         ` <4FF781D8.3040206@firmworks.com>
     [not found]           ` <2966DB01BC317A4DA23684BA0F653415013701@xmb-aln-x08.cisco.com>
     [not found]             ` <4FF7980E.7050705@firmworks.com>
     [not found]               ` <alpine.LFD.2.02.1207090015270.31100@xanadu.home>
     [not found]                 ` <4FFE743B.6080504@firmworks.com>
2012-07-12 20:34                   ` [U-Boot] Where to put a large bootloader-supplied device tree on ARM ? Rob Herring
2012-07-12 21:38                     ` Albert ARIBAUD
2012-07-12 21:47                       ` Wolfgang Denk
2012-07-13  1:28                         ` Rob Herring
2012-07-13  6:45                           ` Albert ARIBAUD [this message]

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=20120713084526.5f680de3@lilith \
    --to=albert.u.boot@aribaud.net \
    --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