From: Peng Fan <peng.fan@oss.nxp.com>
To: Marek Vasut <marex@nabladev.com>
Cc: u-boot@lists.denx.de, "NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Simon Glass <sjg@chromium.org>,
Stefano Babic <sbabic@nabladev.com>,
Tom Rini <trini@konsulko.com>,
Wojciech Dubowik <Wojciech.Dubowik@mt.com>,
Yannic Moog <y.moog@phytec.de>
Subject: Re: [PATCH v2 1/3] binman: imx8mimage: Generate FSPI header in binman instead of mkimage
Date: Wed, 1 Jul 2026 15:37:06 +0800 [thread overview]
Message-ID: <akTDoiZsrHsBpU/y@shlinux89> (raw)
In-Reply-To: <20260630084112.13259-1-marex@nabladev.com>
On Tue, Jun 30, 2026 at 10:40:46AM +0200, Marek Vasut wrote:
>Stop depending on the current mkimage method of generating the FSPI
>header, instead generate the FSPI header within binman itself. This
>is more flexible, as the FSPI header properties can be configured
>from within the board-specific DT instead of being hard-coded in
>mkimage at build time.
>
>Signed-off-by: Marek Vasut <marex@nabladev.com>
Acked-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2026-07-01 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 8:40 [PATCH v2 1/3] binman: imx8mimage: Generate FSPI header in binman instead of mkimage Marek Vasut
2026-06-30 8:40 ` [PATCH v2 2/3] arm64: dts: imx8mm: Drop nxp,fspi-header-filename Marek Vasut
2026-07-01 7:37 ` Peng Fan
2026-07-02 11:14 ` Simon Glass
2026-06-30 8:40 ` [PATCH v2 3/3] arm64: dts: imx8mn: " Marek Vasut
2026-07-01 7:37 ` Peng Fan
2026-07-02 11:16 ` Simon Glass
2026-07-01 7:37 ` Peng Fan [this message]
2026-07-02 11:13 ` [PATCH v2 1/3] binman: imx8mimage: Generate FSPI header in binman instead of mkimage Simon Glass
2026-07-05 21:23 ` Marek Vasut
2026-07-06 12:27 ` Simon Glass
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=akTDoiZsrHsBpU/y@shlinux89 \
--to=peng.fan@oss.nxp.com \
--cc=Wojciech.Dubowik@mt.com \
--cc=festevam@gmail.com \
--cc=marex@nabladev.com \
--cc=quentin.schulz@cherry.de \
--cc=sbabic@nabladev.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--cc=y.moog@phytec.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 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.