summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp
Commit message (Collapse)AuthorAgeFilesLines
* conf: machine: Update KERNEL_DEVICETREE for mainline 32bit platformsRyan Eatmon2024-04-264-27/+27
| | | | | | | | | We missed that the KERNEL_DEVICETREE should have been updated for the 32bit platforms with the change in linux-ti-mainline to v6.6. The new directory structure under arch/arm/boot/dts is in effect for that version. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: deploy initial-env for the main machineDenys Dmytriyenko2024-04-191-7/+7
| | | | | | | | | | | | | | | | | It is useful to have U-boot initial environment deployed for future reference or to initialize environment files as part of the build. In multiconfig setup, such as TI K3 platforms, building U-boot multiple times for Cortex-R5 and Cortex-A53 cores results in file conflicts when deploying under the same name. To avoid that, those initial-env files were removed at the end of the do_deploy task. But it is better to only remove them for k3r5 multiconfig, since that only builds SPL and saved env doesn't make much sense, but preserve and deploy initial-env for the main machine multiconfig. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/layer.conf: Update LAYERSERIES_COMPATRyan Eatmon2024-04-171-1/+1
| | | | | | Update LAYERSERIES_COMPAT to remove EOL branches and add future styhead. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging: Remove SRCPV againRyan Eatmon2024-04-174-4/+4
| | | | | | | Our CICD script inadvertently added the SRCPV back into the recipes. The script has been fixed, so removing the variable once again. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202404100939cicd.master.202404100939LCPD Automation Script2024-04-107-12/+12
| | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: PRUETH_FW_AM65X_SR2_VERSION,TI_LINUX_FW_SRCREV u-boot-ti-staging_2023.04: SRCREV u-boot-ti-staging_2024.04: SRCREV linux-ti-staging-rt_6.1: PV,SRCREV linux-ti-staging-rt_6.6: PV,SRCREV linux-ti-staging_6.1: PV,SRCREV linux-ti-staging_6.6: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* conf: am335x-evm: Bump up max_leb_cntChirag Shilwant2024-04-081-1/+1
| | | | | | | New features added require another increase to max_leb_cnt. Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: beagleplay/beaglebone-ai64: Set KERNEL_DEVICETREE_PREFIXRyan Eatmon2024-04-042-0/+9
| | | | | | | | Set the KERNEL_DEVICETREE_PREFIX so that, when using the various TI kernel recipes, the "correct" DTB files are pulled in depending on what is available in that kernel source. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721s2/j784s4: Pick overlays for V3Link camerasRahul T R2024-03-262-0/+2
| | | | | | | | | | | am69 and am68 sk boards supports V3Link cameras interfaced via V3Link camera fusion board. Refer to commit b7a97b1b (conf: machine: am62axx: Pick overlays for V3Link cameras) for details Signed-off-by: Rahul T R <r-ravikumar@ti.com> Acked-by: Jai Luthra <j-luthra@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j722s-evm: Update KERNERL_DEVICETREE_PREFIX to package ↵Rahul T R2024-03-251-1/+5
| | | | | | | | | | fpdlink cam dtbos j722s-evm supports capture from fpdlink cams via fpdlink fusion1 board or V3Link camera fusion board. So package fpdlink camera overlays Signed-off-by: Rahul T R <r-ravikumar@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add Zephyr RTOS example firmwareAndrew Davis2024-03-221-0/+83
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Like the current TI-RTOS/MCU+ firmware, this is a prebuilt example firmware for TI K3 remote cores. It is an alternative to the echo test demo currently provided by "ti-rtos-firmware" recipe. In addition to supporting rpmsg_client_sample just as the current firmware does, it also provides: * A serial console with shell on the MCU UART port * A console over RPMSG at /dev/ttyRPMSG0 * Example usage of the MCU GPIO/I2C/SPI from this shell * And many other Zephyr default enabled features.. It does all this using the Zephyr RTOS, a scalable real-time operating system, optimized for resource constrained devices, and built with security in mind. Zephyr is a Linux Foundation project. For more info see here[0][1]. Zephyr firmware like this can also be built as part of the Yocto build using meta-zephyr. Although this is a prebuilt currently, we intend to build this from source to reduce meta-ti's dependence on firmware blobs. This currently works with the AM62 M4F. Support for additional SoCs and cores is in progress. [0] https://www.zephyrproject.org/ [1] https://docs.zephyrproject.org/latest/introduction/index.html Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j722s: Add support for HS-SE variantAniket Limaye2024-03-181-0/+3
| | | | | | | | | | ti-u-boot [1] already supports building the HS-SE variant. Add support in the machine conf to package this tiboot3.bin in the built wic images. [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/arch/arm/dts/k3-j722s-binman.dtsi?h=ti-u-boot-2023.04&id=d2612223375a25f81068d7a7abd86c08cd129a2c Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721s2/j784s4: Add support for HS-SE variantsAniket Limaye2024-03-182-0/+6
| | | | | | | | | | | ti-u-boot [1][2] already supports building the HS-SE variants of these platforms. Add support in the machine confs to package them in the built wic images. [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/arch/arm/dts/k3-j721s2-binman.dtsi?h=ti-u-boot-2023.04 [2]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/arch/arm/dts/k3-j784s4-binman.dtsi?h=ti-u-boot-2023.04 Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j7200: Add support for HSSE1.0 and HSFS1.0Aniket Limaye2024-03-181-0/+6
| | | | | | | | | Latest ti-u-boot will be supporting HSSE1.0 and HSFS1.0 versions of the j7200 soc through the binman dts nodes. Add support in yocto to package the created binaries in the wic images. Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721e: Add support for HSSE2.0 and HSFS1.1Aniket Limaye2024-03-181-4/+12
| | | | | | | | | Latest ti-u-boot will be supporting HSSE2.0 and HSFS1.1 versions of the j721e soc through the binman dts nodes. Add support in yocto to package the created binaries in the wic images. Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62p: pick lpm overlayPraneeth Bajjuri2024-03-181-0/+1
| | | | | | | | | | | | | | overlay k3-am62x-sk-lpm-wkup-sources.dtso is common across am62x platforms. This overlay is added in 6.1 kernel at [1] [1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=4ba1886b886d This patch is to enable the same low power management wakeup sources overlay for am62pxx platform as well. Reported-by: Vibhore Vardhan <vibhore@ti.com> Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202403180100cicd.master.202403180100LCPD Automation Script2024-03-184-5/+5
| | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION u-boot-ti-staging_2023.04: SRCREV linux-ti-staging-rt_6.1: SRCREV linux-ti-staging_6.1: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* conf: machine: beagle: Centralize some settings for all beagle boardsRyan Eatmon2024-03-135-7/+7
| | | | | | | | | We have a request to be able to override the beagle kernel set in PREFERRED_PROVIDER_virtual/kernel, but it is being absolutely set and not loosely set with ?=. Take this time to create a central include for all beagle boards like we have for the k3.inc. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am57xx: export ov10635 camera device tree overlaycicd.master.202403140100Udit Kumar2024-03-131-0/+1
| | | | | Signed-off-by: Udit Kumar <u-kumar1@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* pruprp-fw: Do not make this firmware package machine specificAndrew Davis2024-03-131-6/+8
| | | | | | | | | This firmware is named so that the correct firmware is chosen on each machine. No need to split this package for each machine, combine them into one non-machine-specific package. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* prusw-fw: Combine PRU-Switch firmwares into single packageAndrew Davis2024-03-134-34/+18
| | | | | | | | | The firmware for different machines and versions are named differently so there is no need to have machine specific packages for each of these firmwares. Move all the PRU-Switch firmwares into single package. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* pruhsr-fw: Combine PRU-HSR firmwares into single packageAndrew Davis2024-03-134-34/+18
| | | | | | | | | The firmware for different machines and versions are named differently so there is no need to have machine specific packages for each of these firmwares. Move all the PRU-HSR firmwares into single package. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* prueth-fw: Combine PRU-ETH firmwares into single packageAndrew Davis2024-03-136-57/+23
| | | | | | | | | The firmware for different machines and versions are named differently so there is no need to have machine specific packages for each of these firmwares. Move all the PRU-ETH firmwares into single package. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-bsp: Do not use MACHINE_ARCH when package is not machine specificAndrew Davis2024-03-1311-19/+0
| | | | | | | | | | Most firmware does not run on the host and is therefor not architecture specific, at least as far as the package manager is concerned. Although the firmware might not be useful on some machines, the package itself is not machine specific. Remove PACKAGE_ARCH. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202403130100cicd.master.202403130100LCPD Automation Script2024-03-131-1/+1
| | | | | | | Updated the value(s) for: u-boot-ti-staging_2024.04: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ipc: ti-rpmsg-char: Update library to 0.6.6Praneeth Bajjuri2024-03-121-3/+3
| | | | | | | | | | | | update from 0.6.4 to 0.6.6. This update brings the following fixes from ti-rpmsg-char repo. 55a6f40 remove ti.ipc4.ping-pong reference 8892e57 lib: fix data type build warnings 7c2ab48 lib: fix build warnings Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202403120100cicd.master.202403120100LCPD Automation Script2024-03-122-2/+2
| | | | | | | | Updated the value(s) for: linux-ti-staging-rt_6.6: SRCREV linux-ti-staging_6.6: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* CI/CD Auto-Merger: cicd.master.202403080100cicd.master.202403110100cicd.master.202403080100LCPD Automation Script2024-03-088-14/+14
| | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION u-boot-ti-staging_2023.04: SRCREV u-boot-ti-staging_2024.04: SRCREV k3conf: SRCREV linux-ti-staging-rt_6.1: PV,SRCREV linux-ti-staging-rt_6.6: PV,SRCREV linux-ti-staging_6.1: PV,SRCREV linux-ti-staging_6.6: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* conf: machine: am62axx: Pick overlays for V3Link camerasJai Luthra2024-02-291-0/+1
| | | | | | | | | | | | | | | The new V3Link camera fusion board [1] comes with a CSI to FPDLink serializer board, which allows interfacing multiple 22-pin FFC compatible sensors with SK-AM62A. Currently overlays for interfacing IMX219 sensor with V3Link are built as part of the TI linux kernel, so pick these in the BSP filesystem. [1]: https://www.arducam.com/fpd-link-3-cameras/ Signed-off-by: Jai Luthra <j-luthra@ti.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging-rt_6.6: Add KERNEL_LCOALVERSION changeRyan Eatmon2024-02-281-0/+2
| | | | | | Copy the same KERNEL_LOCALVERSION change to the upcoming 6.6 kernel. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: Change from UBOOT_LOCALVERSION and SRCPVRyan Eatmon2024-02-281-3/+6
| | | | | | | | Stop using UBOOT_LOCALVERSION, and copy what is done in the kernel recipe. This allows us to set the correct SHA into the version string even if AUTOREV is used since SRCPV is no longer set in oe-core. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging: Update KERNEL_LOCALVERSIONRyan Eatmon2024-02-282-5/+7
| | | | | | | | | | | | | The use of KERNEL_LOCALVERSION for controlling the kernel version has changed recently. Placing the value of KERNEL_LOCALVERSION in .scmversion was causing it to duplicate the string in the final version. Instead, drop KERNEL_LOCALVERSION to just identify that it comes from TI, and that it is an RT kernel. Additionally, place the commit sha for the kernel into the .scmversion file explicitly to be both backward and forward compatible. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Drop SRCPVDenys Dmytriyenko2024-02-2818-19/+19
| | | | | | | | | | A change in master from last year [1] dropped setting SRCPV. Since it is now empty, we do not need to use when setting PV. [1] https://git.openembedded.org/openembedded-core/commit/?id=a8e7b0f932b9ea69b3a218fca18041676c65aba0 Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* CI/CD Auto-Merger: cicd.master.202402271317cicd.master.202402271317LCPD Automation Script2024-02-276-8/+8
| | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION u-boot-ti-staging_2023.04: SRCREV u-boot-ti-staging_2024.04: SRCREV k3conf: SRCREV linux-ti-staging-rt_6.1: SRCREV linux-ti-staging_6.1: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* conf: beaglebone-ai64: Apply U-boot defconfig fragmentsChirag Shilwant2024-02-202-0/+12
| | | | | | | | | | | | | | | | | | | - Apply j721e_beagleboneai64_a72.config which is maintained in U-boot tree & is intended to be applied on top of j721e_evm_a72_defconfig [1]. - Apply j721e_beagleboneai64_r5.config which is maintained in U-boot tree & is intended to be applied on top of j721e_evm_r5_defconfig [2]. References ---------- [1] https://github.com/beagleboard/u-boot/blob/v2023.04-ti-09.01.00.008-BeaglePlay/configs/j721e_beagleboneai64_a72.config [2] https://github.com/beagleboard/u-boot/blob/v2023.04-ti-09.01.00.008-BeaglePlay/configs/j721e_beagleboneai64_r5.config Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: beagleplay: Apply U-boot defconfig fragmentsChirag Shilwant2024-02-162-0/+10
| | | | | | | | | | | | | | | | | | | - Apply am625_beagleplay_a53.config which is maintained in U-boot tree & is intended to be applied on top of am62x_evm_a53_defconfig [1]. - Apply am625_beagleplay_r5.config which is maintained in U-boot tree & is intended to be applied on top of am62x_evm_r5_defconfig [2]. References ---------- [1] https://github.com/beagleboard/u-boot/blob/v2023.04-ti-09.01.00.008-BeaglePlay/configs/am625_beagleplay_a53.config [2] https://github.com/beagleboard/u-boot/blob/v2023.04-ti-09.01.00.008-BeaglePlay/configs/am625_beagleplay_r5.config Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: update BeagleBoard.org BSP to the latestDenys Dmytriyenko2024-02-146-27/+78
| | | | | | | | | | | * Update linux-bb.org to 6.1.69 for both 32 and 64 bit platforms * Update u-boot-bb.org to the latest 2023.04 based on SDK 9.1 release * Update DTB/DTBO lists to include latest renames and additions Note: all changes are in a single commit for bisectability Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-bb.org: remove custom FILES:${KERNEL_PACKAGE_NAME}-devicetreeDenys Dmytriyenko2024-02-141-7/+3
| | | | | | | | | | | | | Upstream now includes all DTB/DTBO files recursively, no need to extend corresponding FILES list. Revert "linux-bb.org: also package DT overlays in separate dir" This reverts commit f22ea63f66b02297e5a1e66b1d90ebc356bc5eeb. Note: adjust SRC_URI cosmetically, so it now matches kirkstone Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: trusted-firmware-arm: Update to masterManorit Chawdhry2024-02-141-2/+2
| | | | | | | | The current master has the support for power off functionality, update to that. Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: optee: Upgrade to 4.1Manorit Chawdhry2024-02-143-6/+6
| | | | | | | | Update all OP-TEE components to 4.1 tag. OP-TEE examples are already in 4.1 tag. Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Apply U-boot fragment configs for AM62P Display Cluster ImageChirag Shilwant2024-02-141-0/+7
| | | | | | | | | | | | | | | | | | | | | - For AM62P tisdk-display-cluster image[1], Splash Screen is handled by SBL[2]. Hence, disable the A53 based U-boot Splash Screen using the am62px_evm_prune_splashscreen.config fragment present in ti-u-boot tree. - Apply a check on DISPLAY_CLUSTER_ENABLE variable[3] to ensure we apply am62px_evm_prune_splashscreen.config only incase of tisdk-display-cluster image as tisdk-default-image will still have the A53 based U-boot Splash Screen. References ---------- [1] https://git.ti.com/cgit/ti-sdk-linux/meta-tisdk/tree/recipes-core/images/tisdk-display-cluster-image.bb?h=kirkstone [2] https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/09_01_00_39/exports/docs/api_guide_am62px/EXAMPLES_DRIVERS_DSS_DISPLAY_SHARE.html [3] https://software-dl.ti.com/processor-sdk-linux/esd/AM62PX/09_01_00_08/exports/docs/linux/Overview_Building_the_SDK.html#build-steps Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* layer.conf: add compatibility with scarthgapDenys Dmytriyenko2024-02-141-1/+1
| | | | | | | | | | OE-Core master has switched compatibility requirements from nanbield to scarthgap in preparation for the upcoming 5.0 release. https://wiki.yoctoproject.org/wiki/Releases Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202402130100cicd.master.202402130100LCPD Automation Script2024-02-137-9/+9
| | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV u-boot-ti-staging_2023.04: SRCREV k3conf: SRCREV linux-ti-staging-rt_6.1: SRCREV linux-ti-staging-rt_6.6: PV,SRCREV linux-ti-staging_6.1: SRCREV linux-ti-staging_6.6: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-ti-staging-rt: Add LTS 6.6 supportRyan Eatmon2024-02-101-2/+1
| | | | | | | Now that the correct branch exists, we can update this recipe to point to it. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-*: switch branches to new ltsRandolph Sapp2024-02-092-3/+3
| | | | | | | | Switch the branches to the new LTS names. These are still experimental, hence the isolation from kirkstone. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add bootsplash image file for AM62PDevarsh Thakkar2024-02-082-0/+13
| | | | | | | | | | Add TI logo image as bootsplash image file for AM62P and install it in boot directory from where u-boot can read from and display during boot-up time. Signed-off-by: Devarsh Thakkar <devarsht@ti.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-staging: Add 2024.04 uboot in prep for LTS migrationPraneeth Bajjuri2024-02-071-2/+2
| | | | | | | | | | | In preperation of LTS migration, switching from 2024.01 to 2024.04 for u-boot as this is close to what will be the final version for LTS. Default preference is still kept as low for this version since we are in early migration phase. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* cairo: drop local bbappendDenys Dmytriyenko2024-02-072-6/+0
| | | | | | | | | | | | | | | | | | Latest cairo release 1.18.0 no longer has corresponding opengl or glesv2 PACKAGECONFIGs. https://git.openembedded.org/openembedded-core/commit/?id=9a4ca6b08d6031ebb67adcdd650aa59acd4fb5fb Removed: - The cairo-sphinx tool - The XML, GL, GLES, Qt5, BeOS, OS/2, DirectFB, DRM, Cogl, and OpenVL backends - Autotools build system https://www.cairographics.org/news/cairo-1.18.0/ Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-*: version bump to 23.3.6512818Randolph Sapp2024-02-073-41/+4
| | | | | | | | | | | | | | | | Migrate to version 23.3.6512818, this includes the stability updates released in 23.2 as well as some additional modifications to help with userspace application support, namely Chromium. We're also dropping the x11 window system extensions from the Vulkan libraries for now. Ideally, both x11 and wayland extensions will be provided by mesa's vulkan-wsi-layer in the future, but currently x11 isn't supported and this just added extra complexity to the package in Yocto. Signed-off-by: Randolph Sapp <rs@ti.com> Tested-by: Darren Etheridge <detheridge@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: bump srcrev and drop conditional logicRandolph Sapp2024-02-061-5/+1
| | | | | | | | | | Bump the SRCREV to include some useful patches that: - Fix the ROGUE segfault issue introduced by SGX (this was what the old conditional logic was addressing) - Fix destruction of event queue with proxies still attached Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-umlibs: remove the dev packageRandolph Sapp2024-02-061-2/+1
| | | | | | | | | If Yocto even sees a "-dev" package in the PACKAGES string it will automatically forward all dev-so links to that package. Remove that entry from the PACKAGES string so we get the required links again. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>