[PATCH v5 06/26] arm: qemu: Add a devicetree file for qemu_arm64

François Ozog francois.ozog at linaro.org
Mon Nov 1 18:33:35 CET 2021

Hi Simon

Le lun. 1 nov. 2021 à 17:58, Simon Glass <sjg at chromium.org> a écrit :

> Hi Peter,
> On Mon, 1 Nov 2021 at 04:48, Peter Maydell <peter.maydell at linaro.org>
> wrote:
> >
> > On Tue, 26 Oct 2021 at 01:33, Simon Glass <sjg at chromium.org> wrote:
> > >
> > > Add this file, generated from qemu, so there is a reference devicetree
> > > in the U-Boot tree.
> > >
> > > Signed-off-by: Simon Glass <sjg at chromium.org>
> >
> > Note that the dtb you get from QEMU is only guaranteed to work if:
> >  1) you run it on the exact same QEMU version you generated it with
> >  2) you pass QEMU the exact same command line arguments you used
> >     when you generated it
> Yes, I certainly understand that. In general this is not safe, but in
> practice it works well enough for development and CI.

You recognize that you hijack a product directory with development hack
facility. There is a test directory to keep things clear. There can be a
dev-dts or something similar for Dev time tools.
I have only seen push back on those fake dts files in the dts directory: I
guess that unless someone strongly favors a continuation of the discussion,
you may consider re-shaping the proposal to address concerns.

> I am able to use
> QEMU versions that differ by two years, partly because I am not trying
> to do anything clever.
> I have sent a patch to add an indication of where the devicetree came
> from, to help with visibility on this.
> Regards,
> Simon
François-Frédéric Ozog | *Director Business Development*
T: +33.67221.6485
francois.ozog at linaro.org | Skype: ffozog

More information about the U-Boot mailing list