devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

From: Igor Opaniuk <igor.opaniuk-WQOgUJUq/S3vYQKSrp0J2Q@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Applying dtb overlays on pre-compiled dtb's
Date: Mon, 27 Feb 2023 16:25:42 +0200	[thread overview]
Message-ID: <CAL6CDMFiV0_rmE+gTow0X7Wnj7eS6YDu0Ya7dmNACnL1rRy4_w@mail.gmail.com> (raw)

Hi everyone,

I apologize in advance for the possibly wrong ML for this question.

I'm currently looking for any existing ways of adjusting pre-compiled device
tree blobs. I know that dtc doesn't have such ability (and obviously its purpose
is different), but maybe there is something you can recommend in this case
(kind of userland analogy of U-Boot's runtime "fdt apply" cmd).

For instance, I would like to add one property to "/firmware" (its value
 is generated during compile time) node into multiple device tree
blobs built with-in
Linux/U-Boot/TF-A, avoiding any additional intrusive changes to these source
trees (so, for example, adding dtsi with needed firmware property
unfortunately doesn't work for me).

The only solution I see is a custom app that uses libfdt, implemented
specifically
for this task, but maybe there is something which already exists.

Thanks and looking forward to your replies.

-- 
Best regards - Freundliche Grüsse - Meilleures salutations

Igor Opaniuk
Embedded Software Engineer
T:  +380 938364067
E: igor.opaniuk-WQOgUJUq/S3vYQKSrp0J2Q@public.gmane.org
W: www.foundries.io

next             reply	other threads:[~2023-02-27 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 14:25 Igor Opaniuk [this message]
     [not found] ` <CAL6CDMFiV0_rmE+gTow0X7Wnj7eS6YDu0Ya7dmNACnL1rRy4_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-02-27 16:17   ` Applying dtb overlays on pre-compiled dtb's Simon Glass
2023-02-27 16:47   ` 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=CAL6CDMFiV0_rmE+gTow0X7Wnj7eS6YDu0Ya7dmNACnL1rRy4_w@mail.gmail.com \
    --to=igor.opaniuk-wqogujuq/s3vyqksrp0j2q@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.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

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).