From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: Niklas Cassel <cassel@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
Kilian Zinnecker <kilian.zinnecker@mail.de>,
Niklas Cassel via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 2/2] configs/rock5b_defconfig: enable uboot-env on the SD card
Date: Wed, 25 Sep 2024 22:26:13 +0200 [thread overview]
Message-ID: <20240925222613.3f62ed72@windsurf> (raw)
In-Reply-To: <Zuk_RMVJAzqVO5s8@ryzen.lan>
Hello Niklas,
It was nice meeting you during Linux Plumbers last week!
On Tue, 17 Sep 2024 08:35:16 +0000
Niklas Cassel <Niklas.Cassel@wdc.com> wrote:
> > This won't work because the output directory is not always output/. But
> > I believe this is useless, because you're creating an image of what is
> > the default environment. So basically, you should instead not create an
> > environment image at all: just tell U-Boot that the environment is at
> > offset XYZ (or even better, in partition X). The environment partition
> > will contain nothing or garbage, so at the first boot, U-Boot will use
> > its built-in environment itself, and at the first "saveenv", it will
> > save the environment to the designated partition.
>
> Well, what happens if you simply point to an offset or partition that is
> empty, is that uboot will see an empty environment, so it will see bootcmd
> as empty, so it will just enter the uboot command prompt without booting
> anything at all.
This is not what should happen. Indeed, if the environment on the
non-volatile storage is empty or corrupted, U-Boot should ignore it,
and load its built-in environment (which is compiled into the U-Boot
binary). Why isn't this working for you?
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-09-25 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 18:21 [Buildroot] [PATCH 0/2] rock5b quality of life improvements Niklas Cassel via buildroot
2024-09-09 18:21 ` [Buildroot] [PATCH 1/2] configs/rock5b: enable mdev to enable automatic module loading Niklas Cassel via buildroot
2024-09-14 20:15 ` Thomas Petazzoni via buildroot
2024-09-09 18:21 ` [Buildroot] [PATCH 2/2] configs/rock5b_defconfig: enable uboot-env on the SD card Niklas Cassel via buildroot
2024-09-14 20:20 ` Thomas Petazzoni via buildroot
2024-09-17 8:35 ` Niklas Cassel via buildroot
2024-09-17 8:46 ` Niklas Cassel via buildroot
2024-09-25 20:26 ` Thomas Petazzoni via buildroot [this message]
2024-10-03 13:45 ` Niklas Cassel via buildroot
2024-10-03 20:29 ` Niklas Cassel via buildroot
2024-10-03 13:49 ` Niklas Cassel via buildroot
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=20240925222613.3f62ed72@windsurf \
--to=buildroot@buildroot.org \
--cc=Niklas.Cassel@wdc.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=kilian.zinnecker@mail.de \
--cc=thomas.petazzoni@bootlin.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.