From: David Gibson <david@gibson.dropbear.id.au>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Devicetree Compiler <devicetree-compiler@vger.kernel.org>
Subject: Re: Record of original components for fdtoverlay
Date: Tue, 9 Jan 2024 21:51:16 +1100 [thread overview]
Message-ID: <ZZ0lJMxKeD-TGyEr@zatzit> (raw)
In-Reply-To: <CAK7LNARV8Bo-tBXMdOu55Wg9uZRXvNiRdkDJ4LH8PwVMnMp4cA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
On Tue, Jan 09, 2024 at 03:20:12PM +0900, Masahiro Yamada wrote:
> Hi.
>
> Sorry for a stupid question.
>
>
> When you get a DTB by using fdtoverlay, there is no way to
> know how it was produced later. Correct?
More or less, yes. Depending on the exact situation there might be
some clues that an overlay has been applied, but there's certainly no
easy or reliable way to tell.
> For instance, this case:
>
> $ fdtoverlay --input base.dtb ovl.dtbo --output foo.dtb
>
> Once you get foo.dtb, you will never know whether it was
> assembled from base.dtb + ovl.dtbo, or it was directly
> generated from a single source, foo.dts.
Correct.
> In my understanding, there is no room in DTB to record
> such metadata, and it is impossible to disassemble foo.dtb
> into the original components, base.dtb and ovl.dtbo.
Yes and no. It would certainly be possible to add special property
into the dtb to record a listing of the overlays applied. However,
that would only be accurate if the tools used to apply updated it
correctly, and of course the current ones don't.
Even with that, it wouldn't be possible to "unapply" overlays -
overlays can overwrite data in the base tree so it's no longer
available. There's not really any natural way of making that possible
within the dtb + overlay model.
> Please let me confirm that I did not miss anything.
>
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-11 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 6:20 Record of original components for fdtoverlay Masahiro Yamada
2024-01-09 10:51 ` David Gibson [this message]
2024-01-17 1:51 ` Masahiro Yamada
2024-01-09 20:23 ` Rob Herring
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=ZZ0lJMxKeD-TGyEr@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=masahiroy@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).