qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: BALATON Zoltan <balaton@eik.bme.hu>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v4 00/12] Pegasos2 clean up and pegasos1 emulation
Date: Thu, 23 Oct 2025 17:09:11 +0530	[thread overview]
Message-ID: <764df5c7-55d3-48ec-a28b-0c837e13c595@linux.ibm.com> (raw)
In-Reply-To: <cover.1761176219.git.balaton@eik.bme.hu>



On 10/23/25 05:36, BALATON Zoltan wrote:
> This series changes how the fdt for VOF is generated in pegasos2 by
> moving the static parts to a dtb and only generate the changing parts
> such as memory size and PCI devices programmatically. This simplifies
> the code and allows simply adding emulation of Pegasos I which has a
> different north bridge and slightly different memory map but otherwise
> very similar and can be emulated by reusing parts from the amigaone
> machine. The machine was tested with a Pegasos I ROM image and MorphOS.
> 
> The first VOF patch (submitted separetely before, the reviewed v3 is
> included here) fixes handling the name property in VOF that cannot be
> represented in a dts as that always takes the path as the name and
> cannot accept an explicit name property but we need the name property
> to appear when guest queries properties which previously was worked
> around by adding it to every node.
> 
> Regards,
> BALATON Zoltan

Queued.


  parent reply	other threads:[~2025-10-23 11:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  0:06 [PATCH v4 00/12] Pegasos2 clean up and pegasos1 emulation BALATON Zoltan
2025-10-23  0:06 ` [PATCH v4 01/12] ppc/vof: Make nextprop behave more like Open Firmware BALATON Zoltan
2025-10-23  0:06 ` [PATCH v4 02/12] hw/ppc/pegasos2: Remove explicit name properties from device tree BALATON Zoltan
2025-10-23  4:55   ` Harsh Prateek Bora
2025-10-23  0:06 ` [PATCH v4 03/12] hw/ppc/pegasos2: Change device tree generation BALATON Zoltan
2025-10-23  0:06 ` [PATCH v4 04/12] hw/ppc/pegasos2: Remove fdt pointer from machine state BALATON Zoltan
2025-10-23  0:06 ` [PATCH v4 05/12] hw/ppc/pegasos2: Rename mv field in " BALATON Zoltan
2025-10-23  0:06 ` [PATCH v4 06/12] hw/ppc/pegasos2: Add south bridge pointer in the " BALATON Zoltan
2025-10-23  0:06 ` [PATCH v4 07/12] hw/ppc/pegasos2: Move PCI IRQ routing setup to a function BALATON Zoltan
2025-10-23  6:47   ` Philippe Mathieu-Daudé
2025-10-23  0:06 ` [PATCH v4 08/12] hw/ppc/pegasos2: Move hardware specific parts out of machine reset BALATON Zoltan
2025-10-23  6:46   ` Philippe Mathieu-Daudé
2025-10-23  8:45     ` Harsh Prateek Bora
2025-10-23 11:41       ` BALATON Zoltan
2025-10-23 12:58     ` BALATON Zoltan
2025-10-23  0:06 ` [PATCH v4 09/12] hw/ppc/pegasos2: Introduce abstract superclass BALATON Zoltan
2025-10-23  0:06 ` [PATCH v4 10/12] hw/ppc/pegasos2: Add bus frequency to machine state BALATON Zoltan
2025-10-23  6:36   ` Philippe Mathieu-Daudé
2025-10-23 11:05     ` BALATON Zoltan
2025-10-23  0:06 ` [PATCH v4 11/12] hw/ppc/pegasos2: Add Pegasos I emulation BALATON Zoltan
2025-10-23  6:54   ` Philippe Mathieu-Daudé
2025-10-23 13:14     ` BALATON Zoltan
2025-10-23  0:06 ` [PATCH v4 12/12] hw/ppc/pegasos2: Add VOF support for pegasos1 BALATON Zoltan
2025-10-23  6:49   ` Philippe Mathieu-Daudé
2025-10-23 11:39 ` Harsh Prateek Bora [this message]
2025-10-23 12:07   ` [PATCH v4 00/12] Pegasos2 clean up and pegasos1 emulation BALATON Zoltan
2025-10-23 12:15     ` BALATON Zoltan
2025-10-23 12:23       ` Harsh Prateek Bora
2025-10-23 12:29         ` 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=764df5c7-55d3-48ec-a28b-0c837e13c595@linux.ibm.com \
    --to=harshpb@linux.ibm.com \
    --cc=armbru@redhat.com \
    --cc=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).