From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org, Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH 4/7] configs/imx93frdm_defconfig: new defconfig
Date: Wed, 21 Oct 2026 22:06:53 +0200 [thread overview]
Message-ID: <atkbIM2X44OCSixP@windsurf> (raw)
In-Reply-To: <20261020102906.1918308-4-peter@korsgaard.com>
On Tue, Oct 20, 2026 at 12:28:58PM +0200, Peter Korsgaard wrote:
> The i.MX93 FRDM board is quite nicely supported in mainline, so add a
> defconfig using the latest mainline U-Boot/TF-A/Linux releases as an
> alternative to the vendor BSP used by freescale_imx93frdm_defconfig.
>
> Mainline U-Boot uses binman to assemble the flash.bin boot image, so we do
> not need the imx9-bootloader-prepare.sh post-image script.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> DEVELOPERS | 1 +
> .../arm-trusted-firmware.hash | 1 +
> .../imx93frdm/patches/linux/linux.hash | 2 +
> .../imx93frdm/patches/uboot/uboot.hash | 1 +
> configs/imx93frdm_defconfig | 46 +++++++++++++++++++
> 5 files changed, 51 insertions(+)
> create mode 100644 configs/imx93frdm_defconfig
Don't we try to have a readme.txt file for each defconfig?
We already have board/freescale/imx93frdm/readme.txt that covers the
freescale_imx93frdm_defconfig. Should this readme.txt simply be
extended/updated to cover both the "vendor" defconfig and the
"upstream" defconfig?
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-10-21 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 10:28 [Buildroot] [PATCH 1/7] package/freescale-ele-imx: install with original filename Peter Korsgaard
2026-10-20 10:28 ` [Buildroot] [PATCH 2/7] boot/uboot: add support for firmware-ele-imx Peter Korsgaard
2026-10-20 10:28 ` [Buildroot] [PATCH 3/7] board/freescale: use flash.bin for imx9 boot file Peter Korsgaard
2026-10-20 10:28 ` [Buildroot] [PATCH 4/7] configs/imx93frdm_defconfig: new defconfig Peter Korsgaard
2026-10-21 20:06 ` Thomas Petazzoni via buildroot [this message]
2026-10-21 21:29 ` Peter Korsgaard
2026-10-20 10:28 ` [Buildroot] [PATCH 5/7] configs/imx93-evk_defconfig: drop explicit FIRMWARE_IMX_LPDDR4=y Peter Korsgaard
2026-10-20 10:29 ` [Buildroot] [PATCH 6/7] configs/imx93-evk_defconfig: switch to Bootlin glibc toolchain Peter Korsgaard
2026-10-20 10:29 ` [Buildroot] [PATCH 7/7] configs/imx93-evk_defconfig: include EdgeLock firmware in boot image Peter Korsgaard
2026-10-21 20:05 ` [Buildroot] [PATCH 1/7] package/freescale-ele-imx: install with original filename Thomas Petazzoni 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=atkbIM2X44OCSixP@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=peter@korsgaard.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 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.