From: Dinh Nguyen via buildroot <buildroot@buildroot.org>
To: ju.o@free.fr
Cc: dinguyen@kernel.org, thomas.petazzoni@bootlin.com,
buildroot@buildroot.org
Subject: [Buildroot] [PATCHv2 2/2] configs/altera: enable BR2_DOWNLOAD_FORCE_CHECK_HASHES
Date: Mon, 9 Nov 2026 14:51:04 -0600 [thread overview]
Message-ID: <20261109205104.2140273-2-dinguyen@kernel.org> (raw)
In-Reply-To: <20261109205104.2140273-1-dinguyen@kernel.org>
Enable BR2_DOWNLOAD_FORCE_CHECK_HASHES, add custom hashes in
board/altera/agilex5/patches directory.
Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
---
.../patches/arm-trusted-firmware/arm-trusted-firmware.hash | 2 ++
board/altera/agilex5/patches/linux/linux.hash | 2 ++
board/altera/agilex5/patches/uboot/uboot.hash | 2 ++
configs/socfpga_agilex5_altera_defconfig | 2 ++
4 files changed, 8 insertions(+)
create mode 100644 board/altera/agilex5/patches/arm-trusted-firmware/arm-trusted-firmware.hash
create mode 100644 board/altera/agilex5/patches/linux/linux.hash
create mode 100644 board/altera/agilex5/patches/uboot/uboot.hash
diff --git a/board/altera/agilex5/patches/arm-trusted-firmware/arm-trusted-firmware.hash b/board/altera/agilex5/patches/arm-trusted-firmware/arm-trusted-firmware.hash
new file mode 100644
index 0000000000..5a935a0d16
--- /dev/null
+++ b/board/altera/agilex5/patches/arm-trusted-firmware/arm-trusted-firmware.hash
@@ -0,0 +1,2 @@
+# Locally calculated
+sha256 59bed1328131f1eb1ee10f16c94d8f0bbf5600d7573d42d0cf987b8edffe2f6a arm-trusted-firmware-QPDS26.1.1_REL_GSRD_PR-git4.tar.gz
diff --git a/board/altera/agilex5/patches/linux/linux.hash b/board/altera/agilex5/patches/linux/linux.hash
new file mode 100644
index 0000000000..d322ac26c7
--- /dev/null
+++ b/board/altera/agilex5/patches/linux/linux.hash
@@ -0,0 +1,2 @@
+# Locally calculated
+sha256 d8328683db0a6b43a96c18d7149b98a11138909ea50f2fa411339f93eb492571 linux-QPDS26.1.1_REL_GSRD_PR-git4.tar.gz
diff --git a/board/altera/agilex5/patches/uboot/uboot.hash b/board/altera/agilex5/patches/uboot/uboot.hash
new file mode 100644
index 0000000000..51906e1d73
--- /dev/null
+++ b/board/altera/agilex5/patches/uboot/uboot.hash
@@ -0,0 +1,2 @@
+# Locally calculated
+sha256 a78bf187fde344297bea7d986f05996dfba94ea11d2d4dc706a78bcae543e175 uboot-QPDS26.1.1_REL_GSRD_PR-git4.tar.gz
diff --git a/configs/socfpga_agilex5_altera_defconfig b/configs/socfpga_agilex5_altera_defconfig
index a0888bdd25..f989403c69 100644
--- a/configs/socfpga_agilex5_altera_defconfig
+++ b/configs/socfpga_agilex5_altera_defconfig
@@ -2,6 +2,8 @@ BR2_cortex_a55=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_AARCH64_GLIBC_STABLE=y
+BR2_GLOBAL_PATCH_DIR="board/altera/agilex5/patches"
+BR2_DOWNLOAD_FORCE_CHECK_HASHES=y
BR2_TARGET_GENERIC_HOSTNAME="agilex5"
BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
BR2_SYSTEM_DHCP="eth0"
--
2.42.0.411.g813d9a9188
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-11-09 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 20:51 [Buildroot] [PATCHv2 1/2] configs/socfpga_agilex5_altera: new defconfig Dinh Nguyen via buildroot
2026-11-09 20:51 ` Dinh Nguyen via buildroot [this message]
2026-11-10 12:18 ` Julien Olivain 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=20261109205104.2140273-2-dinguyen@kernel.org \
--to=buildroot@buildroot.org \
--cc=dinguyen@kernel.org \
--cc=ju.o@free.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.