summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* conf: machine: move RDEPENDS and RRECOMMENDS from kernel-rdepends.inccicd.master.202310260100cicd.master.202310250100Denys Dmytriyenko2023-10-2423-56/+39
| | | | | | | | | | | | | | | Instead of making kernel RDEPENDS on devicetree and different FW images with lots of machine-override appends that are hard to modify downstream, use proper MACHINE_ESSENTIAL_EXTRA_RDEPENDS and MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS vars that are specifically designed for this purpose. This also makes such dependencies generic and not tied to a particular kernel recipe including kernel-rdepends.inc with the entire machine-specific list. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Acked-by: Andrew Davis <afd@ti.com> Acked-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-bb.org: Remove unneeded patchesRyan Eatmon2023-10-231-5/+0
| | | | | | | With the move to the 6.1 kernel, we no longer need any of the 5.10 based patches. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: beagle*: recommend essential FW images for Beagle devicesDenys Dmytriyenko2023-10-204-0/+10
| | | | | | | | | | Set MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS per platform to list recommended essential FW images to be added to rootfs by default. Correct beagle-x15 to pull devicetrees and kernel image as well. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-bb.org: add back Beagle-specific U-boot 2023.04Denys Dmytriyenko2023-10-203-0/+22
| | | | | | | | | | | | | Majority of Beagle devices use ti-u-boot repo from u-boot-ti-staging directly. But some latest devices may need to point to own tree with additional support added that is not yet upstream, e.g. BeaglePlay. Add the Beagle-specific recipe and point beagleplay to use it. Other devices can switch to using it as well, if desired, but right now the code base is the same for other Beagle devices. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-bb.org: update kernel to 6.1 for Beagle devicesDenys Dmytriyenko2023-10-201-8/+11
| | | | | | | | | Update both 32-bit and 64-bit configs to use the latest 6.1 Linux kernel from beagleboard.org repository, which is based on ti-linux-kernel repo used in linux-ti-staging, but with extra Beagle-specific features on top. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: beagleplay: trim down the DTB listDenys Dmytriyenko2023-10-201-33/+7
| | | | | | | | | Update DTB/DTBO list to only upstreamed devicetrees and overlays. This help with migration to kernel 6.1, which doesn't have BB.org specific overlays. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: beaglebone-ai64: trim down the DTB listDenys Dmytriyenko2023-10-201-53/+8
| | | | | | | | | Update DTB/DTBO list to only upstreamed devicetrees and overlays. This help with migration to kernel 6.1, which doesn't have BB.org specific overlays. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-pru-sw-edma-driver: Remove this recipeAndrew Davis2023-10-201-31/+0
| | | | | | | Not used and the source is gone anyway, remove. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: include TI_COMMON_DEPLOY in PSEUDO_IGNORE_PATHSMatthias Schiffer2023-10-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the introduction of TI_COMMON_DEPLOY, we've been seeing frequent Pseudo errors [1] breaking image build during development, in particular with partial rebuilds due to the externalsrc bbclass. The relevant part of the error log seems to be the following: ERROR: Task (/home/schifferm/Devel/src/ci-meta-tq-kirkstone/sources/meta -tq/meta-dumpling/recipes-images/images/tq-image-generic-debug.bb:do _rootfs) failed with exit code '1' Pseudo log: path mismatch [1 link]: ino 12215614 db '/home/schifferm/Devel/src/ci-me ta-tq-kirkstone/build-mba64xx/deploy-ti/images/tqma64xxl-mbax4xxl/tq -image-generic-debug-tqma64xxl-mbax4xxl-20231020091917.testdata.json ' req '/home/schifferm/Devel/src/ci-meta-tq-kirkstone/build-mba64xx/ tmp/work/tqma64xxl_mbax4xxl-tq-linux/tq-image-generic-debug/1.0-r0/r ootfs/usr/share/stress-ng/example-jobs/device.job;65324e26'. My understanding is that all deploy dirs should be ignored by Pseudo, as openembedded-core/meta/bitbake.conf includes the whole of DEPLOY_DIR in PSEUDO_IGNORE_PATHS. With the introduction of TI_COMMON_DEPLOY, DEPLOY_DIR_IMAGE is not covered by that setting anymore, so we add it in meta-ti to avoid the issue. [1] https://wiki.yoctoproject.org/wiki/Pseudo_Abort Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com> Acked-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202310200100cicd.master.202310230100cicd.master.202310200100LCPD Automation Script2023-10-201-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-ti-staging-rt_6.1: CI/CD Auto-Merger: cicd.master.202310200100LCPD Automation Script2023-10-201-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot-ti-staging_2023.04: CI/CD Auto-Merger: cicd.master.202310200100LCPD Automation Script2023-10-201-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-linux-fw: CI/CD Auto-Merger: cicd.master.202310200100LCPD Automation Script2023-10-201-1/+1
| | | | | | | Updated the value(s) for: TI_LINUX_FW_SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* meta-ti-extras: recipes-ti: Update jailhouse SRC_URI to point to ↵cicd.master.202310180100Paresh Bhagat2023-10-171-1/+1
| | | | | | | | | | | ti-jailhouse repo The ti-jailhouse repo is synced with the Siemens/jailhouse at https://github.com/siemens/jailhouse. Use this for development and build for TI devices. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202310170100cicd.master.202310170100LCPD Automation Script2023-10-171-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot-ti-staging_2023.04: CI/CD Auto-Merger: cicd.master.202310170100LCPD Automation Script2023-10-171-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* machine: include: enable sgx on tested platformsRandolph Sapp2023-10-164-4/+4
| | | | | | | Enable SGX Graphics on the currently tested platforms. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: bump srcrev for sgx supportRandolph Sapp2023-10-161-1/+1
| | | | | | | Bump the SRCREV to include the required changes to build for SGX now. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sgx-ddk-*: version bump to support kirkstoneRandolph Sapp2023-10-163-49/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bump ti-sgx-ddk-um and ti-sgx-ddk-km to the new branch for Kirkstone and mesa independent builds. This also sets up SGX to use the latest mesa revision rogue uses. Changelog: - IMG Support has officially ended. This repo will not be getting regular updates after this unless things are really broken. - The Mesa patches which were previously being relicensed internally were opened and combined with the unofficial rogue efforts on freedesktop. - Toolchains were upgraded and multiple warnings and issues were addressed. Hardware recoveries work now, but there are still some longstanding issues with SGX that remain to be addressed if further resources are set aside for that. - We moved to an lws-generic build target to avoid rebuilding external components. As such, these external components must be patched as needed. Libdrm is an example of this and the required patches can be found in meta-ti. Known bugs: - Buffer allocations under Weston may misbehave - GLSL macro redefinitions will cause errors regardless of whether or not they are identical Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-eth-fw: Reduce priority for softlinks to 5.Aniket Limaye2023-10-161-1/+1
| | | | | | | | | Makes ti-ipc firmware as default for main-r5f0_0 firmware softlink The ti-eth-fw binaries are tested at the SDK level and should be made default only at that level Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-eth-fw: Fix firmware alternative names for j784s4Aniket Limaye2023-10-161-6/+6
| | | | | | | | The main-r5f0_0 softlinks should be pointing to the ethfw binaries instead of the mcu-r5f0_0 Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "recipes-bsp: u-boot-ti.inc: Remove ti-sci-fw from DEPENDS for k3 ↵Aniket Limaye2023-10-121-0/+1
| | | | | | | | | | machine" This reverts commit cd13cafd659f7784f4131fd0bafb8a3c7c9ef126. Some devices need ti-fs-stub-* firmware for the uboot aarch64 build Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Remove COMPATIBLE_MACHINE and extend recipe to k3 machinesAniket Limaye2023-10-121-2/+4
| | | | | | | | | | | | | Revert ebcf15bf0f31208e87ce60a4696e585940b46777 : "recipes-bsp:ti-sci-fw: Add k3r5 as COMPATIBLE_MACHINE" Extend recipe to k3 machines too, to provide ti-fs-stub-* firmware for u-boot aarch64 build. Update do_deploy() to allow multiconfig builds for k3 machines Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* amx3-cm3: use debug-prefix-mapDan McGregor2023-10-121-1/+1
| | | | | | | Fixes the QA warnings about package contains reference to TMPDIR. Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* uboot: Handle UBOOT_CONFIG for multiple R5 defconfigsGarrett Giordano2023-10-111-2/+20
| | | | | | | | | | | Currently the do_compile step fails if we try to implement UBOOT_CONFIG in an attempt to build U-Boot with multiple R5 defconfigs. This commit adds a condition to handle linking the UBOOT_BINARY if UBOOT_CONFIG is used in place of UBOOT_MACHINE. Signed-off-by: Garrett Giordano <ggiordano@phytec.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: Correctly fix SPL binary name for SD/MMC media on HS boardscicd.master.202310120100Ryan Eatmon2023-10-091-3/+30
| | | | | | | | | | The previous patch is incorrectly accepted and released. This patch applies the logic that was discussed on the mailing list. - Create a new variable grouping for SPL_HS_MLO - Update the install/deploy code to reference the new variables. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202310090100cicd.master.202310090100LCPD Automation Script2023-10-091-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-ti-staging-rt_6.1: CI/CD Auto-Merger: cicd.master.202310090100LCPD Automation Script2023-10-091-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* k3conf: CI/CD Auto-Merger: cicd.master.202310090100LCPD Automation Script2023-10-091-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot-ti-staging_2023.04: CI/CD Auto-Merger: cicd.master.202310090100LCPD Automation Script2023-10-091-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-linux-fw: CI/CD Auto-Merger: cicd.master.202310090100LCPD Automation Script2023-10-091-1/+1
| | | | | | | Updated the value(s) for: TI_LINUX_FW_SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot: set the correct latest LIC_FILES_CHKSUM genericallyDenys Dmytriyenko2023-10-053-5/+1
| | | | | | | | | | | | | | | The common u-boot-ti.inc file still uses the old license checksum from 2021 U-boot. There were formatting changes in the license text between 2021 and 2023 and version-specific recipes had the license checksum updated to the new value. Since there are no 2021 recipes remaining, the new license checksum can be set in the common .inc file generically. Note: U-boot license hasn't changed and the same checksum is simply being moved from the recipes to the common .inc file. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: Update to sha fixing deep sleep on AM62xKamlesh Gurudasani2023-10-051-1/+1
| | | | | | | | | | | Update to commit d7a7135d32a8c7da004c0c19b75bd4e2813f9759, which fixes deep sleep bug on AM62x https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=d7a7135d32a8c7da004c0c19b75bd4e2813f9759 Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com> Tested-by: Dhruva Gole <d-gole@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-dm-dw: Preserve structure of the deployed ti-dm-fw binariesAniket Limaye2023-10-051-3/+3
| | | | | | | | | | | Preserve the directory structure of the deployed dm firmware so that one can directly specify the deploy directory for binman based u-boot build. Additionally, this makes it easier to preserve the same structure inside the prebuilt-images directory of the tisdk-core-bundle for the same reason. Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Deploy the fw binaries to the deploy directoryAniket Limaye2023-10-051-0/+11
| | | | | | | | Deploy the sysfw binaries to the DEPLOYDIR, to be picked up by the tisdk-core-bundle... for the prebuilt binaries directory Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: Fix SPL binary name for SD/MMC media on HS boardsJulien Panis2023-09-291-3/+3
| | | | | | | | | The SPL binary built by u-boot for SD/MMC/eMMC media on HS platforms is u-boot-spl_HS_MLO. Thanks to this fix, the binary is properly installed and deployed. Signed-off-by: Julien Panis <jpanis@baylibre.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-bsp:ti-sci-fw: Add k3r5 as COMPATIBLE_MACHINEAniket Limaye2023-09-291-0/+1
| | | | | | | This recipe only provides the sysfw binaries compiled for the r5 Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-bsp: u-boot-ti.inc: Remove ti-sci-fw from DEPENDS for k3 machineAniket Limaye2023-09-291-1/+0
| | | | | | | | ti-sci-fw should be needed by the binman u-boot build only for the k3r5 machines and not for the k3 machines Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: Install OP-TEE OS provided TAsAndrew Davis2023-09-291-0/+6
| | | | | | | | | OP-TEE OS provides a handful of TAs itself. While these are often meant to be built-in, when they are not we should deploy them as part of the OP-TEE OS package so they can be loaded at runtime. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-umlibs: harden handling of usrmergeMax Krummenacher2023-09-291-1/+3
| | | | | | | | | | Only move directories which haven't already been moved. This prevents a build error should a subsequent bitbake execution rerun do_install where the sources to 'mv' no longer exist. | mv: cannot stat 'ti-img-rogue-umlibs/23.1.6404501/git/targetfs/am62_linux/lws-generic/release/lib/firmware': No such file or directory Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging: am335x/am437x: Add no_smp optioncicd.master.202310050100cicd.master.202310030100Praneeth Bajjuri2023-09-294-0/+8
| | | | | | | | | | | | | | | | | | multi_v7_defconfig that is used for legacy platforms enables SMP by default. Platforms like am335x and am473x are single core platforms that doesnt need this option to be enabled. This config cannot go in multi_v7_defconfig as well, since there will be systems like am57x/dra7x or other community platforms which can have multiple arm cores. Adding the provision to disable SMP configuration for applicable platforms like am335x and am437x. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202309290100cicd.master.202310020100cicd.master.202309290100LCPD Automation Script2023-09-291-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-ti-staging-rt_6.1: CI/CD Auto-Merger: cicd.master.202309290100LCPD Automation Script2023-09-291-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* k3conf: CI/CD Auto-Merger: cicd.master.202309290100LCPD Automation Script2023-09-291-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot-ti-staging_2023.04: CI/CD Auto-Merger: cicd.master.202309290100LCPD Automation Script2023-09-291-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-linux-fw: CI/CD Auto-Merger: cicd.master.202309290100LCPD Automation Script2023-09-291-1/+1
| | | | | | | Updated the value(s) for: TI_LINUX_FW_SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-bb.org: update to 5.10.168 for armv7a targetsAnthony J. Martinez2023-09-262-35/+4
| | | | | | | | | | | | | | | | | | | | | Updates SRCREV, PV, and BRANCH for armv7a targets and fixes failure to mount /boot when using poky with systemd. The kernel selected supports VFAT without initramfs as noted here - https://lists.yoctoproject.org/g/meta-ti/message/16913 Removes defconfig patch setting LZMA, as the new kernel already defaults to LZ4. Tested by running `bitbake core-image-base` with this patchset, and then booting a pair of Beaglebone Black devices from the resulting image. Prior to the change, systemd boots to a maintenance mode having failed to mount /boot. After the change, the system boots normally and /boot is mounted. Suggested-by: Robert Nelson <robertcnelson@gmail.com> Signed-off-by: Anthony J. Martinez <anthony@ajmartinez.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ipc: ti-rpmsg-char: Update library to 0.6.3Hari Nagalla2023-09-251-3/+3
| | | | | | | | Update library to 0.6.3 as it adds support for AM62P SoC. Signed-off-by: Hari Nagalla <hnagalla@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: cleanup leftover alternative entries for JacintoDenys Dmytriyenko2023-09-251-12/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Jacinto platforms use first R5 MCU core for DM firmware. When DM firmware was split out into own recipe[1], ALTERNATIVE_TARGET entries got removed from ti-rtos-firmware recipe, but corresponding ALTERNATIVE_LINK_NAME entries remained, causing warnings. Clean up those now. [1] https://git.yoctoproject.org/meta-ti/commit/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb?id=b21d29d94694ac49b97a1f4ba428c7d8cd6fb64a Fixes these warnings: | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7-mcu-r5f0_0-fw or /usr/lib/firmware/j7-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7-mcu-r5f0_0-fw: /usr/lib/firmware/j7-mcu-r5f0_0-fw.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7-mcu-r5f0_0-fw == /usr/lib/firmware/j7-mcu-r5f0_0-fw | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7200-mcu-r5f0_0-fw or /usr/lib/firmware/j7200-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7200-mcu-r5f0_0-fw: /usr/lib/firmware/j7200-mcu-r5f0_0-fw.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7200-mcu-r5f0_0-fw == /usr/lib/firmware/j7200-mcu-r5f0_0-fw | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j721s2-mcu-r5f0_0-fw or /usr/lib/firmware/j721s2-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j721s2-mcu-r5f0_0-fw: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw == /usr/lib/firmware/j721s2-mcu-r5f0_0-fw | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j784s4-mcu-r5f0_0-fw or /usr/lib/firmware/j784s4-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j784s4-mcu-r5f0_0-fw: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw == /usr/lib/firmware/j784s4-mcu-r5f0_0-fw | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-mainline: update to the latest 2023.07Ryan Eatmon2023-09-251-2/+2
| | | | | | Update to the latest release version. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-25 10:31:43 +0000