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@barebox.org>
Subject: Re: [PATCH v3 1/3] resource: supply memory type/attrs on all SDRAM requests
Date: Tue, 10 Jun 2025 08:42:34 +0200	[thread overview]
Message-ID: <174953775488.2128199.841934569158419643.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250605194401.1841679-1-a.fatoum@barebox.org>


On Thu, 05 Jun 2025 21:43:59 +0200, Ahmad Fatoum wrote:
> When running as EFI loader, barebox is expected to provide a virtual
> memory map that describes the memory regions known to barebox as well as
> attributes like whether regions are write-back cached (usable as normal
> memory) or reserved (e.g., for OP-TEE).
> 
> >From a security point of view, it's useful to have this information
> always to inform MMU attributes, so let's make it mandatory.
> 
> [...]

Applied, thanks!

[1/3] resource: supply memory type/attrs on all SDRAM requests
      https://git.pengutronix.de/cgit/barebox/commit/?id=d06862bdd19d (link may not be stable)
[2/3] resource: retire IORESOURCE_BUSY in favor of resource::type
      https://git.pengutronix.de/cgit/barebox/commit/?id=191b639dd53d (link may not be stable)
[3/3] commands: iomem: add support for printing type/attributes
      https://git.pengutronix.de/cgit/barebox/commit/?id=2d3abb44cfa3 (link may not be stable)

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




      parent reply	other threads:[~2025-06-10  6:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 19:43 Ahmad Fatoum
2025-06-05 19:44 ` [PATCH v3 2/3] resource: retire IORESOURCE_BUSY in favor of resource::type Ahmad Fatoum
2025-06-05 19:44 ` [PATCH v3 3/3] commands: iomem: add support for printing type/attributes Ahmad Fatoum
2025-06-10 10:18   ` Sascha Hauer
2025-06-10  6:42 ` 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=174953775488.2128199.841934569158419643.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@barebox.org \
    --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