public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andrew Davis <afd@ti.com>
To: Neha Malcom Francis <n-francis@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
	Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
	Apurva Nandan <a-nandan@ti.com>
Cc: <u-boot@lists.denx.de>, Andrew Davis <afd@ti.com>
Subject: [PATCH RFC 0/2] Unify K3 initial memory map
Date: Wed, 22 Nov 2023 09:14:09 -0600	[thread overview]
Message-ID: <20231122151411.11268-1-afd@ti.com> (raw)

Hello all,

This is just an RFC as it probably breaks remoteproc loading.
I wanted to post anyway as the complexity of having a dedicated
memory map for each SoC came up in a different series.

Or maybe we can take this now and that will expose the issue in
remoteproc loading better and force someone to go fix it. :)

This series depends on this[0].

Thanks,
Andrew

[0] https://patchwork.ozlabs.org/project/uboot/patch/20231106165205.22066-1-afd@ti.com/

Andrew Davis (2):
  arm: mach-k3: Remove non-cached memory map areas
  arm: mach-k3: Merge initial memory maps

 arch/arm/mach-k3/arm64-mmu.c | 253 +----------------------------------
 1 file changed, 2 insertions(+), 251 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-11-22 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 15:14 Andrew Davis [this message]
2023-11-22 15:14 ` [PATCH RFC 1/2] arm: mach-k3: Remove non-cached memory map areas Andrew Davis
2023-11-22 15:14 ` [PATCH RFC 2/2] arm: mach-k3: Merge initial memory maps Andrew Davis
2023-11-23 16:29 ` [PATCH RFC 0/2] Unify K3 initial memory map Nishanth Menon

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=20231122151411.11268-1-afd@ti.com \
    --to=afd@ti.com \
    --cc=a-nandan@ti.com \
    --cc=n-francis@ti.com \
    --cc=nm@ti.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.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