From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Praneeth Bajjuri <praneeth@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master/scarthgap][PATCH] trusted-firmware-a: Move back to tfa upstream except for am62lxx
Date: Tue, 1 Jul 2025 12:13:13 -0400 [thread overview]
Message-ID: <20250701161313.GT18383@denix.org> (raw)
In-Reply-To: <20250701155042.5529-1-reatmon@ti.com>
On Tue, Jul 01, 2025 at 10:50:42AM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
> This moves all of the platforms back to the main TFA repository, but
> still points to the TI fork for the am62lxx platform while we continue
> to work on upstreaming the needed patches.
When I stumbled upon this change being tested in master-wip last wekk, I
noticed it was failing due to LIC_FILES_CHKSUM - I see you fixed it here.
Still, as previously discussed, should there be a brief comment explaining
why the hash is different?
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> .../trusted-firmware-a-ti.inc | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc b/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc
> index c17ac9de..ec52d09c 100644
> --- a/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc
> +++ b/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc
> @@ -1,12 +1,19 @@
> # NOTE: This .inc file with customizations only gets included for K3 platforms
>
> -PV = "2.12+git"
> -SRCREV_tfa = "2ab59f45ad0a5d95b5cb339c0f64686954377050"
> -SRC_URI_TRUSTED_FIRMWARE_A = "git://github.com/TexasInstruments/arm-trusted-firmware.git;protocol=https"
> -SRCBRANCH = "ti-master"
> +PV = "2.13+git"
> +
> +LIC_FILES_CHKSUM = "file://docs/license.rst;md5=6ed7bace7b0bc63021c6eba7b524039e"
> +SRCREV_tfa = "d90bb650fe4cb3784f62214ab5829f4051c38d0a"
> +SRC_URI_TRUSTED_FIRMWARE_A = "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=https"
> +SRCBRANCH = "master"
> +
> +LIC_FILES_CHKSUM:am62lxx = "file://docs/license.rst;md5=1118e32884721c0be33267bd7ae11130"
> +SRCREV_tfa:am62lxx = "2ab59f45ad0a5d95b5cb339c0f64686954377050"
> +SRC_URI_TRUSTED_FIRMWARE_A:am62lxx = "git://github.com/TexasInstruments/arm-trusted-firmware.git;protocol=https"
> +SRCBRANCH:am62lxx = "ti-master"
> +
> SRC_URI = "${SRC_URI_TRUSTED_FIRMWARE_A};name=tfa;branch=${SRCBRANCH}"
>
> -LIC_FILES_CHKSUM = "file://docs/license.rst;md5=1118e32884721c0be33267bd7ae11130"
> COMPATIBLE_MACHINE = "k3"
>
> TFA_BUILD_TARGET = "all"
> --
> 2.17.1
next prev parent reply other threads:[~2025-07-01 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 15:50 [meta-ti][master/scarthgap][PATCH] trusted-firmware-a: Move back to tfa upstream except for am62lxx Ryan Eatmon
2025-07-01 16:13 ` Denys Dmytriyenko [this message]
2025-07-01 17:07 ` Ryan Eatmon
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=20250701161313.GT18383@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.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.