From: Tom Rini <trini@konsulko.com>
To: Sjoerd Simons <sjoerd@collabora.com>
Cc: u-boot@lists.denx.de, Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Kautuk Consul <kconsul@ventanamicro.com>,
Leo Yu-Chi Liang <ycliang@andestech.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: Re: [PATCH 1/3] Bump LMB_MAX_REGIONS default to 16
Date: Thu, 26 Jan 2023 13:28:19 -0500 [thread overview]
Message-ID: <Y9LGQ8PGKJSAXFSr@bill-the-cat> (raw)
In-Reply-To: <20230119083820.2656710-2-sjoerd@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
On Thu, Jan 19, 2023 at 09:38:17AM +0100, Sjoerd Simons wrote:
> Since commit 06d514d77c37 ("lmb: consider EFI memory map") the EFI regions
> are also pushed into the lmb if EFI_LOADER is enabled (which is by
> default on most system). Which can cause the number of entries to go
> over the maximum as it's default is only 8.
>
> Specifically i ran into this case on an TI am62 which has an fdt with
> 4 reserved regions (in practice 3 lmb entries due to adjecent ranges).
>
> As this is likely to impact more devices bump the default max
> regions to 16 so there is a bit more slack.
>
> Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>
I prefer to use:
https://patchwork.ozlabs.org/project/uboot/patch/20230125230823.1567778-1-trini@konsulko.com/
in this case due to it being overall a smaller size increase.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-01-26 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 8:38 [PATCH 0/3] Fix boot regressions on at least TI am62x Sjoerd Simons
2023-01-19 8:38 ` [PATCH 1/3] Bump LMB_MAX_REGIONS default to 16 Sjoerd Simons
2023-01-26 18:28 ` Tom Rini [this message]
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=Y9LGQ8PGKJSAXFSr@bill-the-cat \
--to=trini@konsulko.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kconsul@ventanamicro.com \
--cc=philippe.reynes@softathome.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=sjg@chromium.org \
--cc=sjoerd@collabora.com \
--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