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>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH 1/4] hw/ppc/pegasos2: Add /chosen/stdin node with VOF
Date: Thu, 30 Oct 2025 13:36:08 +0530	[thread overview]
Message-ID: <31effff7-cdff-4ddb-a772-3849941af587@linux.ibm.com> (raw)
In-Reply-To: <642ef77674d08ba466e7a2beb4858ab1e67776ae.1761346145.git.balaton@eik.bme.hu>



On 10/25/25 05:01, BALATON Zoltan wrote:
> Some very old Linux kernels fail to start if /chosen/stdin is not
> found so add it to the device tree when using VOF.
> 
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> ---
>   hw/ppc/pegasos2.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/hw/ppc/pegasos2.c b/hw/ppc/pegasos2.c
> index 93696ed381..21299dde3c 100644
> --- a/hw/ppc/pegasos2.c
> +++ b/hw/ppc/pegasos2.c
> @@ -565,6 +565,7 @@ static void pegasos_machine_reset(MachineState *machine, ResetType type)
>       qemu_fdt_setprop(fdt, "/chosen", "qemu,boot-kernel", d, sizeof(d));
>   
>       vof_build_dt(fdt, pm->vof);
> +    vof_client_open_store(fdt, pm->vof, "/chosen", "stdin", "/failsafe");

Reviewed-by: Harsh Prateek Bora <harshpb@linux.ibm.com>

>       vof_client_open_store(fdt, pm->vof, "/chosen", "stdout", "/failsafe");
>   
>       /* Set machine->fdt for 'dumpdtb' QMP/HMP command */


  reply	other threads:[~2025-10-30  8:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24 23:31 [PATCH 0/4] Some more pegasos patches BALATON Zoltan
2025-10-24 23:31 ` [PATCH 1/4] hw/ppc/pegasos2: Add /chosen/stdin node with VOF BALATON Zoltan
2025-10-30  8:06   ` Harsh Prateek Bora [this message]
2025-10-24 23:31 ` [PATCH 2/4] hw/pci-host/articia: Map PCI memory windows in realize BALATON Zoltan
2025-10-27 19:35   ` Philippe Mathieu-Daudé
2025-10-27 19:47     ` BALATON Zoltan
2025-10-28  5:01       ` Philippe Mathieu-Daudé
2025-10-28 12:59         ` BALATON Zoltan
2025-10-28 16:33           ` Akihiko Odaki
2025-10-28 21:28             ` BALATON Zoltan
2025-10-29  4:23               ` Akihiko Odaki
2025-10-29 10:30                 ` BALATON Zoltan
2025-10-29 13:25                   ` BALATON Zoltan
2025-10-30  0:36                     ` Mark Cave-Ayland
2025-10-30 10:29                       ` BALATON Zoltan
2025-10-29 19:20                   ` Peter Xu
2025-10-30 10:25                     ` Paolo Bonzini
2025-10-30 10:38                       ` BALATON Zoltan
2025-10-30 10:49                         ` Paolo Bonzini
2025-10-30 11:01                           ` BALATON Zoltan
2025-10-30 12:29                             ` Paolo Bonzini
2025-10-30 12:45                               ` BALATON Zoltan
2025-10-30 10:53                       ` BALATON Zoltan
2025-10-28 23:57     ` BALATON Zoltan
2025-10-24 23:31 ` [PATCH 3/4] hw/ppc/pegasos2: Rename to pegasos BALATON Zoltan
2025-10-27 19:36   ` Philippe Mathieu-Daudé
2025-10-24 23:31 ` [PATCH 4/4] hw/ppc/pegasos: Update documentation for pegasos1 BALATON Zoltan
2025-10-27 19:37   ` Philippe Mathieu-Daudé

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=31effff7-cdff-4ddb-a772-3849941af587@linux.ibm.com \
    --to=harshpb@linux.ibm.com \
    --cc=balaton@eik.bme.hu \
    --cc=npiggin@gmail.com \
    --cc=philmd@linaro.org \
    --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).