From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: BALATON Zoltan <balaton@eik.bme.hu>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH 0/3] pegasos2 fixes for 8.1
Date: Fri, 21 Jul 2023 17:37:54 -0300 [thread overview]
Message-ID: <e3eee7ac-a6f8-4643-4600-845d6718e1d4@gmail.com> (raw)
In-Reply-To: <cover.1689725688.git.balaton@eik.bme.hu>
On 7/18/23 21:32, BALATON Zoltan wrote:
> These are some small fixes when using pegasos2 with the QEMU built in
> VOF instead of the non-free board firmware that fix bugs in the
> generated device tree and matches the board firmware in the reset
> state of on-board USB devices. This fixes booting AmigaOS with VOF and
> only touches parts that are used with VOF only so I'd like these to be
> merged for 8.1.
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
And pushed to ppc-next. Thanks,
Daniel
>
> Regards,
>
> BALATON Zoltan (3):
> ppc/pegasos2: Fix reset state of USB functions
> ppc/pegasos2: Fix reg property of ROM BARs
> ppc/pegasos2: Fix naming of device tree nodes
>
> hw/ppc/pegasos2.c | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
next prev parent reply other threads:[~2023-07-21 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 0:32 [PATCH 0/3] pegasos2 fixes for 8.1 BALATON Zoltan
2023-07-19 0:32 ` [PATCH 1/3] ppc/pegasos2: Fix reset state of USB functions BALATON Zoltan
2023-07-19 0:32 ` [PATCH 2/3] ppc/pegasos2: Fix reg property of ROM BARs BALATON Zoltan
2023-07-19 0:32 ` [PATCH 3/3] ppc/pegasos2: Fix naming of device tree nodes BALATON Zoltan
2023-07-21 20:37 ` Daniel Henrique Barboza [this message]
2023-07-21 22:17 ` [PATCH 0/3] pegasos2 fixes for 8.1 BALATON Zoltan
2023-07-22 18:11 ` Daniel Henrique Barboza
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=e3eee7ac-a6f8-4643-4600-845d6718e1d4@gmail.com \
--to=danielhb413@gmail.com \
--cc=balaton@eik.bme.hu \
--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).