From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] configs/beagleboneai64_defconfig: new defconfig
Date: Mon, 6 May 2024 21:51:00 +0200 [thread overview]
Message-ID: <20240506215100.13296b7a@windsurf> (raw)
In-Reply-To: <20240506083905.14681-1-romain.naour@smile.fr>
Hello Romain,
On Mon, 6 May 2024 10:39:05 +0200
Romain Naour <romain.naour@smile.fr> wrote:
> Adds support for BeagleBone AI-64 board by introducing the
> beagleboneai64_defconfig file and related support files.
Perhaps you should state that this board uses the J721E SoC, also known
as DRA829, also known as TDA4VM. This would help...
>
> Retrieve BSP settings from meta-ti (may be useful for other TI boards):
>
> - This defconfig requires u-boot binman support added in u-boot since
> 2023.10.
> See FOSDEM 2024 talk by TI folks about Binman and how it simplify
> the overall boot-loader build flow [1].
>
> - Set BR2_TARGET_ARM_TRUSTED_FIRMWARE_TARGET_BOARD = "generic"
> meta-ti]$ git grep TFA_BOARD
> meta-ti-bsp/conf/machine/beagleplay.conf:TFA_BOARD = "lite"
> meta-ti-bsp/conf/machine/include/am62axx.inc:TFA_BOARD = "lite"
> meta-ti-bsp/conf/machine/include/am62pxx.inc:TFA_BOARD = "lite"
> meta-ti-bsp/conf/machine/include/am62xx.inc:TFA_BOARD = "lite"
> meta-ti-bsp/conf/machine/include/am64xx.inc:TFA_BOARD = "lite"
> meta-ti-bsp/conf/machine/include/am65xx.inc:TFA_BOARD = "generic"
> meta-ti-bsp/conf/machine/include/j7200.inc:TFA_BOARD = "generic"
> meta-ti-bsp/conf/machine/include/j721e.inc:TFA_BOARD = "generic"
... understand that this setting is the important one.
> meta-ti-bsp/conf/machine/include/j721s2.inc:TFA_BOARD = "generic"
> meta-ti-bsp/conf/machine/include/j722s.inc:TFA_BOARD = "lite"
> meta-ti-bsp/conf/machine/include/j784s4.inc:TFA_BOARD = "j784s4"
>
> - Set BR2_TARGET_UBOOT_NEEDS_ATF_BL31 to provide BL31 variable pointing
> to ATF bl31.bin to the U-Boot build process [2].
>
> - Set BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL32_OPTEE to OP-TEE as BL32
> secure payload. meta-ti set "SPD=opteed" to build ATF [3].
>
> - Set BR2_TARGET_OPTEE_OS_PLATFORM to "k3-j721e".
... and understand this setting as well.
> - u-boot is looking at /boot/dtb/ti for devicetree. But Buildroot
> strips the prefixes when installing them into /boot. Set
> BR2_LINUX_KERNEL_DTB_KEEP_DIRNAME to keep "ti" directory used by
> the kernel to organize device tree sources.
> TI's mmc.env [5] uses "dtb" as additional subdirectory, so we need
> to create a symlink to make sure /boot/dtb/ti exist.
> (Yocto uses KERNEL_DTBDEST = "${KERNEL_IMAGEDEST}/dtb").
> Using a symlink avoid to customize too much the u-boot environment.
>
> - At least, provide a custom uEnv.txt to avoid using "Standard boot"
> or "distroboot" [6] to boot.
I'm not sure to understand the "At least" here.
Also, why don't you want to use distroboot? We precisely try to
encourage using distroboot in Buildroot defconfigs, instead of uEnv.txt
stuff. So it's a bit going backward to use uEnv.txt here. Could you
explain this?
> diff --git a/configs/beagleboneai64_defconfig b/configs/beagleboneai64_defconfig
> new file mode 100644
> index 0000000000..593c41625c
> --- /dev/null
> +++ b/configs/beagleboneai64_defconfig
> @@ -0,0 +1,50 @@
> +BR2_aarch64=y
> +BR2_cortex_a72=y
> +BR2_GLOBAL_PATCH_DIR="board/beagleboard/beagleboneai64/patches"
> +BR2_DOWNLOAD_FORCE_CHECK_HASHES=y
Aren't we supposed to have BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_XYZ=y
somewhere?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-05-06 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 8:39 [Buildroot] [PATCH v2] configs/beagleboneai64_defconfig: new defconfig Romain Naour
2024-05-06 19:51 ` Thomas Petazzoni via buildroot [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=20240506215100.13296b7a@windsurf \
--to=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
--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.