From: BALATON Zoltan <balaton@eik.bme.hu>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/6] Misc pegasos2 patches
Date: Thu, 14 Oct 2021 21:50:19 +0200 [thread overview]
Message-ID: <cover.1634241019.git.balaton@eik.bme.hu> (raw)
Some small clean ups and improvements for the pegasos2 machine.
BALATON Zoltan (6):
ppc/pegasos2: Restrict memory to 2 gigabytes
ppc/pegasos2: Warn when using VOF but no kernel is specified
ppc/pegasos2: Implement get-time-of-day RTAS function with VOF
ppc/pegasos2: Access MV64361 registers via their memory region
ppc/pegasos2: Add constants for PCI config addresses
ppc/pegasos2: Implement power-off RTAS function with VOF
hw/pci-host/mv64361.c | 1 +
hw/ppc/pegasos2.c | 162 ++++++++++++++++++++++++++----------------
2 files changed, 101 insertions(+), 62 deletions(-)
--
2.21.4
next reply other threads:[~2021-10-14 20:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 19:50 BALATON Zoltan [this message]
2021-10-14 19:50 ` [PATCH 4/6] ppc/pegasos2: Access MV64361 registers via their memory region BALATON Zoltan
2021-10-15 3:18 ` David Gibson
2021-10-14 19:50 ` [PATCH 3/6] ppc/pegasos2: Implement get-time-of-day RTAS function with VOF BALATON Zoltan
2021-10-15 3:17 ` David Gibson
2021-10-15 9:26 ` BALATON Zoltan
2021-10-15 21:51 ` BALATON Zoltan
2021-10-14 19:50 ` [PATCH 5/6] ppc/pegasos2: Add constants for PCI config addresses BALATON Zoltan
2021-10-15 3:19 ` David Gibson
2021-10-14 19:50 ` [PATCH 6/6] ppc/pegasos2: Implement power-off RTAS function with VOF BALATON Zoltan
2021-10-15 3:19 ` David Gibson
2021-10-14 19:50 ` [PATCH 2/6] ppc/pegasos2: Warn when using VOF but no kernel is specified BALATON Zoltan
2021-10-15 3:15 ` David Gibson
2021-10-14 19:50 ` [PATCH 1/6] ppc/pegasos2: Restrict memory to 2 gigabytes BALATON Zoltan
2021-10-15 3:15 ` David Gibson
2021-10-15 3:20 ` [PATCH 0/6] Misc pegasos2 patches David Gibson
2021-10-15 9:28 ` 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.1634241019.git.balaton@eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=david@gibson.dropbear.id.au \
--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).