public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: <rs@ti.com>
To: <robertcnelson@gmail.com>, <ayush@beagleboard.org>,
	<Erik.Welsh@octavosystems.com>, <anshuld@ti.com>, <bb@ti.com>,
	<trini@konsulko.com>, <afd@ti.com>, <xypron.glpk@gmx.de>,
	<ilias.apalodimas@linaro.org>
Cc: <u-boot@lists.denx.de>
Subject: [PATCH 0/6] various memory related fixups
Date: Wed, 1 Apr 2026 19:14:04 -0500	[thread overview]
Message-ID: <20260402001410.3736815-1-rs@ti.com> (raw)

From: Randolph Sapp <rs@ti.com>

Nitpicks and fixes from the discovery thread on adding PocketBeagle2 support
[1]. This does a lot of general setup required for the device, but these
modifications themselves aren't device specific. For those specifically
interested in PocketBeagle2 support and don't care about these details, my
development branch is public [2].

That first patch may provoke some opinions, but honestly if that warning was
still present I wouldn't have spent a week poking holes in both the EFI and LMB
allocations systems. Please let me know if there is a specific usecase that it
breaks though.

[1] https://lore.kernel.org/all/DHHC66BBMD27.YHGIH43C6XBK@ti.com/
[2] https://github.com/StaticRocket/u-boot/tree/feature/pocketbeagle2

Randolph Sapp (6):
  lmb: add LMB_FDT for fdt reserved regions
  efi_dt_fixup: use fdtdec_get_bool
  efi_selftest_memory: check for duplicates first
  efi_memory: nitpick removal loop
  efi_memory: backfill EFI_CONVENTIONAL_MEMORY
  memory: reserve from start_addr_sp to relocaddr

 boot/image-fdt.c                       |  5 +++-
 include/lmb.h                          |  7 +++++
 lib/efi_loader/efi_dt_fixup.c          |  3 +-
 lib/efi_loader/efi_memory.c            | 41 ++++++++++++++++++++++----
 lib/efi_selftest/efi_selftest_memory.c | 21 +++++++------
 lib/lmb.c                              | 25 +++++++++++++++-
 6 files changed, 82 insertions(+), 20 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-04-02  0:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02  0:14 rs [this message]
2026-04-02  0:14 ` [PATCH 1/6] lmb: add LMB_FDT for fdt reserved regions rs
2026-04-02  0:36   ` Randolph Sapp
2026-04-02  0:14 ` [PATCH 2/6] efi_dt_fixup: use fdtdec_get_bool rs
2026-04-02  8:38   ` Ilias Apalodimas
2026-04-02  0:14 ` [PATCH 3/6] efi_selftest_memory: check for duplicates first rs
2026-04-02  0:14 ` [PATCH 4/6] efi_memory: nitpick removal loop rs
2026-04-02  9:04   ` Ilias Apalodimas
2026-04-02 17:39     ` Randolph Sapp
2026-04-02 19:02       ` Ilias Apalodimas
2026-04-02 19:21         ` Randolph Sapp
2026-04-02  0:14 ` [PATCH 5/6] efi_memory: backfill EFI_CONVENTIONAL_MEMORY rs
2026-04-02  8:53   ` Ilias Apalodimas
2026-04-02 17:32     ` Randolph Sapp
2026-04-02 19:58       ` Randolph Sapp
2026-04-03  5:28         ` Ilias Apalodimas
2026-04-04  0:08           ` Randolph Sapp
2026-04-02  0:14 ` [PATCH 6/6] memory: reserve from start_addr_sp to relocaddr rs
2026-04-02  9:21   ` Ilias Apalodimas
2026-04-02 19:15     ` Randolph Sapp

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=20260402001410.3736815-1-rs@ti.com \
    --to=rs@ti.com \
    --cc=Erik.Welsh@octavosystems.com \
    --cc=afd@ti.com \
    --cc=anshuld@ti.com \
    --cc=ayush@beagleboard.org \
    --cc=bb@ti.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=robertcnelson@gmail.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.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