All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: rmobile: Convert to bootm_size
Date: Tue, 27 Nov 2018 20:23:38 -0500	[thread overview]
Message-ID: <20181128012338.GG11247@bill-the-cat> (raw)
In-Reply-To: <CAAh8qswArOG+1R_qiPgRJNhkwPqWsx84gLm6wFsCVmmiTAeOSg@mail.gmail.com>

On Tue, Nov 27, 2018 at 08:03:04AM +0100, Simon Goldschmidt wrote:

> On Tue, Nov 27, 2018 at 1:11 AM Marek Vasut <marek.vasut@gmail.com> wrote:
> >
> > Convert all Renesas R-Car boards to bootm_size of 256 MiB and drop both
> > fdt_high and initrd_high. This change implies that the FDT and initrd
> > will always be copied into the first 256 MiB of RAM instead of being
> > used in place, which can cause various kinds of inobvious problems.
> >
> > The simpler problems include FDT or initrd being overwritten or being
> > used from unaligned addresses, especially on ARM64. The overhead of
> > copying the FDT to aligned location is negligible and these problems
> > go away, so the benefit is significant.
> >
> > Regarding alignment problems with fitImage. The alignment of DT properties
> > is always 32 bits, which implies that the alignment of the "data" property
> > in fitImage is also 32 bits. The /incbin/ syntax plays no role here. The
> > kernel expects all elements, including DT and initrd, to be aligned to
> > 64 bits on ARM64, thus using them in place may not be possible. Using the
> > bootm_size assures correct alignment, again with negligible overhead.
> 
> In my opinion, all of these raw addresses defined in scripts or config
> should be removed: They are probably vulnerable to overwriting
> themselves as they only provide an address, not a range.
> 
> Just out of curiosity: is it required to put fdt and initrd into the
> first 256 MiB or is this just some 'random' limit to ensure we use lmb

It's the smallest limit that both gives us room for fairly large
ramdisks, kernels and device tree yet will still be within lowmem for
Linux and otherwise meet the requirements of both
linux/Documentation/arm/Booting and linux/Documentation/arm64/booting.txt

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181127/0aff0888/attachment.sig>

  parent reply	other threads:[~2018-11-28  1:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  0:10 [U-Boot] [PATCH] ARM: rmobile: Convert to bootm_size Marek Vasut
2018-11-27  7:03 ` Simon Goldschmidt
2018-11-27 12:20   ` Marek Vasut
2018-11-27 12:33     ` Simon Goldschmidt
2018-11-27 13:09       ` Marek Vasut
2018-11-27 15:26         ` Simon Goldschmidt
2018-11-27 15:47           ` Marek Vasut
2018-11-27 18:31             ` Simon Goldschmidt
2018-11-27 19:06               ` Marek Vasut
2018-11-28  1:31               ` Tom Rini
2018-11-28  8:46                 ` Simon Goldschmidt
2018-11-28 12:19                   ` Tom Rini
2018-11-28 20:55                     ` Simon Goldschmidt
2019-03-05 18:42                       ` Eugeniu Rosca
2019-03-05 18:56                         ` Marek Vasut
2019-03-05 22:28                           ` Eugeniu Rosca
2019-03-05 22:57                             ` Marek Vasut
2018-11-28  1:23   ` Tom Rini [this message]
2018-11-27 12:17 ` Tom Rini

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=20181128012338.GG11247@bill-the-cat \
    --to=trini@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.