From: Rob Herring <robh@kernel.org>
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 14:23:52 -0600 [thread overview]
Message-ID: <CAL_JsqLEpNhRNZvH0=+Mo6eWDhG37GHTozQEe2Zqv4Bjk_SkLg@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNARV8Bo-tBXMdOu55Wg9uZRXvNiRdkDJ4LH8PwVMnMp4cA@mail.gmail.com>
On Tue, Jan 9, 2024 at 12:20 AM Masahiro Yamada <masahiroy@kernel.org> 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?
>
> 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.
That is correct.
If the results are the same, why do you care?
> 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.
>
> Please let me confirm that I did not miss anything.
The kernel has the ability to un-apply overlays. I think that only
depends on having the original overlay and not any state from having
applied the overlay. fdtoverlay could be extended to do something
similar if you wanted to get base.dtb from foo.dtb and ovl.dtbo. If
you can't un-apply the overlay, then it would be a hint that it wasn't
created by applying the overlay.
Rob
prev parent reply other threads:[~2024-01-09 20:24 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
2024-01-17 1:51 ` Masahiro Yamada
2024-01-09 20:23 ` Rob Herring [this message]
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='CAL_JsqLEpNhRNZvH0=+Mo6eWDhG37GHTozQEe2Zqv4Bjk_SkLg@mail.gmail.com' \
--to=robh@kernel.org \
--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).