From: Tom Rini <trini@konsulko.com>
To: "François Ozog" <francois.ozog@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Albert Aribaud <albert.u.boot@aribaud.net>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Simon Glass <sjg@chromium.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Sean Anderson <seanga2@gmail.com>,
Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PATCH v5 06/26] arm: qemu: Add a devicetree file for qemu_arm64
Date: Mon, 1 Nov 2021 14:07:07 -0400 [thread overview]
Message-ID: <20211101180707.GJ24579@bill-the-cat> (raw)
In-Reply-To: <CAHFG_=XWc+Fb=m=SHC6=y4KeF533yqCNk=Ae088oAZyjOULPaw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]
On Mon, Nov 01, 2021 at 06:33:35PM +0100, François Ozog wrote:
> Hi Simon
>
> Le lun. 1 nov. 2021 à 17:58, Simon Glass <sjg@chromium.org> a écrit :
>
> > Hi Peter,
> >
> > On Mon, 1 Nov 2021 at 04:48, Peter Maydell <peter.maydell@linaro.org>
> > wrote:
> > >
> > > On Tue, 26 Oct 2021 at 01:33, Simon Glass <sjg@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@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.
Yes. We need to document how to make development easier. But I'm still
not on board with the notion of including DTS files for platforms where
the source of truth for the DTB is elsewhere. That's going to bring us
a lot more pain.
It is important to make sure our "develop our project" workflow is sane
and relatively pain free. But that needs to not come by making
sacrifices to the "use our project" outcome. I would hope for example
that the new Pi zero platform is just dtb changes, as far as the linux
kernel is concerned which means that for rpi_arm64 (which uses run time
dtb) it also just works. And that's what we want to see.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-11-01 20:25 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 0:23 [PATCH v5 00/26] fdt: Make OF_BOARD a boolean option Simon Glass
2021-10-26 0:23 ` [PATCH v5 03/26] arm: qemu: Mention -nographic in the docs Simon Glass
2021-10-26 0:23 ` [PATCH v5 04/26] arm: riscv: qemu: Explain how to extract the generated dt Simon Glass
2021-10-26 0:23 ` [PATCH v5 05/26] arm: qemu: Add a devicetree file for qemu_arm Simon Glass
2021-10-26 0:23 ` [PATCH v5 06/26] arm: qemu: Add a devicetree file for qemu_arm64 Simon Glass
2021-11-01 10:48 ` Peter Maydell
2021-11-01 16:58 ` Simon Glass
2021-11-01 17:33 ` François Ozog
2021-11-01 18:07 ` Tom Rini [this message]
2021-11-02 15:00 ` Simon Glass
2021-11-02 17:28 ` Tom Rini
2021-11-03 1:29 ` Simon Glass
2021-11-03 5:29 ` François Ozog
2021-11-03 14:41 ` Tom Rini
2021-11-04 11:09 ` Peter Maydell
2021-11-04 11:22 ` François Ozog
2021-11-04 11:41 ` Peter Maydell
2021-11-04 11:48 ` François Ozog
2021-11-03 14:44 ` François Ozog
2021-11-03 14:39 ` Tom Rini
2021-11-02 14:59 ` Simon Glass
2021-11-02 16:57 ` Tom Rini
2021-11-03 1:32 ` Simon Glass
2021-11-03 14:39 ` Tom Rini
2021-10-26 0:23 ` [PATCH v5 07/26] riscv: qemu: Add devicetree files for qemu_riscv32/64 Simon Glass
2021-10-26 6:07 ` [PATCH v5 00/26] fdt: Make OF_BOARD a boolean option François Ozog
2021-10-27 14:08 ` Simon Glass
2021-10-27 15:14 ` François Ozog
2021-10-27 18:23 ` Simon Glass
2021-10-27 19:25 ` Tom Rini
2021-11-03 16:45 ` Simon Glass
2021-11-03 17:21 ` Tom Rini
2021-10-27 20:07 ` François Ozog
2021-11-03 1:20 ` Simon Glass
2021-11-03 4:45 ` François Ozog
2021-10-27 22:30 ` Mark Kettenis
2021-11-03 1:20 ` Simon Glass
2021-11-03 8:22 ` Mark Kettenis
2021-11-03 16:02 ` Tom Rini
2021-11-03 16:45 ` Simon Glass
2021-11-03 17:36 ` Mark Kettenis
2021-11-03 15:56 ` Tom Rini
2021-11-03 16:45 ` Simon Glass
2021-10-27 15:36 ` Tuomas Tynkkynen
2021-10-27 19:13 ` Tom Rini
2021-10-27 18:16 ` Tom Rini
2021-10-27 18:24 ` Tom Rini
2021-11-03 17:13 ` 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=20211101180707.GJ24579@bill-the-cat \
--to=trini@konsulko.com \
--cc=albert.u.boot@aribaud.net \
--cc=francois.ozog@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=mark.kettenis@xs4all.nl \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=tuomas.tynkkynen@iki.fi \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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).