From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: "Frager, Neal" <neal.frager@amd.com>,
"Frager, Neal via buildroot" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2 1/1] boot/uboot/uboot.mk: add stripped u-boot.elf support
Date: Tue, 22 Nov 2022 21:47:13 +0100 [thread overview]
Message-ID: <20221122214713.1359fcac@windsurf> (raw)
In-Reply-To: <20221122190743.2610e8e9@booty>
On Tue, 22 Nov 2022 19:07:43 +0100
Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
> I agree with the principle you are proposing.
>
> However, according to the U-Boot source code, u-boot.elf appears as
> u-boot.bin repackaged into an ELF file. Is "stripped" a correct word
> for this?
I used "stripped" because that's how Neal described this file.
Based on what you say, perhaps a better option name is:
BR2_TARGET_UBOOT_FORMAT_BIN_ELF
bool "u-boot.elf"
Thoughts?
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:[~2022-11-22 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 5:36 [Buildroot] [PATCH v2 1/1] boot/uboot/uboot.mk: add stripped u-boot.elf support Neal Frager via buildroot
2022-11-22 9:01 ` Luca Ceresoli via buildroot
2022-11-22 9:43 ` Frager, Neal via buildroot
2022-11-22 16:13 ` Thomas Petazzoni via buildroot
2022-11-22 18:07 ` Luca Ceresoli via buildroot
2022-11-22 20:47 ` Thomas Petazzoni via buildroot [this message]
2022-11-22 21:31 ` Luca Ceresoli via buildroot
2022-11-23 0:09 ` Frager, Neal via buildroot
2022-11-23 13:31 ` Thomas Petazzoni via buildroot
2022-11-23 14:06 ` Frager, Neal 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=20221122214713.1359fcac@windsurf \
--to=buildroot@buildroot.org \
--cc=luca.ceresoli@bootlin.com \
--cc=neal.frager@amd.com \
--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