aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2021-05-04conf: k2g-evm: Remove keystone-k2g-evm-lcd.dtb from 5.10Praneeth Bajjuri
Remove the non-existent dtb, as they are not currently present on ti-linux-5.10.y. - keystone-k2g-evm-lcd.dtb Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-05-04conf: am65xx-evm: Remove non-existent dtb* from 5.10Praneeth Bajjuri
Remove the non-existent dtb* , as they are not currently present on ti-linux-5.10.y. - ti/k3-am654-base-board-sr1.dtb - ti/k3-am654-gp.dtbo - ti/k3-am654-idk.dtbo - ti/k3-am654-idk-sr1.dtbo - ti/k3-am654-evm-hdmi.dtbo - ti/k3-am654-evm-oldi-lcd1evm.dtbo - ti/k3-am654-evm-tc358876.dtbo - ti/k3-am654-pcie-usb2.dtbo - ti/k3-am654-pcie-usb3.dtbo - ti/k3-am654-base-board-jailhouse.dtbo - ti/k3-am654-evm-prupwm.dtbo Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-05-04conf: j7200-evm: Remove jailhouse overlay from 5.10 kernelPraneeth Bajjuri
Remove jailhouse overlay as it is not currently available in ti-linux-5.10.y branch. Removing for now, and shall be added back once they are available in 5.10 kernel. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-05-04conf: j7-evm: Remove unavailable dtb/o from 5.10 kernelPraneeth Bajjuri
The following dtb/o are not currently available in ti-linux-5.10.y branch. Removing for now, and shall be added back once they are available in 5.10 kernel. - ti/k3-j721e-proc-board-tps65917.dtb - ti/k3-j721e-common-proc-board-infotainment.dtbo - ti/k3-j721e-pcie-backplane.dtbo - ti/k3-j721e-common-proc-board-jailhouse.dtbo Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-05-04linux-ti-staging: Update 5.10 kernel to 5.10.21Praneeth Bajjuri
Update linux 5.10 to 5.10.21 stable. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-05-04Revert "linux-ti-staging-5.10: With the kernel being AUTOREV'd remove the ↵Praneeth Bajjuri
minor version" This reverts commit a0ee3effd66844aad8f693db821b6e3cc002240a. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-05-04ti-uboot-staging: Update to the latest ti-u-boot-2021.01Praneeth Bajjuri
Update to the latest commit of ti-u-boot-2021.01 Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-05-04Revert "linux-ti-staging, u-boot-ti-staging: lower default preference"Praneeth Bajjuri
This reverts commit a0e26c1caf7d36953bd41f6a763101f5a65919e2. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-05-04ti-sgx-ddk-um: Update srcrev to pick latestGowtham Tammana
The eglplatform.h header is updated to account for deprecation of MESA_EGL_NO_X11_HEADERS macro. Update srcrev to pick this change. Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
2021-05-04ti-sgx-ddk-km: update srcrev to pick 5.10Gowtham Tammana
Update the srcrev to pick the k5.10 development branch sources. Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
2021-05-04ti-sgx-ddk-km: properly handle arm-poky-linux-gnueabi compiler prefixZan Dobersek
The additional patch for ti-sgx-ddk-km remaps the arm-oe-linux-gnueabi prefix to the arm-linux-gnueabihf preferred target. Same should be done for the arm-poky-linux-gnueabi prefix. Signed-off-by: Zan Dobersek <zan@falconsigh.net> Reviewed-by: Gowtham Tammana <g-tammana@ti.com>
2021-05-04ti-img-rogue-umlibs: update branch to pick 5.10Gowtham Tammana
Update the branch name to pick 5.10 development branch. The srcrev remains the same at this point. Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
2021-05-04ti-img-rogue-driver: update srcrev to pick 5.10 branchGowtham Tammana
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
2021-04-09README: update maintainersDenys Dmytriyenko
Noticed maintainers list was outdated. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-04-09common-csl-ip-rtos: drop unnecessary dependency on ti-sysbiosDenys Dmytriyenko
It appears common-csl-ip-rtos does not require ti-sysbios dependency to build, but ti-pdk.bbclass adds it by default. While most of PDK-based components do require ti-sysbios to be built from sources, it is safe to remove it from CSL, reducing the dependency tree for special cases like PRU FW based on CSL, but not needing ti-sysbios. This only affects firmwares built from sources against PDK and CSL, not when RTOS firmwares are delivered in binary form for newer K3 platforms. Build-tested on am335x, am57xx, k2g and am65xx. Signed-off-by: Denys Dmytriyenko <denis@denix.org>
2021-04-05cuia: suppress installed-vs-shipped QA errorDenys Dmytriyenko
Fixes: ERROR: cuia-1.0.0.13-r0 do_package: QA Issue: cuia: Files/directories were installed but not shipped in any package: /usr/lib/gnu.targets.arm.rtsv5T.av5T /usr/lib/syscalls.am3g /usr/lib/gnu.targets.codesourcery.rtsv5T.a470MV /usr/lib/syscalls.am4g /usr/lib/gnu.targets.codesourcery.rtsv6.av6 /usr/lib/gnu.targets.arm.rtsv7A.av7A /usr/lib/syscalls.am4fg /usr/lib/gnu.targets.arm.rtsv7M.am4fg /usr/lib/gnu.targets.arm.rtsv7M.am4g /usr/lib/boot.am3g /usr/lib/gnu.targets.arm.rtsv7M.am3g /usr/lib/gnu.targets.arm.rtsv6.av6 /usr/lib/boot.am4fg /usr/lib/boot.am4g Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install. cuia: 14 installed and not shipped files. [installed-vs-shipped] Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-05multiprocmgr-test: suppress ldflags and staticdev QA errorsDenys Dmytriyenko
Resolves: QA Issue: File /usr/share/ti/examples/mpm/test/filetestdemo/host/bin/demo_filetest in package multiprocmgr-test doesn't have GNU_HASH (didn't pass LDFLAGS?) QA Issue: non -staticdev package contains static .a library: multiprocmgr-test path '/usr/share/ti/examples/mpm/test/filetestdemo/bufmgr/lib/bufmgr.a' [staticdev] Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-05edma3-lld: suppress ldflags QA errorDenys Dmytriyenko
Resolves: QA Issue: File /usr/lib/libedma3rm.so.1.0.0 in package edma3-lld doesn't have GNU_HASH (didn't pass LDFLAGS?) QA Issue: File /usr/lib/libedma3.so.1.0.0 in package edma3-lld doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags] QA Issue: File /usr/bin/edma3_drv_c66ak2e_a15_sample_a15host_release.xa15fg in package edma3-lld-test doesn't have GNU_HASH (didn't pass LDFLAGS?) QA Issue: File /usr/bin/edma3_drv_6638k2k_a15_sample_a15host_release.xa15fg in package edma3-lld-test doesn't have GNU_HASH (didn't pass LDFLAGS?) QA Issue: File /usr/bin/edma3_drv_6636k2h_a15_sample_a15host_release.xa15fg in package edma3-lld-test doesn't have GNU_HASH (didn't pass LDFLAGS?) QA Issue: File /usr/bin/edma3_drv_6630k2l_a15_sample_a15host_release.xa15fg in package edma3-lld-test doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags] Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-05vis: suppress "ldflags" QA errorDenys Dmytriyenko
It is a pre-built binary, hence no control over passing correct LDFLAGS. This used to be a warning and recently became an error. Fixes: ERROR: vis-01.50.07.15-r1 do_package_qa: QA Issue: File /usr/bin/RadioApp in package vis doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags] Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-05{qmss, cppi, srio, pa, sa}-lld-test: suppress gcc10 multiple definition of ↵Denys Dmytriyenko
fw_qmss* Workaround for these: .../ti/drv/cppi/test/k2h/armv7/linux/fw_main.c:50: multiple definition of `coreNum'; ./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/src/cppi_test.c:102: first defined here .../ti/drv/cppi/test/k2h/armv7/linux/fw_main.c:50: multiple definition of `errorCount'; ./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/src/cppi_test.c:102: first defined here .../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:85: multiple definition of `fw_passCfgVaddr'; ./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:85: first defined here .../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:84: multiple definition of `fw_srioCfgVaddr'; ./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:84: first defined here .../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:83: multiple definition of `fw_qmssDataVaddr'; ./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:83: first defined here .../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:82: multiple definition of `fw_qmssCfgVaddr'; ./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:82: first defined here Needs to be fixed properly later: https://gcc.gnu.org/gcc-10/porting_to.html Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-05mpm-transport: suppress gcc10 multiple definiton of fw_qmss*Denys Dmytriyenko
Workaround for these: qmss/mpm_transport_qmss_interface.so:(.bss+0x0): multiple definition of `fw_qmssCfgVaddr'; mpm_transport.so:(.bss+0x0): first defined here qmss/mpm_transport_qmss_interface.so:(.bss+0x4): multiple definition of `fw_qmssDataVaddr'; mpm_transport.so:(.bss+0x4): first defined here qmss/mpm_transport_qmss_interface.so:(.bss+0x8): multiple definition of `fw_srioCfgVaddr'; mpm_transport.so:(.bss+0x8): first defined here qmss/mpm_transport_qmss_interface.so:(.bss+0xc): multiple definition of `fw_srioSerdesCfgVaddr'; mpm_transport.so:(.bss+0xc): first defined here qmss/mpm_transport_qmss.so:(.bss+0x0): multiple definition of `fw_qmssCfgVaddr'; mpm_transport.so:(.bss+0x0): first defined here qmss/mpm_transport_qmss.so:(.bss+0x4): multiple definition of `fw_qmssDataVaddr'; mpm_transport.so:(.bss+0x4): first defined here qmss/mpm_transport_qmss.so:(.bss+0x8): multiple definition of `fw_srioCfgVaddr'; mpm_transport.so:(.bss+0x8): first defined here qmss/mpm_transport_qmss.so:(.bss+0xc): multiple definition of `fw_srioSerdesCfgVaddr'; mpm_transport.so:(.bss+0xc): first defined here qmss/mpm_transport_qmss_osal.so:(.bss+0x0): multiple definition of `fw_qmssCfgVaddr'; mpm_transport.so:(.bss+0x0): first defined here qmss/mpm_transport_qmss_osal.so:(.bss+0x4): multiple definition of `fw_qmssDataVaddr'; mpm_transport.so:(.bss+0x4): first defined here qmss/mpm_transport_qmss_osal.so:(.bss+0x8): multiple definition of `fw_srioCfgVaddr'; mpm_transport.so:(.bss+0x8): first defined here qmss/mpm_transport_qmss_osal.so:(.bss+0xc): multiple definition of `fw_srioSerdesCfgVaddr'; mpm_transport.so:(.bss+0xc): first defined here Needs to be fixed properly later: https://gcc.gnu.org/gcc-10/porting_to.html Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-05gdbc6x: suppress gcc10 multiple definitions of *_varobj_opsDenys Dmytriyenko
Workaround for the following gcc10 errors: .../gdbc6x/gdb/varobj.h:221: multiple definition of `ada_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:221: first defined here .../gdbc6x/gdb/varobj.h:220: multiple definition of `java_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:220: first defined here .../gdbc6x/gdb/varobj.h:219: multiple definition of `cplus_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:219: first defined here .../gdbc6x/gdb/varobj.h:218: multiple definition of `c_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:218: first defined here Needs to be resolved properly in the code later: https://gcc.gnu.org/gcc-10/porting_to.html Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-05ti-ipc: suppress gcc10 multiple definitions of _GateHWSpinlock_cfgParamsDenys Dmytriyenko
Workaround for this gcc10 error: .../linux/src/api/gates/GateHWSpinlock.c:96: multiple definition of `_GateHWSpinlock_cfgParams'; .libs/Ipc.o:.../linux/src/api/Ipc.c:97: first defined here Needs to be resolved properly in the code: https://gcc.gnu.org/gcc-10/porting_to.html Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Cc: Suman Anna <s-anna@ti.com>
2021-04-05ti-img-rogue-driver: support OE toolchain alongside Poky oneDenys Dmytriyenko
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Cc: Gowtham Tammana <g-tammana@ti.com> Reviewed-by: Gowtham Tammana <g-tammana@ti.com>
2021-04-05ti-ipc-examples: fix deprecation of sys_errlist[] in glibcDenys Dmytriyenko
It was giving this warning for years, finally gone: | warning: `sys_errlist' is deprecated; use `strerror' or `strerror_r' instead Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Cc: Suman Anna <s-anna@ti.com>
2021-04-05Revert "optee-os: upgrade to upstream 3.11.0"Denys Dmytriyenko
This reverts commit cb9297c9394783d94d69b044689bb226b074e7d2. This commit was meant for dunfell and was merged to master by mistake, as meta-arm/master already has optee 3.11
2021-04-05ti-rtos: Update metadata and versions for RTOS firmwarePraneeth Bajjuri
updated rtos firmwares j721e, j7200: 07.03.00.29 Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-04-05ti-rtos: update metadata and version of am64x rtos firmwareShiju Sivasankaran
update am64x rtos firmware to keep pinmux and control MMRs remain unlocked now since linux needs this to be unlock. this fix the USB and performance degradation issues. am64xx: 07.03.00.19 Signed-off-by: Shiju Sivasankaran <shiju@ti.com> Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-04-05ti-rtos: update metadata and version of am64x rtos firmwareShiju Sivasankaran
updated am64x rtos release mode firmware am64xx: 07.03.00.18 Signed-off-by: Shiju Sivasankaran <shiju@ti.com> Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-04-01ti-rtos: Update metadata and versions for RTOS firmwarePraneeth Bajjuri
updated rtos firmwares j721e, j7200: 07.03.00.26 Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-04-01conf/machine: k3: Lets build bmap files by defaultNishanth Menon
Lets generate bmap files for bmaptool to use as well as default to use with wic files. NOTE: bmaptool can speed up flashing SD cards by 2x-3x by skipping empty blocks of the image. https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#flashing-images-using-bmaptool Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-01conf/machine: am64xx: Switch to multi-certificate boot imagesNishanth Menon
Switch to using all of multi-certificate boot images. This allows us to create bootable images - in this case, we are missing tiboot3.bin Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-01conf/machine: am64xx: Consolidate image configuration to SoC includeNishanth Menon
IMAGE type and dependencies can easily be centralized to SoC include file. This is necessary to make sure that we don't do the duplication and having multiple places to fix up. Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-01conf/machine: j7200-evm: Switch to multi-certificate boot imagesNishanth Menon
Switch to using all of multi-certificate boot images. This allows us to create bootable images - in this case, we are missing tiboot3.bin Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-01conf/machine: am64xx/j7200: Drop trusted-firmware deployment for tar wicNishanth Menon
wic and tar dependency on trusted firmware is wrong. It is u-boot build that depends on trusted firmware deployment and is correctly handled by u-boot recipe. No point in duplicating that dependency, so just clean it all up. Reported-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-01conf/machine: j7: Document boot images as legacy modeNishanth Menon
We use the default IMAGE_BOOT_FILES configuration which matches up with legacy boot configuration. Document the same to allow folks to understand by just looking at the SoC include file. Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-01conf/machine: am65xx: Document boot images as legacy modeNishanth Menon
We use the default IMAGE_BOOT_FILES configuration which matches up with legacy boot configuration. Document the same to allow folks to understand by just looking at the SoC include file. Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-01conf/machine: k3: Add multi-certificate boot image supportNishanth Menon
Lets keep things consistent by providing two possibilities for platforms to pick from - legacy boot and multi-certificate boot. In legacy boot, the base bootloader and system firmware are maintained as separate binaries (tiboot3.bin and sysfw.itb). In multi-certificate boot that newer K3 devices support, ROM is smarter and can handle multiple x509 certificate based images: so we can strip out the sysfw.itb and integrate it as part of tiboot3.bin itself. This improves authentication and overall system boot times since we are now able to boot both the system controller and the boot processor in parallel. We do have a scheme currently to identify the images necessary for boot etc, but things are handled on a platform conf file basis. We can improve that by introducing the pattern at the top level include and use the relevant pattern in platforms as needed. Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
2021-04-01conf/machine: am64*, j7200: cleanup k3r5 configsDenys Dmytriyenko
Remove duplicate machine-specific redefines of UBOOT_BINARY, UBOOT_IMAGE and UBOOT_SYMLINK variables, as they are already defined with same values in the common k3r5.inc file. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Reviewed-by: Nishanth Menon <nm@ti.com>
2021-03-29linux-ti-staging: Update 5.4 kernel to 07.03.00.004Praneeth Bajjuri
Update 5.4 kernel to 07.03.00.004 Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-03-28ti-rtos: update metadata and version of am64x rtos firmwareShiju Sivasankaran
updated rtos firmware am64xx: 07.03.00.13 rtos fw of am64x build and upload from mcu-plus-sdk repo. Signed-off-by: Shiju Sivasankaran <shiju@ti.com> [praneeth@ti.com: updated commit message] Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-03-28ti-rtos-firmware: depend on openssl-native for signingDenys Dmytriyenko
Fixes: .../scripts/secure-binary-image.sh: line 69: openssl: command not found .../scripts/secure-binary-image.sh: line 78: openssl: command not found Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-03-28linux-ti-staging: Update 5.4 kernel to 5.4.106Praneeth Bajjuri
Update linux 5.4 to 5.4.106 stable. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-03-28ti-uboot-staging: Update to the latest commitPraneeth Bajjuri
ti-uboot-staging: Update to the latest commit Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-03-27conf/machine: fix OPTEEMACHINE name for J721ePraneeth Bajjuri
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@ti.com> Acked-by: Denys Dmytriyenko <denys@konsulko.com>
2021-03-27ti-img-rogue-umlibs: Update to pick rpath fixesGowtham Tammana
Update srcrev to pick the rpath warning fixes. Signed-off-by: Gowtham Tammana <g-tammana@ti.com> Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
2021-03-27linux-ti-mainline: Set the branch for the ti-upstream-tools repoDan Murphy
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@ti.com> Signed-off-by: Nishanth Menon <nm@ti.com>
2021-03-27linux-ti-mainline: Add gmp-native as a kernel dependencyDan Murphy
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@ti.com> Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
2021-03-27ti-sci-fw: Update J7200/AM64 deploy to install ti-sci-fwLucas 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@ti.com>
2021-03-19linux-ti-staging: Update 5.4 kernel to the latest commit SHAPraneeth Bajjuri
Update 5.4 kernel to the latest commit SHA Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-06-08 21:53:41 +0000