summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* recipes-security: optee: Update to v4.5.0+Chirag Shilwant2025-02-071-2/+2
| | | | | | | Bump up SRCREV of optee-os to ef1ebdc23034a804a72da2207f1a825ce96a1464 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "u-boot: Fix implicit declaration compile error"Ryan Eatmon2025-02-072-34/+0
| | | | | | | | | This reverts commit eeb68bcae31b60273331245cb849fa6635b74352. This patch was accepted to the ti-u-boot repo, so this patch is no longer needed. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j722s: Add overlay to KERNEL_DEVICETREE_PREFIXAnurag Dutta2025-02-051-0/+1
| | | | | | | | | Add the overlay "k3-j7200-evm-mcspi-loopback.dtso" to the j722s configuration so that SPI loopback tests can be carried out successfully. Signed-off-by: Anurag Dutta <a-dutta@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: relocate 22.3.5 patchesRandolph Sapp2025-02-047-0/+0
| | | | | | | | Relocate the patches for 22.3.5 to the mesa-pvr-22.3.5 subdirectory so it's more clear what version of mesa they apply to. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-mainline: Update to version: v2025.01LCPD Automation Script2025-02-041-2/+2
| | | | | | | | Updated the value(s) for: u-boot-ti-mainline: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-umlibs: filter binaries post installRandolph Sapp2025-02-042-10/+10
| | | | | | | | | No reason to do this pre install now that my python function can evaluate file paths. Also, this may have been causing issues with state when attempting to switch between opencl enabled/disabled builds. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: select the graphics 24.2 packagesRandolph Sapp2025-02-041-1/+6
| | | | | | | | | Since this is new logic is in place, switch the k6.6 and k6.12 configs to use these new libraries. Do not enable GFX on 6.12 just yet. Still need some kernel patches on the SGX side. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: version 23.2.1 -> 24.0.1Randolph Sapp2025-02-0410-113/+181
| | | | | | | | | The gfx library provided by rogue can support this never version of mesa out of the box. Pull it in now that we have ported the SGX side of things. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-*: version 24.1.6554834 -> 24.2.6643903Randolph Sapp2025-02-042-4/+4
| | | | | | | | Bump the package version for DDK 24.2, this includes a few fixups from IMG and support for a newer version of mesa. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot: Fix implicit declaration compile errorRyan Eatmon2025-02-032-0/+34
| | | | | | | | | A recent patch to ti-u-boot 2025.01 introduces a compile error on master for am64xx-evm. A patch has been sent to the mailing list that fixes this, but it will take time before we will see that patch available to us on master. So we need to carry the patch here. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202502031558LCPD Automation Script2025-02-033-5/+5
| | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: CNM_WAVE521_FW_VERSION,TI_LINUX_FW_SRCREV u-boot-ti-staging_2025.01: SRCREV linux-ti-staging_6.12: PV,SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=1eaf07dc4ec5cdeb98078f17a9d4635e88f43f75..7fbc75f80161a400a4b9c618b6191d72ab408def u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=b841e559cd26ffcb20f22e8ee75debed9616c002..4e9c90ad8b12cc5b4fdd1308bc3ac3e4fc869aab linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=ade72d105eb7c9a2a4addfd0204eb4551b8efa7a..8906665ace32eb0dc12810667ee8646bd660c374 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-ti-staging: Add config-fragments for v6.12 KernelBeleswar Padhi2025-01-238-8/+8
| | | | | | | | ti-linux-kernel tree has several prune config fragments for ARM/ARM64/RT configurations. Enable the prune config fragments here. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Acked-by: Andrew Davis <afd@ti.com>
* conf: machine: k3: Use Cortex-A53/A72 CPU tuneAndrew Davis2025-01-221-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | All current K3 devices use either A53 or A72. Use the compile tune configuration specific for these to allow the compiler to make better optimizations. Default tune here is weakly set to a lowest common denominator of aarch64, as before, which is a recommended behavior for a BSP layer. This allows for greater binary reuse (packages, sstate, etc.) across different platforms of the same architecture in multi-BSP environments. At the same time, since all the correct tunes are now configured for K3 devices, one can elevate compiler optimization levels either from local.conf or own Distro configuration on a per-SoC or per-device basis, like so: DEFAULTTUNE:k3 = "armv8a-crc" DEFAULTTUNE:j721e = "cortexa72-cortexa53" DEFAULTTUNE:beagleplay = "cortexa72-cortexa53" Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* ti-ipc-rtos: Move to update-alternatives classRyan Eatmon2025-01-221-21/+19
| | | | | | | | There were some errors related to ipk postinst. The issues were fixed by going to the update-alternatives class instead of trying to create the steps directly in the recipe. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ipumm-fw: Disable buildpaths checkRyan Eatmon2025-01-221-0/+9
| | | | | | | | | The ti-cgt-arm compiler is a custom TI compiler. It does not currently support reproducible builds and is provided via a binary blob download that we cannot patch in the recipe to address the issue. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* libdce: Fix compile errorsRyan Eatmon2025-01-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update SRCREV to pick up patch that fixes some compile errors: ../git/memplugin_linux.c: In function 'memplugin_alloc': ../git/memplugin_linux.c:69:9: error: implicit declaration of function 'dsp_dce_buf_lock' [-Wimplicit-function-declaration] 69 | dsp_dce_buf_lock(1, &(h->dma_buf_fd)); | ^~~~~~~~~~~~~~~~ ../git/memplugin_linux.c:71:9: error: implicit declaration of function 'dce_buf_lock' [-Wimplicit-function-declaration] 71 | dce_buf_lock(1, &(h->dma_buf_fd)); | ^~~~~~~~~~~~ ../git/memplugin_linux.c: In function 'memplugin_free': ../git/memplugin_linux.c:91:17: error: implicit declaration of function 'dsp_dce_buf_unlock' [-Wimplicit-function-declaration] 91 | dsp_dce_buf_unlock(1, &(h->dma_buf_fd)); | ^~~~~~~~~~~~~~~~~~ ../git/memplugin_linux.c:93:17: error: implicit declaration of function 'dce_buf_unlock' [-Wimplicit-function-declaration] 93 | dce_buf_unlock(1, &(h->dma_buf_fd)); | ^~~~~~~~~~~~~~ ../git/memplugin_linux.c:95:13: error: implicit declaration of function 'close'; did you mean 'pclose'? [-Wimplicit-function-declaration] 95 | close(h->dma_buf_fd); | ^~~~~ | pclose and ../git/libdce_linux.c: In function 'dce_deinit': ../git/libdce_linux.c:90:9: error: implicit declaration of function 'close'; did you mean 'pclose'? [-Wimplicit-function-declaration] 90 | close(OmapDrm_FD); | ^~~~~ | pclose Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-mainline: Add patch to use SWIG_AppendOutputRyan Eatmon2025-01-221-0/+2
| | | | | | | | | | | | | | Missed this recipe with the previous recipe. Swig has changed language specific AppendOutput functions. The helper macro SWIG_AppendOutput remains unchanged. Use that instead of SWIG_Python_AppendOutput, which would require an extra parameter since swig 4.3.0. This is a port from oe-core: https://git.openembedded.org/openembedded-core/commit/?id=4eae7888e91c7c864bf490dee38716267be6202e Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Disable GC320 support conditionally on BSP versionAndrew Davis2025-01-222-0/+21
| | | | | | | | | | | | Like we do with GPU support, GC320 support is conditional on the kernel we are building and so should be disabled here for kernels on which it is not functional yet. We can then remove these disabling lines as the driver is updated for each supported kernel, instead of blanket disabling in the distro layer as done currently. Signed-off-by: Andrew Davis <afd@ti.com>
* meta-ti-extras: mathlib: Do not deploy packaged outputAndrew Davis2025-01-221-14/+0
| | | | | | | | | This might have been useful for building development packages with the pre-built binaries for deployment elsewhere, but there are better ways to do this and these are no longer consumed. Remove this packaging step. Signed-off-by: Andrew Davis <afd@ti.com>
* meta-ti-extras: dsplib: Do not deploy packaged outputAndrew Davis2025-01-221-14/+0
| | | | | | | | | This might have been useful for building development packages with the pre-built binaries for deployment elsewhere, but there are better ways to do this and these are no longer consumed. Remove this packaging step. Signed-off-by: Andrew Davis <afd@ti.com>
* linux-ti-staging: Drop systest kernelAndrew Davis2025-01-2213-31/+0
| | | | | | | | | This was used when the kernel had a different configuration for the testing kernel. This has not been the case since v5.10 so drop the systest kernel package as it will be the same as the normal kernel package now. Signed-off-by: Andrew Davis <afd@ti.com>
* ti-bsp: Change to 6.12 as the defaultRyan Eatmon2025-01-224-7/+1
| | | | | | | | | | | | | | | | | We are moving to 6.12 to be our new LTS, so we are switching the default BSP to that. You can still access the 6.6 kernel if you need to by using the BSP system and setting TI_PREFERRED_BSP = "ti-6_6" in your local.conf. Current known issues: - Hardware graphics is disabled until we get a patch that updates the patches to work with the 6.12 kernel. Falling back to software rendering. - am62xxsip-evm and j742s2-evm are not supported in the 2025.01 u-boot yet. They will fail to build until the u-boot recipe is updated to point to a commit that fixes their support. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-staging: Move 2024.10 to 2025.01 for ltsprepRyan Eatmon2025-01-223-15/+13
| | | | | | | We are moving to 2025.01 for the next LTS, so rename the previous ltsprep recipe and update it. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: beaglebone-ai64: Update SPL_BINARYRyan Eatmon2025-01-221-5/+1
| | | | | | | | Rather than override the value for SPL_BINARY for all bsps, simply just set the value to the correct value. This should be ok since all beaglebone-ai64 variations should use tispl.bin_unsigned. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: beagleplay*: Update defaults to mainlineRyan Eatmon2025-01-224-15/+7
| | | | | | | | | The defaults for UBOOT_MACHINE and SPL_BINARY are now aligned with the mainline values and new ti-6_1 values for the previous defaults were created to capture those. Also updated the meta-beagle beagleplay since it inherits the beagleplay-ti settings. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-mainline: Update KERNEL_REPRODUCIBILITY_PATCHES for v6.12Ryan Eatmon2025-01-222-0/+33
| | | | | | | | The script that sends the automated patch does not currently handle updating the KERNEL_REPRODUCIBILITY_PATCHES variable with the changes in the patches. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-mainline: Update to version: v6.12Ryan Eatmon2025-01-223-4/+8
| | | | | | | | | Updated the value(s) for: am65xx-evm: KERNEL_DEVICETREE j722s-evm: KERNEL_DEVICETREE linux-ti-mainline: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* meta-beagle: Add SECURITY filecicd.master.202412200100Ryan Eatmon2024-12-171-0/+20
| | | | | | Add missing SECURITY file required by yocto-check-layer. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-bb.org_6.6: disable FORTIFY_SOURCE for nowDenys Dmytriyenko2024-12-162-0/+4
| | | | | | | | Rogue graphics driver 24.1 currently fails to build against the kernel that enables FORTIFY_SOURCE, such as bb.org. Disable this config for now, until the driver is fixed. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* beagle-bsp, linux-bb.org, u-boot-bb.org: add support for 6.6 BSPDenys Dmytriyenko2024-12-1612-31/+182
| | | | | | | | | | Most Beagle platforms are switching to 6.6 based Linux kernel and U-boot 2024.10. Add corresponding recipes and extend beagle-bsp with required settings. BeagleY-AI for now remains on 6.1 BSP with U-boot 2023.04. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* linux-bb.org, u-boot-bb.org: rename recipes with versionDenys Dmytriyenko2024-12-165-110/+3
| | | | | | | | | Rename "bb_org" BSP recipes to include version in the recipe names. This way we can support multiple versions. Also remove 2 unused kernel patches that were needed for 5.10 Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf/machine: add BeagleY-AI platformDenys Dmytriyenko2024-12-163-0/+42
| | | | | | Add machine configuration for BeagleY-AI platform. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* linux-bb.org: update Beagle BSP to 6.1.83Denys Dmytriyenko2024-12-161-8/+8
| | | | | | Update Beagle BSP to the latest 6.1.83 kernel version. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* u-boot-bb_org, linux-bb_org: move "bb_org" providers to meta-beagleDenys Dmytriyenko2024-12-165-1/+3
| | | | | | | Move "bb_org" kernel and U-boot providers that use corresponding official BeagleBoard.org trees into own meta-beagle layer. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf/machine: move remaining Beagle platforms to meta-beagleDenys Dmytriyenko2024-12-164-8/+4
| | | | | | | Include beagle-bsp.inc to define "bb_org" BSP settings and select that as a default. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf/machine: split beagleplay config between meta-ti-bsp and meta-beagleDenys Dmytriyenko2024-12-164-50/+55
| | | | | | | | | | | Extract "bb_org" BSP specific settings from beagleplay-ti in meta-ti-bsp and move them to own beagleplay machine config in meta-beagle. The differences between 2 configs are minimal, hence beagleplay in meta-beagle inherits beagleplay-ti from meta-ti-bsp as a base and only adjusts what's needed. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf/machine: move "bb_org" BSP settings to meta-beagleDenys Dmytriyenko2024-12-162-20/+25
| | | | | | | Define "bb_org" default BSP settings in meta-beagle layer that all Beagle platforms will use. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* meta-beagle: layer.conf: add lz4c to host tools listDenys Dmytriyenko2024-12-161-0/+2
| | | | | | | | OE-Core master has switched from lz4c to lz4 host tool, but a corresponding change only appears in kernel 6.13. Since bb.org kernels 6.1 and 6.6 enable LZ4 compression by default, also add a legacy lz4c tool in the list. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* meta-beagle: create a separate layer for Beagle platformsDenys Dmytriyenko2024-12-163-0/+63
| | | | | | | | | The new meta-beagle will host all supported Beagle platforms that use TI SoCs and hence need to depend on meta-ti-bsp. The default BSP for the platforms in this layer will use BeagleBoard.org official trees for the Linux kernel and U-boot. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf/machine: rename beagleplay machine to beagleplay-tiDenys Dmytriyenko2024-12-162-0/+0
| | | | | | | | | | | | | BeaglePlay is officially supported by TI "ti-6_6" BSP and is part of the TI-SDK releases. Switching BSP to BeagleBoard.org "bb_org" settings for the same machine is possible within the same layer. But having different machine configs for the same machine name in multiple layers can be confusing and prone to errors. Hence rename the config to indicate BeaglePlay with official TI support in order to re-use the canonical name in a separate layer. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* meta-ti-bsp: ti-rtos-bin: Move this with the other firmware recipesAndrew Davis2024-12-131-0/+0
| | | | | | | | | | | All other firmware recipes are in recipes-bsp. There is nothing much special about this set of firmware so move it to match. This firmware is the pre-compiled "echo test" example for various remote cores. The directory name is not very clear on that, so fix that up too. Signed-off-by: Andrew Davis <afd@ti.com>
* meta-ti-extras: recipes-ti: Remove gadget-init packageAndrew Davis2024-12-1311-199/+0
| | | | | | | As the patch that added these states, this is an ugly hack, the issues involved are fixed and no longer relevant, remove this. Signed-off-by: Andrew Davis <afd@ti.com>
* wl18xx-fw: Do not depend on the makefile for installAndrew Davis2024-12-132-40/+3
| | | | | | | | | We use the makefile shipped with the firmware to deploy the firmware instead of just manually moving it in the install step. But the makefile doesn't do the right thing, so we also modify the makefile. Skip all this and just move the firmware ourselves. Signed-off-by: Andrew Davis <afd@ti.com>
* conf: machine: omap-a15.inc: include ipu1 firmware in the boot partitionAniket Limaye2024-12-131-1/+2
| | | | | | | | | | Early Boot of remote processors is supported at the SPL stage of the bootloader. Currently, SPL looks for the remoteproc firmwares in the boot partition. Therefore, add the rproc firmware to the boot partition of wic images. Signed-off-by: Aniket Limaye <a-limaye@ti.com>
* meta-ti-extras: ti-ipc-rtos: Deploy ipc firmwareAniket Limaye2024-12-131-0/+13
| | | | | | | | | Early boot of remote processors from SPL stage of bootloader requires the remoteproc firmware to be present in the boot partition. Deploy this rproc IPC firmware so that it can be copied to the boot partitions of the wic images. Signed-off-by: Aniket Limaye <a-limaye@ti.com>
* recipes-security: optee: Remove software PRNG for am62pxxAashvij Shenai2024-12-131-1/+1
| | | | | | | | | | | | | | | | | With the latest TIFS fix [1], AM62P is able to leverage the hardware-TRNG instead of having to fallback into the software-PRNG. Background: The default priv-id for A53 cores in SYSFW for AM62P was chosen to be 4 while the other K3 SOCs were configured at 1. Any firewall TISCI API call that used 1 would not be able to run on AM62P. The TIFS fix changes the AM62P value from 4 to 1. [1] - https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/commit/?h=ti-linux-firmware&id=98de0a4290ec200cc224d4a5a6f42d2126230e2f Signed-off-by: Aashvij Shenai <a-shenai@ti.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com>
* CI/CD Auto-Merger: cicd.master.202412130100cicd.master.202412130100LCPD Automation Script2024-12-133-3/+3
| | | | | | | | | | | | | | Updated the value(s) for: u-boot-ti-staging_2023.04: SRCREV linux-ti-staging-rt_6.1: SRCREV linux-ti-staging_6.1: SRCREV Changelogs: u-boot-ti-staging_2023.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=2a13324ec63cc488f5f578886d0cf6ece348dfda..2bedcd265ca6de803c90505df5962cbd70cda611 linux-ti-staging-rt_6.1: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=b0f9de804a162329bc81857ad50947311228dfb2..9e8992fb839c642e3c20ee8ce69a30dbaae7f498 linux-ti-staging_6.1: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=c490f4c0fe51281818c45159c0fbed94f852978e..e4e8b16e66f592749984b2d287e0479e93ef35b3 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* CI/CD Auto-Merger: cicd.master.202412101025cicd.master.202412110100cicd.master.202412101025LCPD Automation Script2024-12-108-14/+14
| | | | | | | | | | | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: PRUETH_FW_AM65X_SR2_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION 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.12: SRCREV linux-ti-staging_6.6: PV,SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=7179a74d1ed38e581bcd35e7b05632955e962c30..1eaf07dc4ec5cdeb98078f17a9d4635e88f43f75 u-boot-ti-staging_2023.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=0853d7725220d59130d8bcc59d01151cba64ffa0..2a13324ec63cc488f5f578886d0cf6ece348dfda u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=2a7de06d57399e04738573622cbdaa3532e7ab4d..29d0c23d67ee7b88e46fe1753cd020e2b04c2ef6 linux-ti-staging-rt_6.1: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=451df8c0a2a3bcf0656b2f6fdc49d6fb4d05f186..b0f9de804a162329bc81857ad50947311228dfb2 linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=d7b6ee144955d71f1c3d29b7dc08619961f12d64..c79d7ef3a56ff61dd83d5527520b419a4f0e32e2 linux-ti-staging_6.1: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=92ce8d7d2ab679e10c1dda309a0fb2ceae78b908..c490f4c0fe51281818c45159c0fbed94f852978e linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=f8f8c0b547f67d2d4d653cc59753f85275ff54f2..ade72d105eb7c9a2a4addfd0204eb4551b8efa7a linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=118cf0c8b392bed94437f1519de10b63705dbacd..a7758da17c2807e5285d6546b6797aae1d34a7d6 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot: Add patch to use SWIG_AppendOutputRyan Eatmon2024-12-074-0/+65
| | | | | | | | | | | | Swig has changed language specific AppendOutput functions. The helper macro SWIG_AppendOutput remains unchanged. Use that instead of SWIG_Python_AppendOutput, which would require an extra parameter since swig 4.3.0. This is a port from oe-core: https://git.openembedded.org/openembedded-core/commit/?id=4eae7888e91c7c864bf490dee38716267be6202e Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: layer.conf: Drop scarthgap from LAYERSERIES_COMPATChirag Shilwant2024-12-062-2/+2
| | | | | | | | | | | | | | After scarthgap release, oe-core switched to use UNPACKDIR instead of WORKDIR [1]. Post this change, meta-ti updated all references of WORKDIR to UNPACKDIR in master branch. Since, UNPACKDIR changes aren't backported to oe-core:scarthgap, we need to drop it from LAYERSERIES_COMPAT in meta-ti. [1]: https://git.openembedded.org/openembedded-core/commit/?id=e022d62ba917790af2121da57646271ef17c03fa Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Acked-by: Denys Dmytriyenko <denys@konsulko.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-08 21:33:06 +0000