Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <neal.frager@amd.com>
Cc: <buildroot@buildroot.org>,  <luca.ceresoli@bootlin.com>,
	<thomas.petazzoni@bootlin.com>,  <michal.simek@amd.com>,
	 <ju.o@free.fr>, <brandon.maier@collins.com>,
	 <romain.naour@smile.fr>, <ibai.erkiaga-elorza@amd.com>
Subject: Re: [Buildroot] [PATCH v6 2/6] boot/uboot: add qspi.bin file support
Date: Tue, 04 Feb 2025 14:27:46 +0100	[thread overview]
Message-ID: <871pwdon59.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250125224930.3639111-2-neal.frager@amd.com> (Neal Frager's message of "Sat, 25 Jan 2025 22:49:26 +0000")

>>>>> "Neal" == Neal Frager <neal.frager@amd.com> writes:

 > u-boot has introduced a new file called qspi.bin for users who boot from a
 > qspi flash device.  It combines the spl/boot.bin and u-boot.itb files into a
 > single binary that can be written to the qspi flash.

 > Here is an example of how binman generates the qspi.bin:
 > https://source.denx.de/u-boot/u-boot/-/commit/a4c98119109a60b9b236996f47065aa8fc0de9ca

 > At the moment, the qspi.bin is only used for the zynqmp platform, but other
 > platforms may adopt it, so the buildroot support has been made in a generic
 > way.

 > This patch adds the necessary support for buildroot to install this binary.

 > [Tested on Kria KV260 starter kit]
 > Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
 > Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>

 > Signed-off-by: Neal Frager <neal.frager@amd.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-02-04 13:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-25 22:49 [Buildroot] [PATCH v6 1/6] boot/uboot: binman generates u-boot.itb Neal Frager
2025-01-25 22:49 ` [Buildroot] [PATCH v6 2/6] boot/uboot: add qspi.bin file support Neal Frager
2025-02-04 13:27   ` Peter Korsgaard [this message]
2025-01-25 22:49 ` [Buildroot] [PATCH v6 3/6] board/zynqmp/patches: add zynqmp binman patches Neal Frager via buildroot
2025-02-04 13:28   ` Peter Korsgaard
2025-01-25 22:49 ` [Buildroot] [PATCH v6 4/6] configs/zynqmp_*: migrate to binman Neal Frager via buildroot
2025-01-25 22:58   ` Frager, Neal
2025-01-31 13:10   ` Luca Ceresoli via buildroot
2025-02-04 13:29   ` Peter Korsgaard
2025-01-25 22:49 ` [Buildroot] [PATCH v6 5/6] board/zynqmp: add new qspi.bin binary to images Neal Frager
2025-01-31 13:11   ` Luca Ceresoli via buildroot
2025-02-04 13:30   ` Peter Korsgaard
2025-02-04 13:33     ` Frager, Neal via buildroot
2025-01-25 22:49 ` [Buildroot] [PATCH v6 6/6] board/zynqmp/kria: update readme.txt Neal Frager via buildroot
2025-01-31 13:12   ` Luca Ceresoli via buildroot
2025-02-04 13:30   ` Peter Korsgaard
2025-02-04 13:27 ` [Buildroot] [PATCH v6 1/6] boot/uboot: binman generates u-boot.itb Peter Korsgaard

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=871pwdon59.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=brandon.maier@collins.com \
    --cc=buildroot@buildroot.org \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=ju.o@free.fr \
    --cc=luca.ceresoli@bootlin.com \
    --cc=michal.simek@amd.com \
    --cc=neal.frager@amd.com \
    --cc=romain.naour@smile.fr \
    --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