mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 0/6] resource: add support for walking resource gaps
Date: Mon, 15 Dec 2025 10:29:09 +0100	[thread overview]
Message-ID: <176579094990.283490.13216135233850821199.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20251211205240.2836186-1-a.fatoum@pengutronix.de>


On Thu, 11 Dec 2025 21:50:02 +0100, Ahmad Fatoum wrote:
> We currently keep track of regions with the SDRAM by requesting a struct
> resource from the memory bank. We will make additional use of that to
> request memory handed out to EFI applications when barebox is being used
> as EFI loader.
> 
> For that purpose, we need an easy way to walk the requested memory
> region and especially the gaps between them as well as support for
> freeing partial regions.
> 
> [...]

Applied, thanks!

[1/6] resource: implement resource walker
      https://git.pengutronix.de/cgit/barebox/commit/?id=f28805f5ffac (link may not be stable)
[2/6] test: self: implement resource walker selftest
      https://git.pengutronix.de/cgit/barebox/commit/?id=9e5e0f7b7933 (link may not be stable)
[3/6] commands: iomem: add support for printing gaps
      https://git.pengutronix.de/cgit/barebox/commit/?id=2585a9ab6a1c (link may not be stable)
[4/6] test: py: add test for valid JSON output from iomem/clk_dump
      https://git.pengutronix.de/cgit/barebox/commit/?id=d93bb7e619be (link may not be stable)
[5/6] memory: add helpers for iterating over memory regions
      https://git.pengutronix.de/cgit/barebox/commit/?id=7bdc0bf05142 (link may not be stable)
[6/6] resource: implement release_region_range
      https://git.pengutronix.de/cgit/barebox/commit/?id=804c79319dcd (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2025-12-15  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 20:50 Ahmad Fatoum
2025-12-11 20:50 ` [PATCH 1/6] resource: implement resource walker Ahmad Fatoum
2025-12-11 20:50 ` [PATCH 2/6] test: self: implement resource walker selftest Ahmad Fatoum
2025-12-11 20:50 ` [PATCH 3/6] commands: iomem: add support for printing gaps Ahmad Fatoum
2025-12-11 20:50 ` [PATCH 4/6] test: py: add test for valid JSON output from iomem/clk_dump Ahmad Fatoum
2025-12-11 20:50 ` [PATCH 5/6] memory: add helpers for iterating over memory regions Ahmad Fatoum
2025-12-11 20:50 ` [PATCH 6/6] resource: implement release_region_range Ahmad Fatoum
2025-12-15  9:29 ` Sascha Hauer [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=176579094990.283490.13216135233850821199.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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