From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <neal.frager@amd.com>
Cc: michal.simek@amd.com, ibai.erkiaga-elorza@amd.com,
luca.ceresoli@bootlin.com, thomas.petazzoni@bootlin.com,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/1] configs/zynqmp_kria_kd240_defconfig: new defconfig
Date: Sat, 16 Dec 2023 10:50:18 +0100 [thread overview]
Message-ID: <877clebhnp.fsf@48ers.dk> (raw)
In-Reply-To: <20231213134849.2822206-1-neal.frager@amd.com> (Neal Frager's message of "Wed, 13 Dec 2023 13:48:49 +0000")
>>>>> "Neal" == Neal Frager <neal.frager@amd.com> writes:
> This patch adds support for Xilinx Kria KD240 starter kit.
> KD240 features can be found here:
> https://www.xilinx.com/products/som/kria/kd240-drives-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.
> 3. The KD240 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 to u-boot.
> Without these patches, the usb, sd card and ethernet peripherals
> do not work correctly.
> https://patchwork.ozlabs.org/project/uboot/patch/20231213134007.2818069-1-neal.frager@amd.com/
> https://patchwork.ozlabs.org/project/uboot/patch/20231213134052.2818879-1-neal.frager@amd.com/
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
> DEVELOPERS | 1 +
> board/zynqmp/kria/kd240/kd240.sh | 16 +
> ...nqmp-Fix-k24-psu_init_gpl.c-clocking.patch | 400 ++++++++++++++
> ...ynqmp-Add-output-enable-pins-to-SOMs.patch | 79 +++
> board/zynqmp/kria/kd240/pm_cfg_obj.c | 494 ++++++++++++++++++
> board/zynqmp/kria/readme.txt | 21 +-
> configs/zynqmp_kria_kd240_defconfig | 42 ++
> 7 files changed, 1045 insertions(+), 8 deletions(-)
> create mode 100755 board/zynqmp/kria/kd240/kd240.sh
> create mode 100644 board/zynqmp/kria/kd240/patches/uboot/0001-arm64-zynqmp-Fix-k24-psu_init_gpl.c-clocking.patch
> create mode 100644 board/zynqmp/kria/kd240/patches/uboot/0002-arm64-zynqmp-Add-output-enable-pins-to-SOMs.patch
> create mode 100644 board/zynqmp/kria/kd240/pm_cfg_obj.c
> create mode 100644 configs/zynqmp_kria_kd240_defconfig
I've fixed the check-package warnings and applied, thanks.
board/zynqmp/kria/kd240/patches/uboot/0001-arm64-zynqmp-Fix-k24-psu_init_gpl.c-clocking.patch:4: generate your patches with 'git format-patch -N'
board/zynqmp/kria/kd240/patches/uboot/0001-arm64-zynqmp-Fix-k24-psu_init_gpl.c-clocking.patch:0: missing Upstream in the header (http://nightly.buildroot.org/#_additional_patch_documentation)
board/zynqmp/kria/kd240/patches/uboot/0002-arm64-zynqmp-Add-output-enable-pins-to-SOMs.patch:4: generate your patches with 'git format-patch -N'
board/zynqmp/kria/kd240/patches/uboot/0002-arm64-zynqmp-Add-output-enable-pins-to-SOMs.patch:0: missing Upstream in the header (http://nightly.buildroot.org/#_additional_patch_documentation)
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-12-16 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 13:48 [Buildroot] [PATCH v1 1/1] configs/zynqmp_kria_kd240_defconfig: new defconfig Neal Frager via buildroot
2023-12-15 16:56 ` Luca Ceresoli via buildroot
2023-12-16 9:50 ` Peter Korsgaard [this message]
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=877clebhnp.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--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