qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH v2 0/5] ppc/amigaone patches
Date: Thu, 27 Feb 2025 17:39:14 +0100 (CET)	[thread overview]
Message-ID: <cover.1740673173.git.balaton@eik.bme.hu> (raw)

Hello,

v2:
- change unused read function to g_assert_not_reached()
- new patch to add defines to constants
- added R-b tags

This series adds NVRAM and support for -kernel, -initrd and -append
options to the amigaone machine. This makes it easier to boot AmigaOS
and avoids a crash in the guest when it tries to access NVRAM.

While the -kernel option emulates what U-Boot passes to the kernel,
old Linux kernels for amigaone may not work with it because of two
reasons: these come in legacy U-Boot Multi-File image format that QEMU
cannot read and even after unpacking that and creating a kernel uimage
it won't find PCI devices because it does not initialise them
correctly. This works when booted from U-Boot because U-Boot inits PCI
devices. So does my BBoot loader which can be used to load AmigaOS so
I don't intend to emulate that part of U-Boot.

I'd like this to be merged for the next release please. When merging
please update https://wiki.qemu.org/ChangeLog/10.0 with the following:

amigaone

Added support for NVRAM and -kernel, -initrd, -append command line
options. By default the NVRAM contents are not preserved between
sessions. To make it persistent create a backing file with 'qemu-image
create -f raw nvram.bin 4k' and add -drive
if=mtd,format=raw,file=nvram.bin to keep NVRAM contents in the backing
file so settings stored in it will be preserved between sessions.

To run AmigaOS with BBoot using the -kernel option at least BBoot
version 0.8 is needed. Older BBoot versions only work with -device
loader and cannot be used with -kernel on amigaone.

Regards,

BALATON Zoltan (5):
  ppc/amigaone: Simplify replacement dummy_fw
  ppc/amigaone: Implement NVRAM emulation
  ppc/amigaone: Add default environment
  ppc/amigaone: Add kernel and initrd support
  ppc/amigaone: Add #defines for memory map constants

 hw/ppc/amigaone.c | 284 +++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 271 insertions(+), 13 deletions(-)

-- 
2.30.9



             reply	other threads:[~2025-02-27 16:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 16:39 BALATON Zoltan [this message]
2025-02-27 16:39 ` [PATCH v2 1/5] ppc/amigaone: Simplify replacement dummy_fw BALATON Zoltan
2025-02-27 16:39 ` [PATCH v2 2/5] ppc/amigaone: Implement NVRAM emulation BALATON Zoltan
2025-02-27 16:39 ` [PATCH v2 3/5] ppc/amigaone: Add default environment BALATON Zoltan
2025-03-07 14:10   ` Philippe Mathieu-Daudé
2025-03-07 14:46     ` BALATON Zoltan
2025-03-07 15:22       ` Philippe Mathieu-Daudé
2025-03-07 15:36         ` BALATON Zoltan
2025-02-27 16:39 ` [PATCH v2 4/5] ppc/amigaone: Add kernel and initrd support BALATON Zoltan
2025-02-27 16:39 ` [PATCH v2 5/5] ppc/amigaone: Add #defines for memory map constants BALATON Zoltan
2025-03-07 14:11   ` Philippe Mathieu-Daudé
2025-03-07 13:09 ` [PATCH v2 0/5] ppc/amigaone patches BALATON Zoltan
2025-03-11  7:36 ` Nicholas Piggin

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.1740673173.git.balaton@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --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).