From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@xilinx.com>
Cc: buildroot@buildroot.org, wesley@sonifex.co.uk,
giulio.benetti@benettiengineering.com, michal.simek@amd.com,
yann.morin.1998@free.fr
Subject: Re: [Buildroot] [PATCH v2 1/1] configs/zynqmp_kria_kv260_defconfig: fix to u-boot.itb generation
Date: Wed, 22 Jun 2022 10:29:33 +0200 [thread overview]
Message-ID: <20220622102933.345ead6c@booty> (raw)
In-Reply-To: <20220622042439.30423-1-neal.frager@xilinx.com>
Hi Neal,
On Tue, 21 Jun 2022 22:24:39 -0600
Neal Frager <neal.frager@xilinx.com> wrote:
> This patch is a temporary fix for the kv260 u-boot.itb generation
> until a proper fix has been implemented within u-boot.
>
> The problem is u-boot can only be configured to use the kria k26
> som dts configuration at build time, and the kv260 carrier board
> overlay is missing from the build. Without this, all of the carrier
> board drivers are missing.
>
> This patch will be removed from buildroot once u-boot can build a
> correct u-boot.itb for the kria kv260 starter kit including the
> carrier board overlay and corresponding drivers.
Adding here the link provided by Michal would have been nice (and also
easy to do...):
https://lore.kernel.org/all/20920b0df6b067aca4040459a9677d7d1d6d766a.1615354376.git.viresh.kumar@linaro.org/
Maybe the BR maintainer wants to add it while applying this patch?
With this possibly added:
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-06-22 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 4:24 [Buildroot] [PATCH v2 1/1] configs/zynqmp_kria_kv260_defconfig: fix to u-boot.itb generation Neal Frager
2022-06-22 8:29 ` Luca Ceresoli via buildroot [this message]
2022-06-22 20:26 ` Yann E. MORIN
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=20220622102933.345ead6c@booty \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@xilinx.com \
--cc=wesley@sonifex.co.uk \
--cc=yann.morin.1998@free.fr \
/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