summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* 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>
* conf: machine: am62xx-lp-evm: Add PWM overlaysJudith Mendez2024-12-061-0/+2
| | | | | | | Add the PWM overlays: k3-am62x-sk-dmtimer-pwm and k3-am62x-sk-pwm for AM62 LP SK. Signed-off-by: Judith Mendez <jm@ti.com>
* ti-ipc: mark as incompatible with non-Linux buildsDenys Dmytriyenko2024-11-211-1/+1
| | | | | | | | | This package provides Linux-side components for TI IPC and depends on virtual/kernel Linux kernel for the build, so it is not compatible with non-Linux builds, such as k3r5 baremetal multiconfig. Hence adjust COMPATIBLE_HOST accordingly. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf: machine: am62pxx: Pick overlays for V3Link camerasRishikesh Donadkar2024-11-211-0/+1
| | | | | | | | | | | | | The V3Link camera fusion board [1] can be used to connect upto 4 OV5640 sensors to SK-AM62A. Overlays for interfacing OV5640 sensor with V3Link are built as part of the TI linux kernel. Pick these in the BSP filesystem. [1]: https://www.arducam.com/product/arducam-v3link-camera-kit-for-ti-development-boards/ Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com>
* ti-ipc-examples: Remove DSP/BIOS IPC examplesAndrew Davis2024-11-154-164/+0
| | | | | | | | | This IPC example is no longer supported nor recommended for new designs. The documentation is no not available either (was on Processors Wiki). Remove this example. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* SECURITY: Add fileRyan Eatmon2024-11-152-0/+40
| | | | | | | | Add a SECURITY file with hints for security researchers and other parties who might report potential security vulnerabilities. Signed-off-by: Ryan Eatmon <reatmon@ti.com> Acked-by: Denys Dmytriyenko <denys@konsulko.com>
* CI/CD Auto-Merger: cicd.master.202411120100cicd.master.202411120100LCPD Automation Script2024-11-123-3/+3
| | | | | | | | | | | | | | Updated the value(s) for: u-boot-ti-staging_2024.04: SRCREV linux-ti-staging-rt_6.6: SRCREV linux-ti-staging_6.6: SRCREV Changelogs: u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=1d8a15d0fb56ae479dd3c11e3b17d7434b079acd..2a7de06d57399e04738573622cbdaa3532e7ab4d linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=4143633c95dc50cb5e2c695629d8b6302ef8de81..d7b6ee144955d71f1c3d29b7dc08619961f12d64 linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=399452cd6d8ff30967ddc4baa444afd32cbbedeb..118cf0c8b392bed94437f1519de10b63705dbacd Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* sgx: bump version for kernel 6.6 / mesa 23.2.1Randolph Sapp2024-11-073-3/+13
| | | | | | | | | | Bump versions of mesa-pvr and ti-sgx-ddk-km to support SGX with kernel 6.6 and the same version of mesa rogue is using. Enable SGX by default in the 6.6 BSP provider section logic. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: Update to DM_MANAGED suspendRyan Eatmon2024-11-071-2/+2
| | | | | | | | | | | | | Update to commit 58b25570c9ef91753b14c2103f45f4be9dddb696, which adds the DM_MANAGED suspend feature. https://git.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a.git/+/58b25570c9ef91753b14c2103f45f4be9dddb696 Also change the docs/license.rst checksum. The license file was modified to include a reference to the pydevicetree project which uses the Apache License 2.0. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: remove dynamic-layer append for llvmpipeRandolph Sapp2024-11-062-18/+0
| | | | | | | | | | The mesa.inc that we inherit from oe-core now has the required parameters. This conditional append is no longer required. This reverts commit dbc6afc46e55b247606dfad5238137c8fa807843. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr-22.3.5: Fix build issues with llvm 18+Ryan Eatmon2024-11-063-0/+120
| | | | | | | Backport two fixes from the latest mesa project to fix two builds issues related to newer llvm versions. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr_23.2.1: Fix build issues with llvm 18+Ryan Eatmon2024-11-062-0/+54
| | | | | | | Backport two fixes from the latest mesa project to fix two builds issues related to newer llvm versions. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202411061115cicd.master.202411061115LCPD Automation Script2024-11-066-10/+10
| | | | | | | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: CNM_WAVE521_FW_VERSION,TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION u-boot-ti-staging_2024.04: SRCREV u-boot-ti-staging_2024.10: SRCREV linux-ti-staging-rt_6.6: SRCREV linux-ti-staging_6.12: PV,SRCREV linux-ti-staging_6.6: SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=ddb9cc251ace41dfad6650390f82e4a389d3967e..7179a74d1ed38e581bcd35e7b05632955e962c30 u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=cdac8b4cd3cc1d1e9ac6354c1cfe03ddbbdf01fa..1d8a15d0fb56ae479dd3c11e3b17d7434b079acd u-boot-ti-staging_2024.10: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=c97ada2dc66934ee00a7a03d9ed078bdfb7b4039..f919c3a889f0ec7d63a48b5d0ed064386b0980bd linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=517163f797b81a8277a000d6a1c9dfd89b3711b8..4143633c95dc50cb5e2c695629d8b6302ef8de81 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=9852d85ec9d492ebef56dc5f229416c925758edc..f8f8c0b547f67d2d4d653cc59753f85275ff54f2 linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=32ae7316ddc6d9b6bb0d87706cf7daa44c4c1e92..399452cd6d8ff30967ddc4baa444afd32cbbedeb Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-bsp: Tighten up versions for PREFERRED_VERSIONRyan Eatmon2024-10-311-3/+3
| | | | | | | | | | PREFERRED_VERSION matches against the PV in the recipe, not against the file name. With the upcoming 6.12, the 6.1 kernel version string was a little too loose. The "6.1%" could glob onto the 6.12 recipe. Take this time to also clean up a couple of the other versions and narrow them down. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Add support for bsp-ti-6_12 in beagleplayChirag Shilwant2024-10-242-0/+2
| | | | | | | | Add bsp-ti-6_12 overrides in A53 & R5 machine configuration to ensure it picks the appropriate u-boot configs for beagleplay Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: Enable OP-TEE TRNG in J722sManorit Chawdhry2024-10-231-1/+1
| | | | | | | | | | | Enable TRNG in J722s, as bugs related to TRNG has been fixed now. Following firmwares have the fix [0] [0]: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/commit/?h=ti-linux-firmware-next&id=d9177916332be8887398d20e12ad48a9faa6cc9c Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee: Update to v4.4.0Ryan Eatmon2024-10-224-7/+14
| | | | | | Update all of the components to the upstream 4.4.0 version. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: Tweak the GIT variables for u-bootRyan Eatmon2024-10-221-2/+3
| | | | | | | | We are planning on adding upstream u-boot testing against stable tagged versions of u-boot and need a little more control over telling bitbake to not point at a branch but point to a tag. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-mainline: Update to 2024.10Ryan Eatmon2024-10-221-11/+4
| | | | | | | | | Update to the latest u-boot release v2024.10. Additionally, take this time to clean up the mainline recipe and streamline it a bit. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* uboot-ti-next: Add new recipe to track master-nextRyan Eatmon2024-10-222-1/+6
| | | | | | | | | Our upstream testing needs to point to both master and master-next and we need two different recipes to track that. This recipe mirrors the linux-ti-next recipe and points to the master-next branch for the latest bleeding edge changes. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux: Consolidate the SRC_URI variablesRyan Eatmon2024-10-197-31/+27
| | | | | | | | | | | | | | | | | | | | | It was suggested to move the reproducibility patches out of ti-kernel.inc and into the respective recipes. Taking this time to also rework all of the pieces that go into the SRC_URI and create a standardization for how all of the kernel recipes are done. Create KERNEL_GIT_URI, KERNEL_GIT_PROTOCOL, KERNEL_GIT_BRANCH, KERNEL_DEFCONFIG, and KERNEL_REPRODUCIBILITY_PATCHES. The default for the above new variables is to the git.ti.com repository and how we manage the kernel settings. The other kernel recipes that do something other than how TI does it can simply override the variables. This change will make it easier to perform the upstream testing that we do on a nightly basis. Additionally, it will simplify the auto generation of the patches to move the mainline (stable kernel) recipes since the required patches will be all done in the same recipe. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-mainline: Update to version: v6.11LCPD Automation Script2024-10-198-3/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | Updated the value(s) for: am57xx-evm: KERNEL_DEVICETREE am62axx-evm: KERNEL_DEVICETREE am62pxx-evm: KERNEL_DEVICETREE am62xx-evm: KERNEL_DEVICETREE am62xx-lp-evm: KERNEL_DEVICETREE am68-sk: KERNEL_DEVICETREE am69-sk: KERNEL_DEVICETREE beagleplay: KERNEL_DEVICETREE am64xx-evm: KERNEL_DEVICETREE am65xx-evm: KERNEL_DEVICETREE am335x-evm: KERNEL_DEVICETREE am437x-evm: KERNEL_DEVICETREE j7200-evm: KERNEL_DEVICETREE j721e-evm: KERNEL_DEVICETREE j721e-sk: KERNEL_DEVICETREE j721s2-evm: KERNEL_DEVICETREE j722s-evm: KERNEL_DEVICETREE j784s4-evm: KERNEL_DEVICETREE linux-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: fix j721e NPOT texture issuesRandolph Sapp2024-10-191-1/+1
| | | | | | | | | | | Resolve some issues with J721E and compressed NPOT (Non-Power-Of-Two) textures. Also, add some additional allocation tracking in render process specific tasks. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-22 22:44:43 +0000