From: "Oliver O'Halloran" <oohall@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] powerpc/chrp: Revert "Move PHB discovery" and "Make hydra_init() static"
Date: Mon, 19 Jul 2021 02:13:54 +1000 [thread overview]
Message-ID: <CAOSf1CEN6022gv_=O9fwyDtJ7ibmXnH+LrpRQvGXTZ22RH-u1g@mail.gmail.com> (raw)
In-Reply-To: <20210717161438.GA3038659@roeck-us.net>
On Sun, Jul 18, 2021 at 2:14 AM Guenter Roeck <linux@roeck-us.net> wrote:
>
> On Sun, Jul 18, 2021 at 01:54:23AM +1000, Oliver O'Halloran wrote:
> > On Sat, Jul 17, 2021 at 8:12 AM Guenter Roeck <linux@roeck-us.net> wrote:
> > >
> > > This patch reverts commit 407d418f2fd4 ("powerpc/chrp: Move PHB
> > > discovery") and commit 9634afa67bfd ("powerpc/chrp: Make hydra_init()
> > > static").
> > >
> > > Running the upstream kernel on Qemu's brand new "pegasos2" emulation
> > > results in a variety of backtraces such as
> >
> > ...and actually using it appears to require both manually enabling it
> > in the qemu config and finding a random bios blob that is no longer
> > distributed by the manufacturer. Cool.
> >
> That is absolutely wrong. vof.bin provided by qemu in the linux root
> directory works just fine, plus chrp32_defconfig minus SMP.
It looks like I forgot to actually merge the current HEAD into my
local qemu branch which was a few weeks old. VOF support was merged on
the 13th so I didn't see it. My apologies.
Oliver
next prev parent reply other threads:[~2021-07-18 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 22:11 [PATCH] powerpc/chrp: Revert "Move PHB discovery" and "Make hydra_init() static" Guenter Roeck
2021-07-17 15:54 ` Oliver O'Halloran
2021-07-17 16:14 ` Guenter Roeck
2021-07-18 16:13 ` Oliver O'Halloran [this message]
2021-07-17 15:57 ` Christophe Leroy
2021-07-17 16:01 ` Christophe Leroy
2021-07-17 16:23 ` Guenter Roeck
2021-07-18 16:09 ` Oliver O'Halloran
2022-09-08 6:23 ` Christophe Leroy
2022-09-08 13:47 ` Guenter Roeck
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='CAOSf1CEN6022gv_=O9fwyDtJ7ibmXnH+LrpRQvGXTZ22RH-u1g@mail.gmail.com' \
--to=oohall@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).