public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sjoerd Simons <sjoerd@collabora.com>
To: u-boot@lists.denx.de
Cc: Ashok Reddy Soma <ashok.reddy.soma@xilinx.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Kautuk Consul <kconsul@ventanamicro.com>,
	Leo Yu-Chi Liang <ycliang@andestech.com>,
	Michal Simek <michal.simek@amd.com>,
	Patrice Chotard <patrice.chotard@foss.st.com>,
	Philippe Reynes <philippe.reynes@softathome.com>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	Simon Glass <sjg@chromium.org>,
	Sughosh Ganu <sughosh.ganu@linaro.org>
Subject: [PATCH 0/3] Fix boot regressions on at least TI am62x
Date: Thu, 19 Jan 2023 09:38:16 +0100	[thread overview]
Message-ID: <20230119083820.2656710-1-sjoerd@collabora.com> (raw)


When booting a recent u-boot master on TI am62x with the distro boot
sequence it fails loading the FDT:

   Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
   Loading Ramdisk to 8d711000, end 8ffffd95 ... OK
ERROR: reserving fdt memory region failed (addr=9e780000 size=80000 flags=4)
ERROR: reserving fdt memory region failed (addr=9e800000 size=1800000 flags=4)
ERROR: reserving fdt memory region failed (addr=9db00000 size=c00000 flags=4)
ERROR: Failed to allocate 0x8f58 bytes below 0x90000000.
device tree - allocation error
FDT creation failed!
resetting ...

It turns out that this is caused by commit 06d514d77c37 ("lmb: consider EFI
memory map") due to injecting both extra and some similar memory regions
via a different path into the lmb. The following series fixes the
apparent fallout from that ;)


Sjoerd Simons (3):
  Bump LMB_MAX_REGIONS default to 16
  lmb: Set correct lmb flags for EFI memory map entries
  lmb: Treat a region which is a subset as equal

 lib/Kconfig |  2 +-
 lib/lmb.c   | 15 +++++++++------
 2 files changed, 10 insertions(+), 7 deletions(-)

-- 
2.39.0


             reply	other threads:[~2023-01-19  8:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19  8:38 Sjoerd Simons [this message]
2023-01-19  8:38 ` [PATCH 1/3] Bump LMB_MAX_REGIONS default to 16 Sjoerd Simons
2023-01-26 18:28   ` Tom Rini
2023-01-27  7:55     ` Sjoerd Simons
2023-01-27 13:22       ` Tom Rini
2023-02-08 20:00   ` Tom Rini
2023-01-19  8:38 ` [PATCH 2/3] lmb: Set correct lmb flags for EFI memory map entries Sjoerd Simons
2023-02-07 16:49   ` Tom Rini
2023-01-19  8:38 ` [PATCH 3/3] lmb: Treat a region which is a subset as equal Sjoerd Simons
2023-02-06 18:04   ` Tom Rini
2023-02-08  7:37     ` Sjoerd Simons
2023-02-08 14:55       ` 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=20230119083820.2656710-1-sjoerd@collabora.com \
    --to=sjoerd@collabora.com \
    --cc=ashok.reddy.soma@xilinx.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kconsul@ventanamicro.com \
    --cc=michal.simek@amd.com \
    --cc=patrice.chotard@foss.st.com \
    --cc=philippe.reynes@softathome.com \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=sjg@chromium.org \
    --cc=sughosh.ganu@linaro.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    --cc=ycliang@andestech.com \
    /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