From: "Cédric Le Goater" <clg@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Joel Stanley <joel@jms.id.au>,
qemu-ppc@nongnu.org, Greg Kurz <groug@kaod.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ppc/pnv: Generate phandle for the "interrupt-parent" property
Date: Wed, 24 Jul 2019 09:11:54 +0200 [thread overview]
Message-ID: <0b80925b-c25b-04ee-2875-cbd155497a55@kaod.org> (raw)
In-Reply-To: <20190724032308.GV25073@umbus.fritz.box>
On 24/07/2019 05:23, David Gibson wrote:
> On Tue, Jul 23, 2019 at 11:01:38AM +0200, Cédric Le Goater wrote:
>> Devices such as the BT or serial devices require a valid
>> "interrupt-parent" phandle in the device tree and it is currently
>> empty (0x0). It was not a problem until now but since OpenFirmare
>> started using a recent libdft (>= 1.4.7), petitboot fails to boot the
>> system image with error :
>>
>> dtc_resize: fdt_open_into returned FDT_ERR_BADMAGIC
>>
>> Provide a phandle for the LPC bus.
>>
>> Suggested-by: Greg Kurz <groug@kaod.org>
>> Signed-off-by: Cédric Le Goater <clg@kaod.org>
>
> I've applied this, since it looks to be correct.
>
> But.. can you connect the dots for me in how this being missing
> results in a BADMAGIC error??
Some binary called by petitboot segfaults when trying to kexec an image on
a system with a bogus DT (generated by QEMU). I don't know exactly which one
as I only see the error message above and the segv message in dmesg
I didn't notice before because I was using an old open-power-v2.1 image. I have
switched to more recent ones now :
https://openpower.xyz/job/openpower/job/openpower-op-build/label=slave,target=witherspoon/lastSuccessfulBuild/
https://openpower.xyz/job/openpower/job/openpower-op-build/label=slave,target=palmetto/lastSuccessfulBuild/
Btw, where could we keep some images of reference ? I have a couple of patches
which enables the QEMU PowerNV machine to boot directly from the PNOR using :
-drive file=./witherspoon.pnor,format=raw,if=mtd
Thanks,
C.
>
>> ---
>> hw/ppc/pnv.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
>> index 36f57479a1f5..2deceecdccb5 100644
>> --- a/hw/ppc/pnv.c
>> +++ b/hw/ppc/pnv.c
>> @@ -431,9 +431,14 @@ static void pnv_dt_isa(PnvMachineState *pnv, void *fdt)
>> .fdt = fdt,
>> .offset = isa_offset,
>> };
>> + uint32_t phandle;
>>
>> _FDT((fdt_setprop(fdt, isa_offset, "primary", NULL, 0)));
>>
>> + phandle = qemu_fdt_alloc_phandle(fdt);
>> + assert(phandle > 0);
>> + _FDT((fdt_setprop_cell(fdt, isa_offset, "phandle", phandle)));
>> +
>> /* ISA devices are not necessarily parented to the ISA bus so we
>> * can not use object_child_foreach() */
>> qbus_walk_children(BUS(pnv->isa_bus), pnv_dt_isa_device, NULL, NULL, NULL,
>
next prev parent reply other threads:[~2019-07-24 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 9:01 [Qemu-devel] [PATCH] ppc/pnv: Generate phandle for the "interrupt-parent" property Cédric Le Goater
2019-07-24 3:23 ` David Gibson
2019-07-24 7:11 ` Cédric Le Goater [this message]
2019-07-24 8:57 ` David Gibson
2019-07-24 9:27 ` Cédric Le Goater
2019-07-24 14:55 ` [Qemu-devel] [Qemu-ppc] " Amol Surati
2019-07-25 3:26 ` 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=0b80925b-c25b-04ee-2875-cbd155497a55@kaod.org \
--to=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=joel@jms.id.au \
--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).