qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: BALATON Zoltan <balaton@eik.bme.hu>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Greg Kurz <groug@kaod.org>, Laurent Vivier <laurent@vivier.eu>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 0/4] ppc/Pegasos2: Firmware replacement using VOF
Date: Mon, 5 Jul 2021 21:17:19 +0200	[thread overview]
Message-ID: <2fa5211f-593c-8939-1b34-4964a93baee4@amsat.org> (raw)
In-Reply-To: <a72a7538-e571-efae-27b-3cec1493441@eik.bme.hu>

On 7/1/21 1:35 PM, BALATON Zoltan wrote:
> On Sun, 27 Jun 2021, BALATON Zoltan wrote:
>> Based-on: <20210625055155.2252896-1-aik@ozlabs.ru>
>> ^ That is v22 of Alexey's VOF patch
>>
>> With this series on top of VOF v22 I can now boot Linux and MorphOS on
>> pegasos2 without a firmware blob so I hope this is enough to get this
>> board in 6.1 and also have it enabled so people can start using it
>> eventually (a lot of people don't compile their QEMU but rely on
>> binaries from distros and other sources). Provided that VOF will also
>> be merged by then. This gives VOF another use case that may help it
>> getting merged at last.
>>
>> Further info and example command lines can be found at
>> https://osdn.net/projects/qmiga/wiki/SubprojectPegasos2
> 
> Ping? Freeze is coming and this would be the second release pegasos2
> misses (after it missed 6.0) if this is not in the next pull request so
> that's why I'm pushing.

I'm not sure who can help, I was expecting Alexey would review
your series. Cc'ing Laurent and Greg in case, to help you...

>> BALATON Zoltan (4):
>>  ppc/pegasos2: Introduce Pegasos2MachineState structure
>>  target/ppc: Allow virtual hypervisor on CPU without HV
>>  ppc/pegasos2: Use Virtual Open Firmware as firmware replacement
>>  ppc/pegasos2: Implement some RTAS functions with VOF
>>
>> default-configs/devices/ppc-softmmu.mak |   2 +-
>> hw/ppc/Kconfig                          |   1 +
>> hw/ppc/pegasos2.c                       | 783 +++++++++++++++++++++++-
>> target/ppc/cpu.c                        |   2 +-
>> 4 files changed, 771 insertions(+), 17 deletions(-)
>>
>>
> 



  reply	other threads:[~2021-07-05 19:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 16:27 [PATCH 0/4] ppc/Pegasos2: Firmware replacement using VOF BALATON Zoltan
2021-06-27 16:27 ` [PATCH 2/4] target/ppc: Allow virtual hypervisor on CPU without HV BALATON Zoltan
2021-07-08  2:48   ` David Gibson
2021-06-27 16:27 ` [PATCH 1/4] ppc/pegasos2: Introduce Pegasos2MachineState structure BALATON Zoltan
2021-07-08  2:47   ` David Gibson
2021-06-27 16:27 ` [PATCH 4/4] ppc/pegasos2: Implement some RTAS functions with VOF BALATON Zoltan
2021-07-08  4:37   ` David Gibson
2021-07-08 22:25     ` BALATON Zoltan
2021-06-27 16:27 ` [PATCH 3/4] ppc/pegasos2: Use Virtual Open Firmware as firmware replacement BALATON Zoltan
2021-07-01 11:35 ` [PATCH 0/4] ppc/Pegasos2: Firmware replacement using VOF BALATON Zoltan
2021-07-05 19:17   ` Philippe Mathieu-Daudé [this message]
2021-07-08  4:37 ` David Gibson

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=2fa5211f-593c-8939-1b34-4964a93baee4@amsat.org \
    --to=f4bug@amsat.org \
    --cc=aik@ozlabs.ru \
    --cc=balaton@eik.bme.hu \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=laurent@vivier.eu \
    --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).