From: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
To: Trent Piepho <trent.piepho@igorinstitute.com>
Cc: barebox@lists.infradead.org
Subject: Re: Howto implement bootchooser <-> rauc interaction
Date: Mon, 06 Dec 2021 09:30:38 +0100 [thread overview]
Message-ID: <bfa5b77b1367dec7d64bba249c24b441@inside-m2m.de> (raw)
In-Reply-To: <CAMHeXxOoXjqtSGXdE73oROUk9ybFmFv7gi8PtzLsKn=iH+FXLA@mail.gmail.com>
Dear Trent,
thank you so much for this comprehensive clarification.
On 2021-12-03 18:52, Trent Piepho wrote:
> You should add a node of "barebox,state" to the *Barebox* device tree.
I will try to prepare a proper device tree.
It was this special tiny detail:
> must have state node ALSO in the Linux device tree. But you do not
> need to add it manually! Barebox will automatically inject the state
What I was not aware of, yet! I think I got the point now.
> For this to work, you need to have Barebox give the kernel the Linux
> device tree when booting. This is the normal way to boot now. All
> current docs tell you to do this. There was a much older style where
> the dtb was appended to the kernel image and the kernel found it
> itself without involving the bootloader. I assume this will not work,
> but I think Barebox state did not exist when I last booted a system
> this way, so I haven't tried.
Yes, no problem, I stumpled upon the combined image+dtb thingy once in
our
but the new stuff I am working upon is barebox passing the dtb to the
kernel.
Thanks also for explaining the possibilities and requirements,
I will figure a nice way to do this on my Beaglebone Black now.
Kind Regards
Konstantin
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-12-06 8:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 12:40 Howto implement bootchooser <-> rauc interaction Konstantin Kletschke
2021-12-03 17:52 ` Trent Piepho
2021-12-05 22:55 ` Roland Hieber
2021-12-06 8:52 ` Konstantin Kletschke
2021-12-14 21:40 ` Konstantin Kletschke
2021-12-15 10:56 ` Ahmad Fatoum
2021-12-16 19:35 ` Konstantin Kletschke
2021-12-17 10:00 ` Ahmad Fatoum
2021-12-17 12:50 ` Konstantin Kletschke
2022-01-03 15:24 ` Roland Hieber
2021-12-06 8:30 ` Konstantin Kletschke [this message]
2021-12-14 21:28 ` Konstantin Kletschke
2021-12-15 10:50 ` Ahmad Fatoum
[not found] ` <297b3425baa118783dccb6446900fbfa@inside-m2m.de>
2021-12-16 19:42 ` Fwd: " Konstantin Kletschke
2021-12-17 9:46 ` Ahmad Fatoum
2021-12-17 12:43 ` Konstantin Kletschke
2021-12-17 13:08 ` Ahmad Fatoum
2021-12-17 14:21 ` Konstantin Kletschke
2021-12-22 14:05 ` Konstantin Kletschke
2022-01-05 17:50 ` Ahmad Fatoum
2022-01-06 9:59 ` Konstantin Kletschke
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=bfa5b77b1367dec7d64bba249c24b441@inside-m2m.de \
--to=konstantin.kletschke@inside-m2m.de \
--cc=barebox@lists.infradead.org \
--cc=trent.piepho@igorinstitute.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.