From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: terry.oneal@amd.com, kris.chaplin@amd.com,
thomas.petazzoni@bootlin.com, buildroot@buildroot.org,
michal.simek@amd.com
Subject: Re: [Buildroot] [PATCH v1 2/3] add board/versal
Date: Thu, 3 Nov 2022 09:14:31 +0100 [thread overview]
Message-ID: <20221103091431.5e57a65b@booty> (raw)
In-Reply-To: <20221024142216.31273-2-neal.frager@amd.com>
Hi Neal,
On Mon, 24 Oct 2022 08:22:15 -0600
Neal Frager <neal.frager@amd.com> wrote:
> --- /dev/null
> +++ b/board/versal/genimage.cfg
> @@ -0,0 +1,30 @@
> +image boot.vfat {
> + vfat {
> + files = {
> + "boot.bin",
> + "system.dtb",
system.dtb is stored in the FAT partition...
> --- /dev/null
> +++ b/board/versal/post-image.sh
> @@ -0,0 +1,35 @@
> +#!/bin/sh
> +
> +# By default U-Boot loads DTB from a file named "system.dtb", so
> +# let's use a symlink with that name that points to the *first*
> +# devicetree listed in the config.
> +
> +FIRST_DT=$(sed -nr \
> + -e 's|^BR2_LINUX_KERNEL_INTREE_DTS_NAME="xilinx/([-_/[:alnum:]\\.]*).*"$|\1|p' \
> + ${BR2_CONFIG})
> +
> +[ -z "${FIRST_DT}" ] || ln -fs ${FIRST_DT}.dtb ${BINARIES_DIR}/system.dtb
> +
> +BOARD_DIR="$(dirname $0)"
> +BOARD_NAME=$4
> +
> +mkdir -p "${BINARIES_DIR}"
> +cat <<-__HEADER_EOF > "${BINARIES_DIR}/bootgen.bif"
> + the_ROM_image:
> + {
> + image {
> + { type=bootimage, file=${BINARIES_DIR}/${BOARD_NAME}_vpl_gen_fixed.pdi }
> + { type=bootloader, file=${BINARIES_DIR}/${BOARD_NAME}_plm.elf }
> + { core=psm, file=${BINARIES_DIR}/${BOARD_NAME}_psmfw.elf }
> + }
> + image {
> + id = 0x1c000000, name=apu_subsystem
> + { type=raw, load=0x00001000, file=${BINARIES_DIR}/system.dtb }
...and also in boot.bin. What's the reason for this? One copy is for
U-Boot and the other for the kernel?
--
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-11-03 8:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 14:22 [Buildroot] [PATCH v1 1/3] add package/versal-firmware Neal Frager via buildroot
2022-10-24 14:22 ` [Buildroot] [PATCH v1 2/3] add board/versal Neal Frager via buildroot
2022-11-02 16:38 ` Thomas Petazzoni via buildroot
2022-11-02 16:56 ` Frager, Neal via buildroot
2022-11-03 8:14 ` Luca Ceresoli via buildroot [this message]
2022-11-03 9:03 ` Frager, Neal via buildroot
2022-10-24 14:22 ` [Buildroot] [PATCH v1 3/3] add configs/versal_vck190_defconfig Neal Frager via buildroot
2022-11-02 16:11 ` [Buildroot] [PATCH v1 1/3] add package/versal-firmware Frager, Neal via buildroot
2022-11-02 16:44 ` Thomas Petazzoni via buildroot
2022-11-02 17:10 ` Frager, Neal via buildroot
2022-11-03 7:46 ` Luca Ceresoli via buildroot
2022-11-03 9:08 ` Frager, Neal via buildroot
-- strict thread matches above, loose matches on Subject: below --
2022-08-19 6:37 Neal Frager
2022-08-19 6:37 ` [Buildroot] [PATCH v1 2/3] add board/versal Neal Frager
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=20221103091431.5e57a65b@booty \
--to=buildroot@buildroot.org \
--cc=kris.chaplin@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=terry.oneal@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