From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Cédric Le Goater" <clg@kaod.org>, "BALATON Zoltan" <balaton@eik.bme.hu>
Cc: <qemu-devel@nongnu.org>, <qemu-ppc@nongnu.org>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
<philmd@linaro.org>
Subject: Re: [PATCH v2 for-8.2] ppc/amigaone: Allow running AmigaOS without firmware image
Date: Tue, 28 Nov 2023 11:47:45 +1000 [thread overview]
Message-ID: <CXA2ENP9VBT1.2THPXM7WFD3I3@wheely> (raw)
In-Reply-To: <3f188a09-9927-4fc3-a4eb-0cde34934539@kaod.org>
On Tue Nov 28, 2023 at 2:37 AM AEST, Cédric Le Goater wrote:
>
> > I'm not sure, I don't think it's necessary if your minimal patch works.
> >
> > I'll do a PR for 8.2 for SLOF and Skiboot updates, so happy to include
> > this as well.
>
> I think this is a bit late for 8.2 to change FW images, well, at least
> SLOF and skiboot. Are the new versions fixing something critical ?
Ah okay. Well then I can put them in next instead.
SLOF has a fix for virtio console over reboots, pretty minimal.
skiboot has some bug fixes but it's a bigger change and maybe not
so important for QEMU.
Could they be merged in next release and SLOF tagged with stable?
I think this amigaone patch could still be merged since it's only
touching a new machine and it's fixing an issue of missing firmware.
Thanks,
Nick
next prev parent reply other threads:[~2023-11-28 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 16:34 [PATCH v2 for-8.2] ppc/amigaone: Allow running AmigaOS without firmware image BALATON Zoltan
2023-11-27 7:13 ` Nicholas Piggin
2023-11-27 11:43 ` BALATON Zoltan
2023-11-27 12:50 ` Nicholas Piggin
2023-11-27 13:49 ` BALATON Zoltan
2023-11-27 16:37 ` Cédric Le Goater
2023-11-28 1:47 ` Nicholas Piggin [this message]
2023-11-28 7:07 ` Cédric Le Goater
2023-11-28 9:16 ` Philippe Mathieu-Daudé
2023-11-28 12:40 ` 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=CXA2ENP9VBT1.2THPXM7WFD3I3@wheely \
--to=npiggin@gmail.com \
--cc=balaton@eik.bme.hu \
--cc=clg@kaod.org \
--cc=danielhb413@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.