From: Denys Dmytriyenko <denis@denix.org>
To: Chirag Shilwant <c-shilwant@ti.com>
Cc: meta-ti@lists.yoctoproject.org, Ryan Eatmon <reatmon@ti.com>
Subject: Re: [meta-ti][master/scarthgap][PATCH v2 3/5] trusted-firmware-a: Switch TFA to TI fork
Date: Wed, 5 Feb 2025 12:17:01 -0500 [thread overview]
Message-ID: <20250205171701.GL21608@denix.org> (raw)
In-Reply-To: <20250205111211.1847450-4-c-shilwant@ti.com>
On Wed, Feb 05, 2025 at 04:42:09PM +0530, Chirag Shilwant wrote:
> - While TFA patches for K3-based AM62L platform are under
> review upstream, temporarily switch to TI's GitHub fork
> for all K3 platforms to prevent disruptions and ensure timely bringup
>
> - Also update the LIC_FILES_CHKSUM since the license file changed between
> upstream TFA v2.12 [1] & the SRCREV in this commit [2][3]
>
> [1]: https://github.com/ARM-software/arm-trusted-firmware/blob/v2.12/docs/license.rst
>
> [2]: https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/license.rst
>
> [3]: https://github.com/TexasInstruments/arm-trusted-firmware/blob/ti-master/docs/license.rst
Sorry for the late reply, but master (styhead+) now requires License-Update:
tag for such cases:
https://docs.yoctoproject.org/dev/contributor-guide/recipe-style-guide.html#license-updates
> Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
> ---
> .../trusted-firmware-a/trusted-firmware-a-ti.inc | 6 +++---
> 1 file changed, 3 insertions(+), 3 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 df3cea23..c628eb15 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,7 +1,7 @@
> PV:k3 = "2.12+git"
> -SRCREV_tfa:k3 = "4ec2948fe3f65dba2f19e691e702f7de2949179c"
> -LIC_FILES_CHKSUM:k3 = "file://docs/license.rst;md5=83b7626b8c7a37263c6a58af8d19bee1"
> -SRC_URI:k3 = "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=https;name=tfa;branch=master"
> +SRCREV_tfa:k3 = "5227171c079d0c7d22a6d37b5cec079c8c5bb4b1"
> +LIC_FILES_CHKSUM:k3 = "file://docs/license.rst;md5=1118e32884721c0be33267bd7ae11130"
> +SRC_URI:k3 = "git://github.com/TexasInstruments/arm-trusted-firmware.git;protocol=https;name=tfa;branch=ti-master"
> COMPATIBLE_MACHINE:k3 = "k3"
> TFA_BUILD_TARGET:k3 = "all"
> TFA_INSTALL_TARGET:k3 = "bl31"
> --
> 2.34.1
next prev parent reply other threads:[~2025-02-05 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 11:12 [meta-ti][master/scarthgap][PATCH v2 0/5] Upgrade TFA, OPTEE-OS & enable AM62L support Chirag Shilwant
2025-02-05 11:12 ` [meta-ti][master/scarthgap][PATCH v2 1/5] recipes-security: optee: Update to v4.5.0+ Chirag Shilwant
2025-02-05 11:12 ` [meta-ti][master/scarthgap][PATCH v2 2/5] trusted-firmware-a: Update to v2.12 release tag Chirag Shilwant
2025-02-05 11:12 ` [meta-ti][master/scarthgap][PATCH v2 3/5] trusted-firmware-a: Switch TFA to TI fork Chirag Shilwant
2025-02-05 14:53 ` Andrew Davis
2025-02-05 17:17 ` Denys Dmytriyenko [this message]
2025-02-05 11:12 ` [meta-ti][master/scarthgap][PATCH v2 4/5] meta-ti-bsp: Add Support for AM62L Chirag Shilwant
2025-02-05 11:12 ` [meta-ti][master/scarthgap][PATCH v2 5/5] conf: machine: am62lxx-evm: Add logic to generate UBI filesystem images Chirag Shilwant
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=20250205171701.GL21608@denix.org \
--to=denis@denix.org \
--cc=c-shilwant@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--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.