| Message ID | 20220608171418.576-1-afd@ti.com |
|---|---|
| State | Rejected |
| Headers | show |
| Series | [meta-ti,dunfell,v2,1/2] trusted-firmware-a: Update to latest upstream master | expand |
What is the difference between v1 and v2 of these patches? On Wed, Jun 08, 2022 at 12:14:17PM -0500, Andrew Davis via lists.yoctoproject.org wrote: > For TF-A we work against upstream first, our fork has only been > used in the rare cases we need to ship a feature before we can > get it upstream. This is not currently the case so lets switch > to upstream repo until there is a need for our fork. > > Signed-off-by: Andrew Davis <afd@ti.com> > --- > recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend > index 68bfa899..207f3dac 100644 > --- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend > +++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend > @@ -1,8 +1,6 @@ > PV_k3 = "2.6" > LIC_FILES_CHKSUM_k3 = "file://license.rst;md5=1dd070c98a281d18d9eefd938729b031" > -BRANCH_k3 = "ti-atf" > -SRC_URI_k3 = "git://git.ti.com/atf/arm-trusted-firmware.git;branch=${BRANCH};name=tfa" > -SRCREV_tfa_k3 = "6541aa24f834daa80da701e0054dfe3a16cda0ce" > +SRCREV_tfa_k3 = "453abc80b2eacbf2816c838e47e40f063227d934" > COMPATIBLE_MACHINE_k3 = "k3" > TFA_BUILD_TARGET_k3 = "all" > TFA_INSTALL_TARGET_k3 = "bl31" > -- > 2.36.1 >
He sent this one as a mistake. He is going to send a V3 that moves the optee-[client|test|examples] out of meta-arago and into meta-ti so that all of the optee stuff is in one place. On 6/8/2022 14:20, Denys Dmytriyenko wrote: > What is the difference between v1 and v2 of these patches? > > > On Wed, Jun 08, 2022 at 12:14:17PM -0500, Andrew Davis via lists.yoctoproject.org wrote: >> For TF-A we work against upstream first, our fork has only been >> used in the rare cases we need to ship a feature before we can >> get it upstream. This is not currently the case so lets switch >> to upstream repo until there is a need for our fork. >> >> Signed-off-by: Andrew Davis <afd@ti.com> >> --- >> recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend | 4 +--- >> 1 file changed, 1 insertion(+), 3 deletions(-) >> >> diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend >> index 68bfa899..207f3dac 100644 >> --- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend >> +++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend >> @@ -1,8 +1,6 @@ >> PV_k3 = "2.6" >> LIC_FILES_CHKSUM_k3 = "file://license.rst;md5=1dd070c98a281d18d9eefd938729b031" >> -BRANCH_k3 = "ti-atf" >> -SRC_URI_k3 = "git://git.ti.com/atf/arm-trusted-firmware.git;branch=${BRANCH};name=tfa" >> -SRCREV_tfa_k3 = "6541aa24f834daa80da701e0054dfe3a16cda0ce" >> +SRCREV_tfa_k3 = "453abc80b2eacbf2816c838e47e40f063227d934" >> COMPATIBLE_MACHINE_k3 = "k3" >> TFA_BUILD_TARGET_k3 = "all" >> TFA_INSTALL_TARGET_k3 = "bl31" >> -- >> 2.36.1 >>
On Wed, Jun 08, 2022 at 02:21:40PM -0500, Ryan Eatmon wrote: > > He sent this one as a mistake. He is going to send a V3 that moves > the optee-[client|test|examples] out of meta-arago and into meta-ti > so that all of the optee stuff is in one place. What is the pressing need to update optee in dunfell to the very latest? > On 6/8/2022 14:20, Denys Dmytriyenko wrote: > >What is the difference between v1 and v2 of these patches? > > > > > >On Wed, Jun 08, 2022 at 12:14:17PM -0500, Andrew Davis via lists.yoctoproject.org wrote: > >>For TF-A we work against upstream first, our fork has only been > >>used in the rare cases we need to ship a feature before we can > >>get it upstream. This is not currently the case so lets switch > >>to upstream repo until there is a need for our fork. > >> > >>Signed-off-by: Andrew Davis <afd@ti.com> > >>--- > >> recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend | 4 +--- > >> 1 file changed, 1 insertion(+), 3 deletions(-) > >> > >>diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend > >>index 68bfa899..207f3dac 100644 > >>--- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend > >>+++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend > >>@@ -1,8 +1,6 @@ > >> PV_k3 = "2.6" > >> LIC_FILES_CHKSUM_k3 = "file://license.rst;md5=1dd070c98a281d18d9eefd938729b031" > >>-BRANCH_k3 = "ti-atf" > >>-SRC_URI_k3 = "git://git.ti.com/atf/arm-trusted-firmware.git;branch=${BRANCH};name=tfa" > >>-SRCREV_tfa_k3 = "6541aa24f834daa80da701e0054dfe3a16cda0ce" > >>+SRCREV_tfa_k3 = "453abc80b2eacbf2816c838e47e40f063227d934" > >> COMPATIBLE_MACHINE_k3 = "k3" > >> TFA_BUILD_TARGET_k3 = "all" > >> TFA_INSTALL_TARGET_k3 = "bl31" > >>-- > >>2.36.1 > >>
On 6/8/22 2:43 PM, Denys Dmytriyenko wrote: > On Wed, Jun 08, 2022 at 02:21:40PM -0500, Ryan Eatmon wrote: >> >> He sent this one as a mistake. He is going to send a V3 that moves >> the optee-[client|test|examples] out of meta-arago and into meta-ti >> so that all of the optee stuff is in one place. > > What is the pressing need to update optee in dunfell to the very latest? > It pulls in new features for our plats like HUK and AM64x/AM62x support. Andrew > >> On 6/8/2022 14:20, Denys Dmytriyenko wrote: >>> What is the difference between v1 and v2 of these patches? >>> >>> >>> On Wed, Jun 08, 2022 at 12:14:17PM -0500, Andrew Davis via lists.yoctoproject.org wrote: >>>> For TF-A we work against upstream first, our fork has only been >>>> used in the rare cases we need to ship a feature before we can >>>> get it upstream. This is not currently the case so lets switch >>>> to upstream repo until there is a need for our fork. >>>> >>>> Signed-off-by: Andrew Davis <afd@ti.com> >>>> --- >>>> recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend | 4 +--- >>>> 1 file changed, 1 insertion(+), 3 deletions(-) >>>> >>>> diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend >>>> index 68bfa899..207f3dac 100644 >>>> --- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend >>>> +++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend >>>> @@ -1,8 +1,6 @@ >>>> PV_k3 = "2.6" >>>> LIC_FILES_CHKSUM_k3 = "file://license.rst;md5=1dd070c98a281d18d9eefd938729b031" >>>> -BRANCH_k3 = "ti-atf" >>>> -SRC_URI_k3 = "git://git.ti.com/atf/arm-trusted-firmware.git;branch=${BRANCH};name=tfa" >>>> -SRCREV_tfa_k3 = "6541aa24f834daa80da701e0054dfe3a16cda0ce" >>>> +SRCREV_tfa_k3 = "453abc80b2eacbf2816c838e47e40f063227d934" >>>> COMPATIBLE_MACHINE_k3 = "k3" >>>> TFA_BUILD_TARGET_k3 = "all" >>>> TFA_INSTALL_TARGET_k3 = "bl31" >>>> -- >>>> 2.36.1 >>>>
diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend index 68bfa899..207f3dac 100644 --- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend +++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend @@ -1,8 +1,6 @@ PV_k3 = "2.6" LIC_FILES_CHKSUM_k3 = "file://license.rst;md5=1dd070c98a281d18d9eefd938729b031" -BRANCH_k3 = "ti-atf" -SRC_URI_k3 = "git://git.ti.com/atf/arm-trusted-firmware.git;branch=${BRANCH};name=tfa" -SRCREV_tfa_k3 = "6541aa24f834daa80da701e0054dfe3a16cda0ce" +SRCREV_tfa_k3 = "453abc80b2eacbf2816c838e47e40f063227d934" COMPATIBLE_MACHINE_k3 = "k3" TFA_BUILD_TARGET_k3 = "all" TFA_INSTALL_TARGET_k3 = "bl31"
For TF-A we work against upstream first, our fork has only been used in the rare cases we need to ship a feature before we can get it upstream. This is not currently the case so lets switch to upstream repo until there is a need for our fork. Signed-off-by: Andrew Davis <afd@ti.com> --- recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)