mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Devicetree add-on
Date: Thu, 30 Jan 2025 14:39:22 +0100	[thread overview]
Message-ID: <Z5uBCoIy69dB3QH_@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvRa-1XPm087pzti1XmqvRDqchKOWZgvgYmcAQh+uOayBg@mail.gmail.com>

Hi Alexander,

On Wed, Jan 29, 2025 at 09:10:58AM +0300, Alexander Shiyan wrote:
> Hello All.
> 
> The question arose whether it is possible to load an add-on into
> devicetree, but NOT through an overlay,
> i.e. as a full-fledged dtb?
> Ideally, it should look like this: the main ENTRY_FUNCTION() loads the
> base tree, then,
> after initialization in device_initcall(), the board modification is
> determined and the full devicetree
> written for this variant is loaded.

exchanging the device tree during runtime is not a good idea. Pointers
from the old tree might still be in use. Also it's not easy to track
which devices have been probed already and which have to be probed from
the new tree. Exchanging the device tree might work at first, but opens
the door for some bad surprises.

Do you need the full device tree in barebox itself or just in the
Kernel? If the latter I would just start the kernel with the full device
tree and keep the original one in barebox.

There are also some boards in the tree in which we use I2C EEPROM
support in PBL, so we can pick the correct device tree from the start
rather than starting with a base device tree.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  parent reply	other threads:[~2025-01-30 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29  6:10 Alexander Shiyan
2025-01-29  8:50 ` Marco Felsch
2025-01-30  8:06   ` Alexander Shiyan
2025-01-30 13:39 ` Sascha Hauer [this message]
2025-01-30 13:45   ` Alexander Shiyan
2025-01-31 13:19     ` Sascha Hauer

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=Z5uBCoIy69dB3QH_@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=eagle.alexander923@gmail.com \
    /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