[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 05/16] arm: qemu: Add a devicetree file for qemu_arm64
|
From: |
Tom Rini |
|
Subject: |
Re: [PATCH 05/16] arm: qemu: Add a devicetree file for qemu_arm64 |
|
Date: |
Wed, 27 Oct 2021 10:56:53 -0400 |
On Wed, Oct 27, 2021 at 03:44:08PM +0100, Alex Bennée wrote:
>
> François Ozog <francois.ozog@linaro.org> writes:
>
> > Hi Simon
> >
> > The only place I could agree with this file presence is in the
> > documentation directory, not in dts. It creates a mental picture for the
> > reader
> > an entirely bad mind scheme around Qemu and DT.
> >
> > And even in a documentation directory I would place a bug warning: don’t
> > use this with any kernel , Qemu generates a DT dynamically
> > based on cpu, memory and devices specified at the command line.
>
> Certainly for the arm, aarch64 and riscv "virt" machines you should
> always use the QEMU generated DTB. I'm not entirely clear what a
> qemu_arm and qemu_arm64 def targets are meant to be in this context.
Agreed. We cannot include random device trees in U-Boot for devices
that generate their own at run time or otherwise have the source of
truth elsewhere.
--
Tom
signature.asc
Description: PGP signature
[PATCH 06/16] riscv: qemu: Add devicetree files for qemu_riscv32/64, Simon Glass, 2021/10/12
[PATCH 02/16] arm: qemu: Explain how to extract the generate devicetree, Simon Glass, 2021/10/12
Re: [PATCH 00/16] fdt: Make OF_BOARD a boolean option, Bin Meng, 2021/10/12