From: Denys Dmytriyenko <denis@denix.org>
To: afd@ti.com
Cc: c-shilwant@ti.com, meta-ti@lists.yoctoproject.org,
Ryan Eatmon <reatmon@ti.com>
Subject: Re: [meta-ti][master/scarthgap][PATCH 1/3] trusted-firmware-a: Switch TFA to TI fork
Date: Tue, 4 Feb 2025 14:16:47 -0500 [thread overview]
Message-ID: <20250204191647.GJ21608@denix.org> (raw)
In-Reply-To: <11d39f7d-7b08-42e0-87a5-0b4380859706@ti.com>
On Tue, Feb 04, 2025 at 10:25:14AM -0600, Andrew Davis via lists.yoctoproject.org wrote:
> On 2/4/25 7:49 AM, Chirag Shilwant via lists.yoctoproject.org 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 PV & LIC_FILES_CHKSUM as well
>
> The license change isn't something we did as part of our fork ti-atf.
> Maybe you could split this into two to make that clear,
>
> * Update to upstream 2.12 + license fix
> * Patch that only deals with switching to ti-atf.
Andrew,
Any downside to switching from upstream tfa to ti-tfa?
Is the only change to support non-R5 platform and won't affect other K3
devices?
> >Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
> >---
> > .../trusted-firmware-a/trusted-firmware-a-ti.inc | 9 +++++----
> > 1 file changed, 5 insertions(+), 4 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 ebb13bbd..e4a9c49b 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,8 @@
> >-PV:k3 = "2.11+git"
> >-SRCREV_tfa:k3 = "58b25570c9ef91753b14c2103f45f4be9dddb696"
> >-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"
> >+PV:k3 = "2.12+git"
> >+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"
next prev parent reply other threads:[~2025-02-04 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 13:49 [meta-ti][master/scarthgap][PATCH 0/3] Add support for AM62L Chirag Shilwant
2025-02-04 13:49 ` [meta-ti][master/scarthgap][PATCH 1/3] trusted-firmware-a: Switch TFA to TI fork Chirag Shilwant
2025-02-04 16:25 ` Andrew Davis
2025-02-04 16:47 ` Ryan Eatmon
2025-02-04 19:16 ` Denys Dmytriyenko [this message]
2025-02-04 20:05 ` Andrew Davis
2025-02-05 9:46 ` Chirag Shilwant
2025-02-04 13:49 ` [meta-ti][master/scarthgap][PATCH 2/3] meta-ti-bsp: Add Support for AM62L Chirag Shilwant
2025-02-04 16:42 ` Andrew Davis
2025-02-04 16:46 ` Ryan Eatmon
2025-02-04 19:08 ` Denys Dmytriyenko
2025-02-04 16:45 ` Ryan Eatmon
2025-02-04 13:49 ` [meta-ti][master/scarthgap][PATCH 3/3] 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=20250204191647.GJ21608@denix.org \
--to=denis@denix.org \
--cc=afd@ti.com \
--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.