From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>
Subject: [PULL 0/2] ppc-for-8.2 queue
Date: Thu, 30 Nov 2023 22:41:09 +1000 [thread overview]
Message-ID: <20231130124111.109602-1-npiggin@gmail.com> (raw)
The following changes since commit abf635ddfe3242df907f58967f3c1e6763bbca2d:
Update version for v8.2.0-rc2 release (2023-11-28 16:31:16 -0500)
are available in the Git repository at:
https://gitlab.com/npiggin/qemu.git tags/pull-ppc-for-8.2-20231130
for you to fetch changes up to e25acd619135c752672de323f22aba8c1d00584e:
ppc/amigaone: Allow running AmigaOS without firmware image (2023-11-30 22:13:00 +1000)
----------------------------------------------------------------
* Add a default BIOS for the new amigaone machine so it does not
require out of tree binary blob.
* SLOF update to fix virtio serial bugs.
----------------------------------------------------------------
Alexey Kardashevskiy (1):
pseries: Update SLOF firmware image
BALATON Zoltan (1):
ppc/amigaone: Allow running AmigaOS without firmware image
hw/ppc/amigaone.c | 35 +++++++++++++++++++++++------------
pc-bios/README | 2 +-
pc-bios/slof.bin | Bin 995176 -> 995000 bytes
roms/SLOF | 2 +-
4 files changed, 25 insertions(+), 14 deletions(-)
next reply other threads:[~2023-11-30 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 12:41 Nicholas Piggin [this message]
2023-11-30 12:41 ` [PULL 1/2] pseries: Update SLOF firmware image Nicholas Piggin
2023-11-30 12:41 ` [PULL 2/2] ppc/amigaone: Allow running AmigaOS without " Nicholas Piggin
2023-11-30 13:16 ` BALATON Zoltan
2023-11-30 13:20 ` BALATON Zoltan
2023-12-01 19:58 ` [PULL 0/2] ppc-for-8.2 queue Stefan Hajnoczi
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=20231130124111.109602-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=clg@kaod.org \
--cc=danielhb413@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).