Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: Bradley.Gamble@entrust.com, ibai.erkiaga-elorza@amd.com,
	thomas.petazzoni@bootlin.com, buildroot@buildroot.org,
	david.evans@ebv.com, dylan.bespalko@amd.com,
	michal.simek@amd.com
Subject: Re: [Buildroot] [PATCH v3 1/1] configs/zynqmp_kria_kr260_defconfig: new defconfig
Date: Fri, 22 Sep 2023 16:10:42 +0200	[thread overview]
Message-ID: <20230922161042.5c4bd39a@booty> (raw)
In-Reply-To: <20230903075427.738733-1-neal.frager@amd.com>

Hi Neal,

On Sun, 3 Sep 2023 08:54:27 +0100
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.

The above 2 items are the same as the KV260, right?

> 3. The KR260 has a USB to SD card bridge, so the Linux kernel
> and file system are found on /dev/sda1 and /dev/sda2.
> 
> 4. The following patches have been submitted upstream for u-boot.  They are
> required for enabling the pinctrl of the tri-state registers, so that u-boot
> can detect the SD card connected via the USB to SD card bridge on the KR260
> carrier board.  These patches are temporarily included with buildroot until
> they have been applied upstream.
> 
> http://patchwork.ozlabs.org/project/uboot/list/?series=368369
> http://patchwork.ozlabs.org/project/uboot/list/?series=371196
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>

Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-09-22 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-03  7:54 [Buildroot] [PATCH v3 1/1] configs/zynqmp_kria_kr260_defconfig: new defconfig Neal Frager via buildroot
2023-09-22 14:10 ` Luca Ceresoli via buildroot [this message]
2023-09-22 14:16   ` Frager, Neal via buildroot
  -- strict thread matches above, loose matches on Subject: below --
2022-12-08  9:46 Neal Frager via buildroot
2022-12-19 12:36 ` Luca Ceresoli via buildroot
2022-12-19 12:42   ` Frager, Neal 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=20230922161042.5c4bd39a@booty \
    --to=buildroot@buildroot.org \
    --cc=Bradley.Gamble@entrust.com \
    --cc=david.evans@ebv.com \
    --cc=dylan.bespalko@amd.com \
    --cc=ibai.erkiaga-elorza@amd.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox