From: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
buildroot@buildroot.org
Cc: Bartosz Bilas <b.bilas@grinn-global.com>,
Marleen Vos <marleen.vos@mind.be>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-amarula@amarulasolutions.com
Subject: Re: [Buildroot] [PATCH v4 2/2] configs/stm32mp1*_dk*: bump TF-A to 2.10, Linux to 6.12.22 and U-Boot to 2025.04
Date: Mon, 14 Apr 2025 20:16:49 +0200 [thread overview]
Message-ID: <86eaf5bd-23e6-40c3-82f2-adc1d6a7e85c@gmail.com> (raw)
In-Reply-To: <20250413164708.1943803-2-dario.binacchi@amarulasolutions.com>
Le 13/04/2025 à 18:47, Dario Binacchi a écrit :
> The patch bumps Arm Trusted Firmware (TF-A) to version 2.10 LTS for
>
> - stm32mp157a_dk1_defconfig
> - stm32mp157c_dk2_defconfig
>
> the Linux kernel to version 6.12.22 and U-Boot to version 2025.04 for
>
> - stm32mp135f_dk_defconfig
> - stm32mp157a_dk1_defconfig
> - stm32mp157c_dk2_defconfig
>
> The new version of U-Boot has added EFI Capsule support, which depends on
> GnuTLS, thus requiring the activation of BR2_TARGET_UBOOT_NEEDS_GNUTLS
> for stm32mp135f_dk_defconfig.
>
> Tested on STM32MP157C-DK2 Discovery Board.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
>
Hi Dario,
Reviewed-by: Raphaël Gallais-Pou <rgallaispou@gmail.com>
Best regards,
Raphaël
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-04-14 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-13 16:47 [Buildroot] [PATCH v4 1/2] configs/stm32mp135f_dk: fix optee hash Dario Binacchi
2025-04-13 16:47 ` [Buildroot] [PATCH v4 2/2] configs/stm32mp1*_dk*: bump TF-A to 2.10, Linux to 6.12.22 and U-Boot to 2025.04 Dario Binacchi
2025-04-14 18:16 ` Raphaël Gallais-Pou [this message]
2025-04-14 18:15 ` [Buildroot] [PATCH v4 1/2] configs/stm32mp135f_dk: fix optee hash Raphaël Gallais-Pou
2025-04-19 16:36 ` Thomas Petazzoni via buildroot
2025-05-02 10:43 ` Arnout Vandecappelle 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=86eaf5bd-23e6-40c3-82f2-adc1d6a7e85c@gmail.com \
--to=rgallaispou@gmail.com \
--cc=b.bilas@grinn-global.com \
--cc=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=marleen.vos@mind.be \
--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