From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Devicetree add-on
Date: Tue, 4 Feb 2025 18:31:00 +0300 [thread overview]
Message-ID: <CAP1tNvSnOaCbW9qFt34JX_L5Ljiz2cxd1A4cgtOiiHmHjzd2ag@mail.gmail.com> (raw)
In-Reply-To: <Z5zNy19vd_13rRsY@pengutronix.de>
Hello All!
Eventually I switched to using overlays.
Of course, there are some unsolved problems, such as already occupied aliases
if they are specified in the overlay, or, for example, using
"assigned-clocks" in
overlays for already probed devices. I will give two examples from my
current projects,
criticize them if it is not difficult, maybe an idea will arise on how
to do it better.
The first link with two overlays [1], the third with three [2]:)
[1] https://github.com/MacroGroup/barebox/blob/macro/arch/arm/boards/diasom-rk3568/board.c
[2] https://github.com/shcgit/barebox-github/blob/milas/arch/arm/boards/mm-sm-sama5d2/board.c
Thanks!
пт, 31 янв. 2025 г. в 16:19, Sascha Hauer <s.hauer@pengutronix.de>:
>
> On Thu, Jan 30, 2025 at 04:45:48PM +0300, Alexander Shiyan wrote:
> > Hello.
> >
> > Yes, I understand that.
> > But maybe we can make another entry point to start from scratch,
> > but with another tree, roughly the same way we do with pbl?
>
> It's not universally possible to jump into the currently running image.
> Static variables in the data section might be modified already.
>
> Of course you can load the barebox image from the boot device again
> manually and jump into it, with a device tree passed in a pointer this
> time.
>
> 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 |
prev parent reply other threads:[~2025-02-04 15:37 UTC|newest]
Thread overview: 7+ 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
2025-01-30 13:45 ` Alexander Shiyan
2025-01-31 13:19 ` Sascha Hauer
2025-02-04 15:31 ` Alexander Shiyan [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=CAP1tNvSnOaCbW9qFt34JX_L5Ljiz2cxd1A4cgtOiiHmHjzd2ag@mail.gmail.com \
--to=eagle.alexander923@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox