From: BALATON Zoltan <balaton@eik.bme.hu>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
Edgar E. Iglesias <edgar.iglesias@gmail.com>
Subject: [PATCH 0/2] Consolidate embedded PPC initial mappung functions
Date: Tue, 16 Jul 2024 14:07:56 +0200 (CEST) [thread overview]
Message-ID: <cover.1721131193.git.balaton@eik.bme.hu> (raw)
Embedded PPC has always enabled MMU so it needs initial mappings to
start. This code is duplicated within machines which this small series
aims to consolidate into helper functions to reduce duplicated code
and make the board code simpler.
Regards,
BALATON Zoltan
BALATON Zoltan (2):
hw/ppc: Consolidate e500 initial mapping creation functions
hw/ppc: Consolidate ppc440 initial mapping creation functions
hw/ppc/e500.c | 41 ++++++++++++++++++--------------------
hw/ppc/e500.h | 2 --
hw/ppc/ppc440_bamboo.c | 28 +++-----------------------
hw/ppc/ppc_booke.c | 10 ++++++++++
hw/ppc/ppce500_spin.c | 30 +++++++++-------------------
hw/ppc/sam460ex.c | 45 ++++++++++--------------------------------
hw/ppc/virtex_ml507.c | 28 +++-----------------------
include/hw/ppc/ppc.h | 7 +++++++
8 files changed, 61 insertions(+), 130 deletions(-)
--
2.30.9
next reply other threads:[~2024-07-16 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 12:07 BALATON Zoltan [this message]
2024-07-16 12:07 ` [PATCH 1/2] hw/ppc: Consolidate e500 initial mapping creation functions BALATON Zoltan
2024-08-15 19:01 ` Bernhard Beschow
2024-10-01 19:31 ` Bernhard Beschow
2024-10-01 23:35 ` BALATON Zoltan
2024-10-06 18:46 ` BALATON Zoltan
2024-07-16 12:07 ` [PATCH 2/2] hw/ppc: Consolidate ppc440 " BALATON Zoltan
2024-07-16 17:07 ` [PATCH 0/2] Consolidate embedded PPC initial mappung functions Edgar E. Iglesias
2024-10-08 13:32 ` BALATON Zoltan
2024-11-02 12:20 ` BALATON Zoltan
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=cover.1721131193.git.balaton@eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=danielhb413@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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;
as well as URLs for NNTP newsgroup(s).