From: Max Krummenacher <max.oss.09@gmail.com>
To: u-boot@lists.denx.de
Cc: "Tom Rini" <trini@konsulko.com>,
"U-Boot STM32" <uboot-stm32@st-md-mailman.stormreply.com>,
"Pali Rohár" <pali@kernel.org>, "Adam Ford" <aford173@gmail.com>,
"Patrick DELAUNAY" <patrick.delaunay@foss.st.com>,
"Patrice CHOTARD" <patrice.chotard@foss.st.com>,
"Max Krummenacher" <max.krummenacher@toradex.com>,
"Heinrich Schuchardt" <xypron.glpk@gmx.de>,
"Marek Behún" <kabel@kernel.org>,
"Philippe Reynes" <philippe.reynes@softathome.com>,
"Quentin Schulz" <quentin.schulz@theobroma-systems.com>,
"Simon Glass" <sjg@chromium.org>
Subject: [PATCH v2 0/1] Makefile: rework u-boot-initial-env target
Date: Fri, 28 Oct 2022 18:18:48 +0200 [thread overview]
Message-ID: <20221028161850.565610-1-max.oss.09@gmail.com> (raw)
From: Max Krummenacher <max.krummenacher@toradex.com>
With CONFIG_LTO enabled the current way of extracting the
configured environment no longer works, i.e. the object file
content changes due to LTO.
Build a host tool which prints the configured environment instead
of using objcopy and friends to achive the same.
The code and Makefile changes were mostly stolen from tools/env/
i.e. the target userspace tools to access the environment.
Changes in v2:
- reworked to build a host tool which prints the configured
environment as proposed by Pali Rohár
https://lore.kernel.org/u-boot/20221018174827.1393211-1-max.oss.09@gmail.com/
- renamed patch, v1 used "Makefile: fix u-boot-initial-env target if lto is enabled"
Max Krummenacher (1):
Makefile: rework u-boot-initial-env target
Makefile | 7 ++++---
scripts/.gitignore | 1 +
scripts/Makefile | 5 +++++
scripts/printinitialenv.c | 44 +++++++++++++++++++++++++++++++++++++++
4 files changed, 54 insertions(+), 3 deletions(-)
create mode 100644 scripts/printinitialenv.c
--
2.35.3
next reply other threads:[~2022-10-28 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 16:18 Max Krummenacher [this message]
2022-10-28 16:18 ` [PATCH v2 1/1] Makefile: rework u-boot-initial-env target Max Krummenacher
2022-10-28 16:40 ` Pali Rohár
2022-10-31 10:51 ` Max Krummenacher
2022-11-01 14:07 ` Tom Rini
2022-11-01 17:35 ` Pali Rohár
2022-11-01 19:48 ` Tom Rini
2022-11-01 19:55 ` Pali Rohár
2022-11-01 20:00 ` Tom Rini
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=20221028161850.565610-1-max.oss.09@gmail.com \
--to=max.oss.09@gmail.com \
--cc=aford173@gmail.com \
--cc=kabel@kernel.org \
--cc=max.krummenacher@toradex.com \
--cc=pali@kernel.org \
--cc=patrice.chotard@foss.st.com \
--cc=patrick.delaunay@foss.st.com \
--cc=philippe.reynes@softathome.com \
--cc=quentin.schulz@theobroma-systems.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-stm32@st-md-mailman.stormreply.com \
--cc=xypron.glpk@gmx.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