From: Marek Vasut <marek.vasut@mailbox.org>
To: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@konsulko.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Adriano Cordova <adrianox@gmail.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Peter Robinson <pbrobinson@gmail.com>,
Sam Edwards <cfsworks@gmail.com>,
u-boot@lists.denx.de
Subject: Re: [RFC][PATCH] kbuild: Produce diff between base DT and U-Boot augmented DT if DEVICE_TREE_DEBUG=1
Date: Tue, 11 Nov 2025 14:50:30 +0100 [thread overview]
Message-ID: <f1f10508-4767-4943-8411-8eb4bb0618aa@mailbox.org> (raw)
In-Reply-To: <CAFLszTjjhOj8g63vs_hprykYrWvEM=YuwT4ZNDnuppuJ-8aXZw@mail.gmail.com>
On 11/11/25 1:38 PM, Simon Glass wrote:
Hello Simon,
>>> Maybe we put it in the u-boot-extras repo for now as a standalone
>>> script, so people can be asked to run it and look at the output?
>> I'd say no, because the output is full of noise unless the phandle
>> non-resolution gets somehow improved.
>
> Another idea would be to create an fdtdiff tool which does this. We
> already have fdtgrep[1]
A new tool is not needed, up to date DTC retains the phandles across dtc
-I dts -O dts and the result can be diff'd using regular diff.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2025-11-11 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 21:08 [RFC][PATCH] kbuild: Produce diff between base DT and U-Boot augmented DT if DEVICE_TREE_DEBUG=1 Marek Vasut
2025-11-07 9:00 ` Fwd: " Heinrich Schuchardt
2025-11-07 10:21 ` E Shattow
2025-11-07 9:12 ` Heinrich Schuchardt
2025-11-07 14:06 ` Marek Vasut
2025-11-07 15:56 ` Tom Rini
2025-11-07 16:44 ` Marek Vasut
2025-11-09 23:44 ` Marek Vasut
2025-11-10 16:47 ` Tom Rini
2025-11-11 3:21 ` Marek Vasut
2025-11-11 12:38 ` Simon Glass
2025-11-11 13:50 ` Marek Vasut [this message]
2025-11-14 13:46 ` 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=f1f10508-4767-4943-8411-8eb4bb0618aa@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=adrianox@gmail.com \
--cc=cfsworks@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=pbrobinson@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--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 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.