All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH qemu v23] spapr: Fix implementation of Open Firmware client interface
Date: Fri, 9 Jul 2021 23:46:46 +1000	[thread overview]
Message-ID: <f8b149b7-366d-f5cd-7820-7e5ceab0157d@ozlabs.ru> (raw)
In-Reply-To: <433d7bea-60be-2962-4974-ba74ea4fe84@eik.bme.hu>



On 09/07/2021 23:28, BALATON Zoltan wrote:
> On Fri, 9 Jul 2021, Alexey Kardashevskiy wrote:
>> On 09/07/2021 08:34, BALATON Zoltan wrote:
>>> MorphOS still boots but this breaks Linux which changes a few things 
>>> in the device tree to fix it up to make it look the way it thinks is 
>>> better.
>>
>>
>> What are those things? What does the change break precisely? Does the 
>> kernel stop booting?
>> Can you please send output with the trace_vof_setprop tracepoint enabled?
> 
> It's fixing up some props that on Pegasos2 firmware are not how Linux 
> expects them.

Why does it need to fix them then? You are building the FDT in QEMU, 
built it in the way Linux like and then you do not depend on the kernel 
fixing them up. What do I miss?

 From traces I see that (besides PCI) it mostly sets props for 
linux-initrd/bootargs which you rather need to handle to keep the 
machine's properties and the FDT in sync.


> Without this it's not booting. Attached is the trace 
> output with VOF v23 as it is now (nosetprop) and another one after the 
> patch that adds setprop callback to pegasos2 I'm sending separately. 
> That patch restores Linux boot but I still think all this boilerplate 
> would not be needed if we kept the default to allow setprop and that 
> results in overall simpler code. If something breaks becuase of enabling 
> setprop by default (which normally works on real Open Firmware) it's 
> easy enough to debug by enabling vof_setprop trace points so I don't see 
> this adds any value other than making board code more complex.



-- 
Alexey


  reply	other threads:[~2021-07-09 13:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  6:56 [PATCH qemu v23] spapr: Fix implementation of Open Firmware client interface Alexey Kardashevskiy
2021-07-08 10:18 ` BALATON Zoltan
2021-07-08 10:25   ` Alexey Kardashevskiy
2021-07-08 10:39     ` BALATON Zoltan
2021-07-08 11:10       ` Alexey Kardashevskiy
2021-07-08 13:00         ` BALATON Zoltan
2021-07-09  0:54           ` David Gibson
2021-07-09 13:34             ` BALATON Zoltan
2021-07-08 22:34 ` BALATON Zoltan
2021-07-09  3:43   ` Alexey Kardashevskiy
2021-07-09 13:28     ` BALATON Zoltan
2021-07-09 13:46       ` Alexey Kardashevskiy [this message]
2021-07-09 15:35         ` BALATON Zoltan
2021-07-09  0:52 ` 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=f8b149b7-366d-f5cd-7820-7e5ceab0157d@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=balaton@eik.bme.hu \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.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.