|
Re: [dunfell/master PATCH] conf/machine: fix OPTEEMACHINE name for J721e
Denys Dmytriyenko
ACK
toggle quoted messageShow quoted text
On Thu, Mar 25, 2021 at 10:41:10PM -0500, praneeth via lists.yoctoproject.org wrote:
From: Praneeth Bajjuri <praneeth@...>
|
|
|
|
Re: [dunfell/master PATCH v2] trusted-firmware-a: am64xx: fix target board name
Denys Dmytriyenko
toggle quoted messageShow quoted text
On Thu, Mar 25, 2021 at 10:39:45PM -0500, praneeth via lists.yoctoproject.org wrote:
From: Praneeth Bajjuri <praneeth@...>
|
|
|
|
Re: [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
Shiju Sivasankaran
<1>
toggle quoted messageShow quoted text
Yes, All the FW are hosted on same repo processor-sdk/coresdk_rtos_releases. But its only hosting purpose, these FW are builds from PDK (all device except AM64x) and mcu-plus-sdk (AM64x alone) Similarly metadata.inc will be used to get the version/urls details for all devices except AM64x and mcusdk_metadata.inc is used for AM64x. Same metadata.inc for mcu-plus-sdk is a big risk as any PDK build of AM64x can override this. <2> coresdk_rtos_releases has 2 branches - master & next. All metadata files and tags are applied on next and during RC period coreSDK team merge next to master. At the same time next-branch also carry the metadata files from daily build as well. During this merge they make sure only release builds of all devices on that tag/commit, as only release build points the FW url from external location. If any daily build of any device happens in between the tagging and as daily build has TI internal url for FW will spoil the purpose. AM65x, J7 & J7200 builds of PSDK should have happen one after another without any daily builds in between, this can be controlled as all these are built from same codebase of PDK. As AM64x builds from mcu-plus-sdk, a different codebase, code-freeze and RC timing rarely match. Rebuild of all devices and recipe updates will arises if builds from both repo doesn't happen at same time. Separate TI_RTOS_METADATA_SRCREV_am64xx is added to avoid this syncing of builds from two different repos. <3> I will correct the typo in the commit-comment
-----Original Message-----
From: Bajjuri, Praneeth Sent: Friday, March 26, 2021 3:04 AM To: Sivasankaran, Shiju <shiju@...>; meta-ti@... Subject: Re: [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware On 3/25/2021 1:30 AM, Shiju Sivasankaran wrote: updated rtos firmwareBut all of the fws are coming from the same repo processor-sdk/coresdk_rtos_releases where metadata.inc is updated on master with right tag and public urls inside the metadata_*.inc isnt it ? a separate TI_RTOS_METADATA_SRCREV_am64xx for pining am64x fw fromtypo s/macu? avoids syncing of builds from two different repos. TI_RTOS_METADATA_SRCREV is pointing to master branch commitsha where the given tag is present. I dont see why we have to seperate this macro for each device seperately. Add your signoff by. ---Why this? Why TI_RTOS_METADATA_SRCREV ?= "051de801b539f4acc6e7630684f9993e34332dde" willnot work for all devices? TI_RTOS_METADATA_BRANCH ?= "master"
|
|
|
|
[dunfell/master PATCH] conf/machine: fix OPTEEMACHINE name for J721e
praneeth
From: Praneeth Bajjuri <praneeth@...>
OPTEEMACHINE name as defined in the optee_os project [1] for j721e is k3-j721e. This patch fixes the name to correct target. [1]: https://github.com/OP-TEE/optee_os/commit/87613cf9520db2e65bc8367d3e13c4217c13bdad Signed-off-by: Praneeth Bajjuri <praneeth@...> --- conf/machine/include/j7.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/machine/include/j7.inc b/conf/machine/include/j7.inc index 7d326f4a..c187f299 100644 --- a/conf/machine/include/j7.inc +++ b/conf/machine/include/j7.inc @@ -1,7 +1,7 @@ require conf/machine/include/k3.inc SOC_FAMILY_append = ":j7" -OPTEEMACHINE = "k3-j7" +OPTEEMACHINE = "k3-j721e" OPTEEOUTPUTMACHINE = "k3" # Set the list of device targets for ti-pdk class recipes -- 2.17.1
|
|
|
|
[dunfell/master PATCH v2] trusted-firmware-a: am64xx: fix target board name
praneeth
From: Praneeth Bajjuri <praneeth@...>
am64xx is the first generation of k3 device that uses a updated board defintion as "lite" platform.[1] This patch fixes the TFA board to appropriate target as "lite" instead of "generic" for am64xx. [1]: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=84af89563e1b17def844d3672bc601ae51f0257f Signed-off-by: Praneeth Bajjuri <praneeth@...> --- conf/machine/include/k3.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/machine/include/k3.inc b/conf/machine/include/k3.inc index c727d724..a96ebb76 100644 --- a/conf/machine/include/k3.inc +++ b/conf/machine/include/k3.inc @@ -28,6 +28,7 @@ EXTRA_IMAGEDEPENDS += "virtual/bootloader" TFA_PLATFORM = "k3" TFA_BOARD = "generic" +TFA_BOARD_am64xx = "lite" MACHINE_GUI_CLASS = "smallscreen" -- 2.17.1
|
|
|
|
[dunfell/master PATCH] trusted-firmware-a: am64xx:
praneeth
From: Praneeth Bajjuri <praneeth@...>
am64xx is the first generation of k3 device that uses a updated board defintion as "lite" platform.[1] This patch fixes the TFA board to appropriate target as "lite" instead of "generic" for am64xx. [1]: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=84af89563e1b17def844d3672bc601ae51f0257f Signed-off-by: Praneeth Bajjuri <praneeth@...> --- conf/machine/include/k3.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/machine/include/k3.inc b/conf/machine/include/k3.inc index c727d724..a96ebb76 100644 --- a/conf/machine/include/k3.inc +++ b/conf/machine/include/k3.inc @@ -28,6 +28,7 @@ EXTRA_IMAGEDEPENDS += "virtual/bootloader" TFA_PLATFORM = "k3" TFA_BOARD = "generic" +TFA_BOARD_am64xx = "lite" MACHINE_GUI_CLASS = "smallscreen" -- 2.17.1
|
|
|
|
Re: [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
praneeth
On 3/25/2021 1:30 AM, Shiju Sivasankaran wrote:
updated rtos firmwareBut all of the fws are coming from the same repo processor-sdk/coresdk_rtos_releases where metadata.inc is updated on master with right tag and public urls inside the metadata_*.inc isnt it ? a separate TI_RTOS_METADATA_SRCREV_am64xx for pining am64x fwtypo s/macu? avoids syncing of builds from two different repos. TI_RTOS_METADATA_SRCREV is pointing to master branch commitsha where the given tag is present. I dont see why we have to seperate this macro for each device seperately. Add your signoff by. ---Why this? Why TI_RTOS_METADATA_SRCREV ?= "051de801b539f4acc6e7630684f9993e34332dde" willnot work for all devices? TI_RTOS_METADATA_BRANCH ?= "master"
|
|
|
|
[dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
Shiju Sivasankaran
updated rtos firmware
am64xx: 07.03.00.13 rtos fw of am64x build and upload from mcu-plus-sdk repo. rtos fw of am65x, j7 and j7200 build and upload from pdk repo. a separate TI_RTOS_METADATA_SRCREV_am64xx for pining am64x fw from macu-plus-sdk avoids syncing of builds from two different repos. --- recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 6 +++--- recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb | 1 + 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb index e85948b2..fe020aa3 100644 --- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb +++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb @@ -23,8 +23,8 @@ DEFAULT_RTOS_FAMILY = "jacinto" DEFAULT_RTOS_VERSION = "07_03_00_21" DEFAULT_RTOS_VERSION_DOT = "07.03.00.21" -DEFAULT_RTOS_VERSION_am64xx = "07_03_00_03" -DEFAULT_RTOS_VERSION_DOT_am64xx = "07.03.00.03" +DEFAULT_RTOS_VERSION_am64xx = "07_03_00_13" +DEFAULT_RTOS_VERSION_DOT_am64xx = "07.03.00.13" DEFAULT_RTOS_VERSION_am65xx = "07_03_00_22" DEFAULT_RTOS_VERSION_DOT_am65xx = "07.03.00.22" @@ -51,7 +51,7 @@ DEFAULT_FIRMWARE_SHA256SUM = "unknown" DEFAULT_FIRMWARE_SHA256SUM_j7 = "fc7805ed3d6c1801efb2b85ac9af99a8657aa3a7a9327bc16a1163d566f11c2c" DEFAULT_FIRMWARE_SHA256SUM_j7200-evm = "71f282ba6768ad3b603a17d30851cc621986c88311c174960a50196bfc79f85c" DEFAULT_FIRMWARE_SHA256SUM_am65xx = "61e0be08bea8ab1055645bd96504a6a29c70318c5b277237dee9981cd94d7f79" -DEFAULT_FIRMWARE_SHA256SUM_am64xx = "bc2d3d603ad30006ea3fefa3e777c26c19b95ee6d6f5a630259009f2f5a4996b" +DEFAULT_FIRMWARE_SHA256SUM_am64xx = "0c43cea6ccaf45b3d7c48996f1c561e814a6e409a330da5d45877c82ce7a299a" # Use weak assignment for CORESDK_RTOS_* variables to use defaults if not yet set CORESDK_RTOS_FAMILY ?= "${DEFAULT_RTOS_FAMILY}" diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb index 83e0e901..f052c627 100644 --- a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb +++ b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb @@ -19,6 +19,7 @@ PLAT_SFX_am64xx = "/am64x" TI_RTOS_METADATA_URI ?= "git://git.ti.com/processor-sdk/coresdk_rtos_releases.git" TI_RTOS_METADATA_PROTOCOL ?= "git" TI_RTOS_METADATA_SRCREV ?= "3cda650c9e22eb4fd4eb5797ad998991a6124243" +TI_RTOS_METADATA_SRCREV_am64xx ?= "051de801b539f4acc6e7630684f9993e34332dde" TI_RTOS_METADATA_BRANCH ?= "master" TI_RTOS_METADATA_DIR ?= "${PLAT_SFX}" TI_RTOS_METADATA_FILE ?= "${S}${TI_RTOS_METADATA_DIR}/metadata.inc" -- 2.17.1
|
|
|
|
[dunfell/master][PATCH] ti-img-rogue-umlibs: Update to pick rpath fixes
Gowtham Tammana <g-tammana@...>
Update srcrev to pick the rpath warning fixes.
Signed-off-by: Gowtham Tammana <g-tammana@...> --- recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb b/recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb index d8fae3dd..dafb9dd8 100644 --- a/recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb +++ b/recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb @@ -10,13 +10,13 @@ REQUIRED_MACHINE_FEATURES = "gpu" PACKAGE_ARCH = "${MACHINE_ARCH}" COMPATIBLE_MACHINE = "j7" -PR = "r1" +PR = "r2" BRANCH = "linuxws/dunfell/k5.4/${PV}" SRC_URI = "git://git.ti.com/graphics/ti-img-rogue-umlibs.git;branch=${BRANCH}" -SRCREV = "3c4cabc8df10a066569e5f959cbbd4c0ce9961cd" +SRCREV = "5ef38353c38d921a65ea6df75c7b6ce710b66034" PVR_SOC ?= "j721e_linux" PVR_BUILD ?= "release" -- 2.31.0
|
|
|
|
Re: [dunfell/master] [PATCH] linux-ti-mainline: Add gmp-native as a kernel dependency
Denys Dmytriyenko
On Tue, Mar 23, 2021 at 03:57:45PM -0500, Nishanth Menon wrote:
From: Dan Murphy <dmurphy@...>This is in-line with oe-core as added since 5.8 in: d3590f16d9c1b56813114113b74f7b6f01e6b0ba kernel-yocto/5.8: add gmp-native dependency Signed-off-by: Dan Murphy <dmurphy@...>Reviewed-by: Denys Dmytriyenko <denys@...> ---
|
|
|
|
[dunfell/master][PATCH] linux-ti-mainline: Set the branch for the ti-upstream-tools repo
From: Dan Murphy <dmurphy@...>
ti-upstream-tools[1] repository carries the overlays and defconfig fragments that we don't wish to overload upstream kernel community with. The reason for that being these are constantly on churn as our test coverage increases etc. Currently we reuse the "BRANCH" variable to also matchup with kernel and ti-upstream-tools repositories as well. This can tend to be a little painful if we decide to start testing various kernel configurations - RT etc.. So, lets just split out the TOOLS_BRANCH separated from the branch we use for kernel. Even though the branch remains the exact same at this point. [1] https://git.ti.com/cgit/ti-linux-kernel/ti-upstream-tools/ Signed-off-by: Dan Murphy <dmurphy@...> Signed-off-by: Nishanth Menon <nm@...> --- recipes-kernel/linux/linux-ti-mainline_git.bb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/recipes-kernel/linux/linux-ti-mainline_git.bb b/recipes-kernel/linux/linux-ti-mainline_git.bb index 41e852ba0e88..19c091e81e79 100644 --- a/recipes-kernel/linux/linux-ti-mainline_git.bb +++ b/recipes-kernel/linux/linux-ti-mainline_git.bb @@ -16,6 +16,7 @@ KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT}" S = "${WORKDIR}/git" BRANCH = "master" +TOOLS_BRANCH = "master" # 5.11 Mainline version SRCREV = "f40ddce88593482919761f74910f42f4b84c004b" @@ -29,7 +30,7 @@ KERNEL_GIT_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.g KERNEL_GIT_PROTOCOL = "git" SRC_URI += " \ ${KERNEL_GIT_URI};protocol=${KERNEL_GIT_PROTOCOL};branch=${BRANCH};name=linux \ - git://git.ti.com/ti-linux-kernel/ti-upstream-tools.git;protocol=${KERNEL_GIT_PROTOCOL};name=ti-upstream-tools;destsuffix=ti-upstream-tools \ + git://git.ti.com/ti-linux-kernel/ti-upstream-tools.git;branch=${TOOLS_BRANCH};protocol=${KERNEL_GIT_PROTOCOL};name=ti-upstream-tools;destsuffix=ti-upstream-tools \ file://defconfig \ " -- 2.31.0
|
|
|
|
[dunfell/master] [PATCH] linux-ti-mainline: Add gmp-native as a kernel dependency
From: Dan Murphy <dmurphy@...>
Add GNU Multiple Precision Arithmetic Library as a dependency for mainline linux builds. These are necesary for kernel to handle gcc plugins for builtins.h Signed-off-by: Dan Murphy <dmurphy@...> Signed-off-by: Nishanth Menon <nm@...> --- recipes-kernel/linux/linux-ti-mainline_git.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recipes-kernel/linux/linux-ti-mainline_git.bb b/recipes-kernel/linux/linux-ti-mainline_git.bb index ed7607046186..41e852ba0e88 100644 --- a/recipes-kernel/linux/linux-ti-mainline_git.bb +++ b/recipes-kernel/linux/linux-ti-mainline_git.bb @@ -9,6 +9,8 @@ DEFCONFIG_BUILDER = "${WORKDIR}/ti-upstream-tools/config/defconfig_builder.sh" require recipes-kernel/linux/setup-defconfig.inc require recipes-kernel/linux/kernel-rdepends.inc +DEPENDS += "gmp-native" + KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT}" S = "${WORKDIR}/git" -- 2.31.0
|
|
|
|
[dunfell/master][PATCH v3] ti-sci-fw: Update J7200/AM64 deploy to install ti-sci-fw
Weaver, Lucas
From: Lucas Weaver <l-weaver@...>
The J7200/AM64 ti-sci-fw needs to be installed in the deploy directory so that it can be packaged in Processor SDK bundle This is required because the ti-sci-fw is needed in the installer prebuilt-images in order to build the combined boot image for J7200/AM64 Signed-off-by: Lucas Weaver <l-weaver@...> --- recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb index e7580a57..e6fa460c 100644 --- a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb +++ b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb @@ -99,6 +99,7 @@ do_deploy_j7200-evm-k3r5() { install -m 644 ${WORKDIR}/imggen/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE} ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_SYMLINK} ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_BINARY} + install -m 644 ${SYSFW_TISCI} ${DEPLOYDIR}/ } do_install_am64xx-evm-k3r5() { @@ -113,6 +114,7 @@ do_deploy_am64xx-evm-k3r5() { install -m 644 ${WORKDIR}/imggen/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE} ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_SYMLINK} ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_BINARY} + install -m 644 ${SYSFW_TISCI} ${DEPLOYDIR}/ } do_install_am64xx-sk-k3r5() { @@ -127,6 +129,7 @@ do_deploy_am64xx-sk-k3r5() { install -m 644 ${WORKDIR}/imggen/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE} ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_SYMLINK} ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_BINARY} + install -m 644 ${SYSFW_TISCI} ${DEPLOYDIR}/ } addtask deploy before do_build after do_compile -- 2.17.1
|
|
|
|
Re: [EXTERNAL] Re: [meta-ti][dunfell/master][PATCH v2] ti-sci-fw: Update J7200 deploy to install ti-sci-fw
Shiju Sivasankaran
Yes, combined boot is also targeted for AM64x.
Lucas, can you pls add this capability for am64xx-evm and am64xx-sk as well?
|
|
|
|
Re: [EXTERNAL] Re: [meta-ti][dunfell/master][PATCH v2] ti-sci-fw: Update J7200 deploy to install ti-sci-fw
Denys Dmytriyenko
On Mon, Mar 22, 2021 at 11:54:10AM -0500, Weaver, Lucas wrote:
Ah, you are right. I somehow misread those as appends and not complete overrides. In that case your change is correct. I just wonder if the same change is needed for am64x platforms. And that portion of the code needs some unification and cleanup... https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb#n97-- Regards, Denys Dmytriyenko <denis@...> PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964 Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
|
|
|
|
Re: [EXTERNAL] Re: [meta-ti][dunfell/master][PATCH v2] ti-sci-fw: Update J7200 deploy to install ti-sci-fw
Weaver, Lucas
On 3/22/2021 11:21 AM, Denys Dmytriyenko wrote:
On Mon, Mar 22, 2021 at 09:37:06PM +0530, l-weaver via lists.yoctoproject.org wrote:From my understanding, I thought that the do_deploy_j7200-evm-k3r5 shown below will overwrite the do_deploy task for the j7200-evm-k3r5 platform. This was seemingly confirmed when I tried to bundle the ti-sci-fw for J7200 in the Processor SDK bundle but this file was not found. After adding the change from this patch, the bundle step succeeded. Could you please clarify my understanding?From: Lucas Weaver <l-weaver@...>This is already done for all platforms: https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb#n97 do_deploy_j7200-evm-k3r5() { install -d ${DEPLOYDIR} install -m 644 ${WORKDIR}/imggen/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE} ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_SYMLINK} ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_BINARY} } }
|
|
|
|
Re: [dunfell/master][PATCH v2] ti-sci-fw: Update J7200 deploy to install ti-sci-fw
Denys Dmytriyenko
On Mon, Mar 22, 2021 at 09:37:06PM +0530, l-weaver via lists.yoctoproject.org wrote:
From: Lucas Weaver <l-weaver@...>This is already done for all platforms: https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb#n87 do_deploy () { ... install -m 644 ${SYSFW_TISCI} ${DEPLOYDIR}/ } }
|
|
|
|
[dunfell/master][PATCH v2] ti-sci-fw: Update J7200 deploy to install ti-sci-fw
Weaver, Lucas
From: Lucas Weaver <l-weaver@...>
The J7200 ti-sci-fw needs to be installed in the deploy directory so that it can be packaged in Processor SDK bundle This is required because the ti-sci-fw is needed in the installer prebuilt-images in order to build the combined boot image for J7200 Signed-off-by: Lucas Weaver <l-weaver@...> --- recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb index e7580a57..25fac359 100644 --- a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb +++ b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb @@ -99,6 +99,7 @@ do_deploy_j7200-evm-k3r5() { install -m 644 ${WORKDIR}/imggen/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE} ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_SYMLINK} ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_BINARY} + install -m 644 ${SYSFW_TISCI} ${DEPLOYDIR}/ } do_install_am64xx-evm-k3r5() { -- 2.17.1
|
|
|
|
Re: [master][PATCH] layer.conf: add hardknott to compatible release branches
Denys Dmytriyenko
On Fri, Mar 19, 2021 at 05:58:26PM -0500, Bajjuri, Praneeth wrote:
Thanks! On Fri, Mar 19, 2021 at 04:07:19PM -0400, Denys Dmytriyenko wrote:From: Denys Dmytriyenko <denys@...>
|
|
|
|
Re: [master][PATCH] layer.conf: add hardknott to compatible release branches
praneeth
On 3/19/2021 3:31 PM, Denys Dmytriyenko wrote:
Praneeth,sounds good. done . merged to master and dunfell the seperate patches. On Fri, Mar 19, 2021 at 04:07:19PM -0400, Denys Dmytriyenko wrote:From: Denys Dmytriyenko <denys@...>
|
|
|