From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: "U-Boot Mailing List" <u-boot@lists.denx.de>,
"François Ozog" <francois.ozog@linaro.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Albert Aribaud" <albert.u.boot@aribaud.net>
Subject: Re: [PATCH 02/16] arm: qemu: Explain how to extract the generate devicetree
Date: Wed, 13 Oct 2021 13:36:12 -0400 [thread overview]
Message-ID: <20211013173612.GX7964@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ1g4j4YdcgWKfJU81xC8NViA2Wew62Ygp0VO2QbrT6zhQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
On Wed, Oct 13, 2021 at 10:58:31AM -0600, Simon Glass wrote:
> Hi François,
>
> On Tue, 12 Oct 2021 at 19:20, François Ozog <francois.ozog@linaro.org> wrote:
> >
> >
> >
> > Le mer. 13 oct. 2021 à 03:02, Simon Glass <sjg@chromium.org> a écrit :
> >>
> >> QEMU currently generates a devicetree for use with U-Boot. Explain how to
> >> obtain it.
> >>
> >> Signed-off-by: Simon Glass <sjg@chromium.org>
> >> ---
> >>
> >> doc/board/emulation/qemu-arm.rst | 12 ++++++++++++
> >> 1 file changed, 12 insertions(+)
> >>
> >> diff --git a/doc/board/emulation/qemu-arm.rst b/doc/board/emulation/qemu-arm.rst
> >> index 97b6ec64905..b458a398c69 100644
> >> --- a/doc/board/emulation/qemu-arm.rst
> >> +++ b/doc/board/emulation/qemu-arm.rst
> >> @@ -91,3 +91,15 @@ The debug UART on the ARM virt board uses these settings::
> >> CONFIG_DEBUG_UART_PL010=y
> >> CONFIG_DEBUG_UART_BASE=0x9000000
> >> CONFIG_DEBUG_UART_CLOCK=0
> >> +
> >> +Obtaining the QEMU devicetree
> >> +-----------------------------
> >> +
> >> +QEMU generates its own devicetree to pass to U-Boot and does this by default.
> >> +You can use `-dtb u-boot.dtb` to force QEMU to use U-Boot's in-tree version.
> >
> > this is for either Qemu experts or u-boot for Qemu maintainers. Not for the kernel développer as it is recipe for problems: could you add this warning ?
>
> Yes I can do that...or would it be better to hide this in doc/develop
> somewhere with a link here?
Somewhere under doc/develop and an external link to the QEMU
documentation on dumpdtb would be good, as it's (as you demonstrate
throughout this series) a generic feature.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-10-13 17:39 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 1:01 [PATCH 00/16] fdt: Make OF_BOARD a boolean option Simon Glass
2021-10-13 1:01 ` [PATCH 01/16] arm: qemu: Mention -nographic in the docs Simon Glass
2021-10-13 1:01 ` [PATCH 02/16] arm: qemu: Explain how to extract the generate devicetree Simon Glass
2021-10-13 1:19 ` François Ozog
2021-10-13 16:58 ` Simon Glass
2021-10-13 17:36 ` Tom Rini [this message]
2021-10-13 1:01 ` [PATCH 03/16] riscv: " Simon Glass
2021-10-13 1:01 ` [PATCH 04/16] arm: qemu: Add a devicetree file for qemu_arm Simon Glass
2021-10-13 1:01 ` [PATCH 05/16] arm: qemu: Add a devicetree file for qemu_arm64 Simon Glass
2021-10-13 1:15 ` François Ozog
2021-10-27 14:44 ` Alex Bennée
2021-10-27 14:56 ` Tom Rini
2021-10-27 18:34 ` Simon Glass
2021-10-27 18:39 ` Tom Rini
2021-10-27 19:45 ` Alex Bennée
2021-10-13 1:01 ` [PATCH 06/16] riscv: qemu: Add devicetree files for qemu_riscv32/64 Simon Glass
2021-10-13 4:21 ` Heinrich Schuchardt
2021-10-13 1:29 ` [PATCH 00/16] fdt: Make OF_BOARD a boolean option Bin Meng
2021-10-13 1:34 ` Tom Rini
2021-10-13 8:02 ` François Ozog
2021-10-13 14:47 ` Simon Glass
2021-10-13 17:34 ` François Ozog
2021-10-13 18:06 ` Simon Glass
2021-10-14 14:56 ` Tom Rini
2021-10-14 15:17 ` Simon Glass
2021-10-14 15:28 ` Tom Rini
2021-10-14 17:58 ` François Ozog
2021-10-15 18:03 ` Simon Glass
2021-10-26 6:46 ` Ilias Apalodimas
2021-10-27 12:59 ` Tom Rini
2021-10-27 13:30 ` François Ozog
2021-10-27 13:38 ` Tom Rini
2021-10-27 13:47 ` Ilias Apalodimas
2021-10-27 14:26 ` Tom Rini
2021-10-27 13:48 ` François Ozog
2021-10-27 14:30 ` Tom Rini
2021-10-28 2:50 ` Simon Glass
2021-10-28 8:21 ` François Ozog
2021-10-28 14:30 ` Simon Glass
2021-10-28 14:50 ` François Ozog
2021-10-28 15:44 ` Simon Glass
2021-10-28 16:25 ` François Ozog
2021-11-02 14:59 ` Simon Glass
2021-11-01 11:04 ` Ilias Apalodimas
2021-11-02 10:06 ` Michael Walle
2021-11-02 12:34 ` François Ozog
2021-11-02 14:59 ` Simon Glass
2021-10-27 12:48 ` Tom Rini
2021-10-27 13:15 ` François Ozog
2021-10-27 13:23 ` Heinrich Schuchardt
2021-10-27 14:55 ` Tom Rini
2021-10-27 15:02 ` Heinrich Schuchardt
2021-10-27 18:04 ` Tom Rini
2021-10-27 14:54 ` Tom Rini
2021-10-27 15:10 ` Mark Kettenis
2021-10-27 15:24 ` Simon Glass
2021-10-27 18:06 ` Tom Rini
2021-10-27 18:11 ` François Ozog
2021-10-27 21:52 ` Mark Kettenis
2021-10-27 16:02 ` François Ozog
2021-10-27 19:06 ` Tom Rini
2021-10-27 22:00 ` François Ozog
2021-10-28 14:41 ` Tom Rini
2021-10-14 16:24 ` Andre Przywara
2021-10-14 17:48 ` François Ozog
2021-10-14 18:12 ` François Ozog
2021-10-14 21:00 ` Simon Glass
2021-10-13 12:39 ` Philippe Mathieu-Daudé
2021-10-13 13:06 ` François Ozog
2021-10-13 4:26 ` Heinrich Schuchardt
2021-10-13 13:06 ` François Ozog
2021-10-13 9:50 ` Andre Przywara
2021-10-13 13:05 ` François Ozog
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=20211013173612.GX7964@bill-the-cat \
--to=trini@konsulko.com \
--cc=albert.u.boot@aribaud.net \
--cc=francois.ozog@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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).