All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	Peter Maydell <peter.maydell@linaro.org>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Andrew Phelps <andrew.phelps@canonical.com>,
	Alexander Graf <agraf@csgraf.de>, Bin Meng <bmeng.cn@gmail.com>,
	Caleb Connolly <caleb.connolly@linaro.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Jerry Van Baren <vanbaren@cideas.com>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Lukas Funke <lukas.funke@weidmueller.com>,
	Marek Vasut <marek.vasut+renesas@mailbox.org>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Michal Simek <michal.simek@amd.com>,
	Oliver Gaskell <Oliver.Gaskell@analog.com>,
	Patrick Rudolph <patrick.rudolph@9elements.com>,
	Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
	Robert Marko <robert.marko@sartura.hr>,
	Sumit Garg <sumit.garg@linaro.org>,
	This contributor prefers not to receive mails
	<noreply@example.com>, Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
Subject: Re: [PATCH v2] emulation: fdt: Allow using U-Boot's device tree with QEMU
Date: Mon, 14 Apr 2025 16:53:07 -0600	[thread overview]
Message-ID: <20250414225307.GH5495@bill-the-cat> (raw)
In-Reply-To: <20250405190711.365419-1-sjg@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]

On Sun, Apr 06, 2025 at 07:07:04AM +1200, Simon Glass wrote:

> At present it is impossible to change the qemu_arm64 defconfig to
> obtain a devicetree from the U-Boot build.
> 
> This is necessary for FIT validation, for example, where the signature
> node must be compiled into U-Boot.
> 
> A proposed change to QEMU to allow device tree additions has been
> blocked for several years. The only known workaround is to use QEMU's
> dumpdtb option, merge in the signature node manually, disable
> OF_HAS_PRIOR_STAGE and then start QEMU with special arguments. This is
> complicated enough that it is documented in U-Boot[1].

This paragraph and then

[snip]
> +	  Note: this work-around is necessary since Linaro has blocked
> +	  addition of a feature to support additions to the QEMU devicetree:

This part of the help are overly antagonistic.

[snip]
> diff --git a/dts/Kconfig b/dts/Kconfig
> index 2e88d210bb8..53f7e246a80 100644
> --- a/dts/Kconfig
> +++ b/dts/Kconfig
> @@ -205,8 +205,13 @@ config OF_HAS_PRIOR_STAGE
>  	  development purposes, but it is not recommended, and likely will not
>  	  even work, for production systems.
>  
> -	  Note: This option must be set in Kconfig and cannot be enabled or
> -	  disabled in the board's defconfig file.
> +	  Note: This option can be disabled for QEMU usiing QEMU_MANUAL_DTB thus
> +	  allowing QEMU to support FIT validation, where the devicetree must
> +	  include a public key.
> +
> +	  See also this for context:
> +
> +	  https://patchwork.kernel.org/project/qemu-devel/patch/20210926183410.256484-1-sjg@chromium.org/#24481799

And we don't need more wording here. The QEMU_MANUAL_DTB option itself
is enough.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2025-04-14 22:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-05 19:07 [PATCH v2] emulation: fdt: Allow using U-Boot's device tree with QEMU Simon Glass
2025-04-14 22:53 ` Tom Rini [this message]
2025-04-15  7:22   ` Ilias Apalodimas
2025-04-15 14:12     ` Tom Rini
2025-04-15 18:45       ` Ilias Apalodimas
2025-04-17 21:39   ` Simon Glass
2025-04-17 22:04     ` Tom Rini
2025-04-16  5:33 ` Heinrich Schuchardt
2025-04-16 13:50   ` Tom Rini
2025-04-17 21:35   ` Simon Glass

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=20250414225307.GH5495@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=Oliver.Gaskell@analog.com \
    --cc=agraf@csgraf.de \
    --cc=andrew.phelps@canonical.com \
    --cc=bmeng.cn@gmail.com \
    --cc=caleb.connolly@linaro.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=lukas.funke@weidmueller.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=michal.simek@amd.com \
    --cc=noreply@example.com \
    --cc=patrick.rudolph@9elements.com \
    --cc=peter.maydell@linaro.org \
    --cc=rayagonda.kokatanur@broadcom.com \
    --cc=robert.marko@sartura.hr \
    --cc=sjg@chromium.org \
    --cc=sumit.garg@linaro.org \
    --cc=tuomas.tynkkynen@iki.fi \
    --cc=u-boot@lists.denx.de \
    --cc=vanbaren@cideas.com \
    /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.