From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Heiko Thiery <heiko.thiery@gmail.com>
Cc: Matt Weber <matthew.weber@rockwellcollins.com>,
Michael Walle <michael@walle.cc>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/uboot-tools: use U-Boot host tool printinitialenv to extract environment
Date: Mon, 5 Jan 2026 14:56:11 +0100 [thread overview]
Message-ID: <20260105145611.7a99251d@windsurf> (raw)
In-Reply-To: <CAEyMn7bBCT4qMbJbMPkPHVuvC7rGM-LcQsNaL8=rMw1790mp-A@mail.gmail.com>
On Mon, 5 Jan 2026 14:50:44 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> > I'm not sure why we're using $(UBOOT_SRCDIR) in all of this instead of
> > $(@D), but that's a comment unrelated to your change.
>
> At least for the first case we need to use the file coming from the
> built U-Boot and not from the used sources from u-boot-tools package
> (an older U-Boot version). How it is for the "old" path I do not know
> if we could use here the script from the u-boot-tools package version
> or if it is also related to the U-Boot sources related to the
> environment.
Aaah, yes, indeed.
Isn't it a bit crappy that the uboot-tools package does that? This
logic is in uboot-tools, but it uses nothing from uboot-tools, only
stuff from the uboot package. But oh well, we're not going to
revolutionize this now :)
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:[~2026-01-05 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 13:23 [Buildroot] [PATCH v2] package/uboot-tools: use U-Boot host tool printinitialenv to extract environment Heiko Thiery
2026-01-05 13:42 ` Thomas Petazzoni via buildroot
2026-01-05 13:50 ` Heiko Thiery
2026-01-05 13:56 ` Thomas Petazzoni via buildroot [this message]
2026-01-05 15:31 ` Arnout Vandecappelle 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=20260105145611.7a99251d@windsurf \
--to=buildroot@buildroot.org \
--cc=heiko.thiery@gmail.com \
--cc=matthew.weber@rockwellcollins.com \
--cc=michael@walle.cc \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox