From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: "buildroot@buildroot.org" <buildroot@buildroot.org>
Cc: michal.simek@amd.com, Luca Ceresoli <luca.ceresoli@bootlin.com>,
thomas.petazzoni@bootlin.com, Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v4 1/1] configs/zynqmp_kria_kr260_defconfig: new defconfig
Date: Fri, 27 Jan 2023 19:22:40 +0100 [thread overview]
Message-ID: <20230127192240.096828b2@booty> (raw)
In-Reply-To: <20221228095626.2976f2b3@booty>
Hello,
On Wed, 28 Dec 2022 09:56:26 +0100
Luca Ceresoli via buildroot <buildroot@buildroot.org> wrote:
> On Thu, 22 Dec 2022 13:33:50 +0000
> Neal Frager <neal.frager@amd.com> wrote:
>
> > This patch adds support for Xilinx Kria KR260 starter kit.
> >
> > KR260 features can be found here:
> > https://www.xilinx.com/products/som/kria/kr260-robotics-starter-kit.html
> >
> > While the Kria SOM is based on a ZynqMP SoC, there are some key
> > boot config differences from the other ZynqMP evaluation boards.
> >
> > 1. There are no boot switches on Kria SOMs. The boot mode is thus
> > hard configured for QSPI flash. A pre-programmed boot.bin comes
> > with every Starter Kit. U-Boot can then find the Linux kernel and
> > file system on the SD card.
> >
> > Optional instructions for updating the boot.bin in the QSPI flash
> > can be found in the readme.txt file and the link below.
> >
> > https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1641152513/Kria+K26+SOM
> >
> > 2. Kria SOMs use UART1 for the console instead of UART0. For this
> > reason, Kria Starter Kits will use a separate extlinux.conf file
> > from other ZynqMP evaluation boards.
> >
> > Signed-off-by: Neal Frager <neal.frager@amd.com>
>
> Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
The dependency patch got applied to master, so this one should be clear
to go.
Strange however, I can't find this one in patchwork.
--
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:[~2023-01-27 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 13:33 [Buildroot] [PATCH v4 1/1] configs/zynqmp_kria_kr260_defconfig: new defconfig Neal Frager via buildroot
2022-12-22 13:36 ` Frager, Neal via buildroot
2022-12-28 8:56 ` Luca Ceresoli via buildroot
2023-01-27 18:22 ` Luca Ceresoli via buildroot [this message]
2023-01-27 19:32 ` Frager, Neal via buildroot
-- strict thread matches above, loose matches on Subject: below --
2023-10-26 11:50 Neal Frager via buildroot
2023-12-03 18:24 ` 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=20230127192240.096828b2@booty \
--to=buildroot@buildroot.org \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.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 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.