From: Antoni Jankowski <antoni.s.jankowski@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Igor Opaniuk <igor.opaniuk@gmail.com>, u-boot@lists.denx.de
Subject: Re: Distro Boot instructions with examples
Date: Tue, 14 May 2024 12:37:01 +0300 [thread overview]
Message-ID: <CAM4sPk-XioK7+_AskiavrYHZFQKdZGOqAkaJbTfERYqz22to-A@mail.gmail.com> (raw)
In-Reply-To: <87zft1he71.fsf@bloch.sibelius.xs4all.nl>
Thanks for your suggestions. I read the docs and it seems that maybe the
standard boot procedure is a bit too much, the current u-boot config for
raspberry pi CM4 is very simple and I'd like to keep it that way.
By default the u-boot environment on CM4 is kept on the boot FAT partition.
Would it be a good solution to simply copy all the CM4 related (but not
u-boot) files like the kernel image, the device trees and the rpi config
files (config.txt, cmdline.txt) to the rootfs partition and only tell
u-boot that they are available there?
I suppose that the files *.elf files should also stay on the /boot
partition along with the uboot.env.
Best regards,
Antoni
On Tue, May 7, 2024 at 5:46 PM Mark Kettenis <mark.kettenis@xs4all.nl>
wrote:
> > From: Igor Opaniuk <igor.opaniuk@gmail.com>
> > Date: Tue, 7 May 2024 16:30:17 +0200
> >
> > Hello Antoni,
> >
> > On Tue, May 7, 2024 at 4:14 PM Antoni Jankowski
> > <antoni.s.jankowski@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > I've recently learned about the Distro Boot feature of u-boot. This
> sounds
> > > interesting, however the official instructions are sparse and examples
> seem
> > > to be non-existent.
> > >
> > > The platform I'm working with at the moment is a raspberry pi CM4, are
> > > there any examples of how to implement this concept? Distro Boot seems
> to
> > > be suitable for updating all the rootfs at once, including what
> usually is
> > > a separate boot partition.
> > >
> > > Best regards,
> > > Antoni
> >
> > There is a nice manual from Toradex about Distro Boot integration [1].
> > You can also find a bunch of examples of integration of existing boards
> > just by grep-ing:
> >
> > u-boot.git$ grep -ine "config_distro_bootcmd" -r ./include/configs/
> > ./include/configs/pico-imx6ul.h:86:#include <config_distro_bootcmd.h>
> > ./include/configs/kp_imx6q_tpc.h:84:#include <config_distro_bootcmd.h>
> > ./include/configs/imx8mp_venice.h:21:#include <config_distro_bootcmd.h>
> > ./include/configs/stm32f746-disco.h:30:#include <config_distro_bootcmd.h>
> > ...
> >
> > Hope this helps.
> >
> > [1]
> https://developer.toradex.com/linux-bsp/os-development/boot/distro-boot/
>
> However, "distro boot" is being superseded by "standard boot" in
> recent versions of U-Boot and the raspberry pi boards have already
> moved on. See doc/develop/bootstd.rst for some documentation on
> "standard boot".
>
prev parent reply other threads:[~2024-05-14 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 13:21 Distro Boot instructions with examples Antoni Jankowski
2024-05-07 14:30 ` Igor Opaniuk
2024-05-07 14:46 ` Mark Kettenis
2024-05-14 9:37 ` Antoni Jankowski [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=CAM4sPk-XioK7+_AskiavrYHZFQKdZGOqAkaJbTfERYqz22to-A@mail.gmail.com \
--to=antoni.s.jankowski@gmail.com \
--cc=igor.opaniuk@gmail.com \
--cc=mark.kettenis@xs4all.nl \
--cc=u-boot@lists.denx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).