summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* CI/CD Auto-Merger: cicd.master.202510220100HEADcicd.master.202510220100master-nextmasterLCPD Automation Script25 hours1-1/+1
| | | | | | | | | | Updated the value(s) for: k3conf: SRCREV Changelogs: k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=f63ccd27cba9550de04e8dbb04bc6003d8b5168e..4612157b45912dfc21ef49e364931c5ce3cb27a0 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* meta-ti-bsp: conf: machine: include: Build initramfs for all TI SoCs.Moteen Shah32 hours1-1/+17
| | | | | | | | | Trigger build for initramfs image and package it in the boot partition of all TI SoC's whenever an image recipe is built with upstream kernel(mainline or mainline-next). Signed-off-by: Moteen Shah <m-shah@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: wic: Add initramfs path to to grub configMoteen Shah32 hours1-1/+1
| | | | | | | | | Add initrd path to grub.cfg config so that it picks up the initramfs image from the boot partition and includes it in the boot process. Signed-off-by: Moteen Shah <m-shah@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-ti: initramfs: Make minimal initramfs imageMoteen Shah32 hours2-0/+48
| | | | | | | | | | Introduce a new minimal initramfs image which will be used for all K3 devices in the boot flow. The image will package boot essential and other modules which will be modprobed by initramfs-udev once the inbuilt drivers gets probed. Signed-off-by: Moteen Shah <m-shah@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: conf: machine: include: Add common module variable for TI ↵Moteen Shah32 hours4-0/+11
| | | | | | | | | | | Initramfs image Add a new variable in ti-soc.inc which would be populated by individual platforms with the required modules which would later be packaged inside the initramfs image. Signed-off-by: Moteen Shah <m-shah@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202510200100cicd.master.202510210100cicd.master.202510200100LCPD Automation Script3 days5-8/+8
| | | | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION atf: SRCREV_tfa:am62lxx u-boot-ti-staging_2025.01: SRCREV_uboot linux-ti-staging-rt_6.12: PV_ARM32,SRCREV_ARM32 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=27344bea60be4f0410feb1c309b9de3cdc7f8c6d..237071793594723bf1c2e9eef8ff836ffa3b09df u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=c779c758475cb98e95d3c05744e0dcbca5fc9991..b5956eebf45b7b604c046a21792883a42cd9c198 linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=2c04cd1373bf2cd53784cc10efad710f9fa5b5c8..dd80e6d61d8ccba753eb372040107ff195c8550d linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=3a3f87d0bf70131af74a85336c2785d933732825..2ce6f0999344a368217d04cdbee0922144ecc899 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot-ti-mainline: Update to version: v2025.10LCPD Automation Script8 days1-2/+2
| | | | | | | | Updated the value(s) for: u-boot-ti-mainline: PV,SRCREV_uboot Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-extras: dsptop: Explicitly allow build for AM57xAndrew Davis8 days3-3/+3
| | | | | | | | | | | | This recipe builds and runs fine on both DRA7x and AM57x machines. The COMPATIBLE_MACHINE is set to just DRA7x, but this was okay as AM57x machines also set themselves as DRA7x family devices. The issue is then we cannot then differentiate between packages that are actually DRA7x- only and those that just use that family to mean both machine types. To fix this when we mean both are allowed use "omap-a15" as done here. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-extras: gdbc6x: Explicitly allow build for AM57xAndrew Davis8 days3-3/+3
| | | | | | | | | | | | This recipe builds and runs fine on both DRA7x and AM57x machines. The COMPATIBLE_MACHINE is set to just DRA7x, but this was okay as AM57x machines also set themselves as DRA7x family devices. The issue is then we cannot then differentiate between packages that are actually DRA7x- only and those that just use that family to mean both machine types. To fix this when we mean both are allowed use "omap-a15" as done here. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-extras: dsptop: Simplify for DRA7xx only buildAndrew Davis8 days3-18/+6
| | | | | | | | | | | This recipe is already only compatible with the DRA7xx machine, so no need to set PLATFORM based on the only possibility. This then allows us to directly set the compile flags for the same. And now that the package does not change based on the machine, remove the PACKAGE_ARCH line. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-extras: gdbc6x: Simplify for DRA7xx only buildAndrew Davis8 days2-12/+4
| | | | | | | | | | | This recipe is already only compatible with the DRA7xx machine, so no need to set PLATFORM based on the only possibility. This then allows us to directly set the compile flags for the same. And now that the package does not change based on the machine, remove the PACKAGE_ARCH line. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-extras: libaet: Remove this recipeAndrew Davis8 days1-38/+0
| | | | | | | | This was only ever used as part of the DSP firmware for OpenCL dispatch. That is all gone now, so remove this leftover dependency. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: vpe-tests: Remove this recipeAndrew Davis8 days1-28/+0
| | | | | | | | | | vpe-tests is obsolete, it was replaced with "testvpe" as part of glsdk-example-apps about 10 years ago in meta-arago, so long ago even its replacement has been obsoleted and removed. Yet, this unbuildable recipe still lives on here in meta-ti. Send it out to sea. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot: Make sure the build dir is unique for each UBOOT_CONFIGRyan Eatmon9 days1-29/+31
| | | | | | | | Make the same changes as the corresponding oe-core patch. [1] [1] https://git.openembedded.org/openembedded-core/commit/?id=22e96b32b0be02ec0971c9334d4b1df7c9ef8d84 Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* machine: Add FIT_CONF_DEFAULT_DTB for legacy platformsRyan Eatmon13 days3-0/+3
| | | | | | | | | | As of u-boot 2025.10, the fit image requires a value for the default configuration. The change [1] introduced the FIT_CONF_DEFAULT_DTB code to the legacy fitimage class, but failed to set values for the legacy platforms. This led to us putting default = "" in the .its file, which is now an error. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add pruprp-fw for AM64xxMD Danish Anwar2025-09-301-1/+1
| | | | | | | | AM64x supports PRP. Add pruprp-fw to AM64xx so that this can be packaged for AM64xx Signed-off-by: MD Danish Anwar <danishanwar@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-beagle: beagley-ai: Set forward looking UBOOT_MACHINE defaultAndrew Davis2025-09-302-4/+7
| | | | | | | | | | U-Boot bb.org-v6.12, Mainline, Next, and all future releases will have am67a_beagley_ai_r5_defconfig. Only the three listed versions in this patch need to use the old defconfig. Set the default so that we do not need to set this for future versions. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot: Moved to named git repocicd.master.202509300100Ryan Eatmon2025-09-265-5/+7
| | | | | | | | | An upcoming patch series will optionally add in a second repository that will optionally be needed as part of the builds. To facilitate that, we need to name the uboot checkout so that the SRCREV can be tracked correctly in the recipe. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-extras: Clean upRyan Eatmon2025-09-2612-36/+21
| | | | | | | | | | | | | | | | | | | The TI_EXTRAS infrastructure needs a little tweaking to support turning on multiple extra options at the same time. 1) Since TI_EXTRAS can be a space separated list and not a single fixed value, we need to change how we detect when to include the TI_EXTRA values. 2) The tie-jailhouse overrides were being a little too heavy handed. All of the variables that are changed for any given extra feature needs to use the proper variable override. This was most important for the COMPATIBLE_MACHINE settings. 3) Move the ti-extras out of specific machine configs and into the ti-soc so that all machines can use the extras. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202509260100cicd.master.202509260100LCPD Automation Script2025-09-266-6/+6
| | | | | | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV atf: SRCREV_tfa:am62lxx u-boot-ti-staging_2025.01: SRCREV k3conf: SRCREV linux-ti-staging-rt_6.12: SRCREV_ARM32 linux-ti-staging_6.12: SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=33b0116556a8a57e8e456a99e45e8736db7652f3..27344bea60be4f0410feb1c309b9de3cdc7f8c6d u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=f3f8c664b3001e40cbdf46687732b2c37e1b6b33..c779c758475cb98e95d3c05744e0dcbca5fc9991 k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=3de294db4f2cd75404f358768f4be8f8fa3132d7..f63ccd27cba9550de04e8dbb04bc6003d8b5168e linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=9085e19579dfb5074d05000dcca3b9b7d8afb106..2c04cd1373bf2cd53784cc10efad710f9fa5b5c8 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=10c7960f9cf6c5e3ed0c8865596e07540bf9ba1b..3a3f87d0bf70131af74a85336c2785d933732825 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* mesa-pvr: Use PREFERRED_PROVIDER directly for GPU selectionAndrew Davis2025-09-181-8/+3
| | | | | | | | | | Now that display controller aliases are not set using PACKAGECONFIG, instead of using PREFERRED_PROVIDER to add either "sgx" or "pvr" to PACKAGECONFIG, followed by reading it back out, simply use PREFERRED_PROVIDER directly. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: Remove need for PVR/SGX display aliasesAndrew Davis2025-09-184-9/+1
| | | | | | | | | | Update mesa-pvr which includes a default set of display controller aliases for the supported display controllers. This means we do not have to manually set the alias for each device here in the integration layer. Remove that here. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Use same version for both UM and KM driverAndrew Davis2025-09-182-12/+2
| | | | | | | | The DRIVER and matching UMLIBS must always match, no need to define a version number for both. Keep this simple and remove the extra defines. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Do not remove gpu MACHINE_FEATURE conditionally on BSP versionAndrew Davis2025-09-1815-22/+14
| | | | | | | | | | | | | | | Setting or removing the gpu MACHINE_FEATURE does not actually change if the GPU driver is built or not. That is done based on the setting of the BSP_{SGX,ROGUE}_{DRIVER,UMLIBS}_{PROVIDER,VERSION} vars. These are default empty for BSP versions without supported GPU drivers, which will correctly cause a fallback to SW rendering when the GPU driver is not available. As the "gpu" MACHINE_FEATURE now has no uses, remove it from all the machine config include files. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sgx-ddk-um: UM side driver depends on KM side driverAndrew Davis2025-09-181-3/+1
| | | | | | | This also matches what is done for ti-img-rogue-umlibs. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-test: Remove unneeded patchRyan Eatmon2025-09-182-69/+0
| | | | | | | The recent SRCREV change now includes the patch, so we no longer need it. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee: Update to 4.7.0 tagSuhaas Joshi2025-09-187-10/+19
| | | | | | | | | | | | | | | Update optee_client, optee_examples, optee_os and optee_test to the newer 4.7.0 tag from the previous 4.6.0 one. Further: meta-arm applies 0003-optee-enable-clang-support patch to optee_os. However, in a recent upstream commit [0], the line to which the patch applies was removed. Therefore the patch is no longer required. As a result, tell optee_os.bbappend file to remove it. [0] https://github.com/OP-TEE/optee_os/commit/3d5c2dd8b59ae888434b3f86842828131f115d90 Signed-off-by: Suhaas Joshi <s-joshi@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-ftpm: Add TI version override for ftpmRyan Eatmon2025-09-182-0/+6
| | | | | | | | | | We are missing the optee-ftpm package verson override along with our other optee-* overrides. This resulted in a build error when meta-arm moved to 4.7.0 while we are still sitting on 4.6.0. The 4.7.0 optee-ftpm is using some new header info that the 4.6.0 optee-os-tadevkit is not providing. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: add PROVIDES for Vulkan and OpenCL ICDsRyan Eatmon2025-09-181-0/+4
| | | | | | | | | | | | A recent change in oe-core [1] has created new virtual packages to pick the driver packages for OpenCL and Vulkan Installable Client Drivers. This patch just copies the same changes from oe-core into our copy of the mesa package. [1] https://git.openembedded.org/openembedded-core/commit/meta/recipes-graphics/mesa/mesa.inc?id=6f01f029ef6fed96e257d6a88de42edaa437de3e Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Andrew Davis <afd@ti.com>
* CI/CD Auto-Merger: cicd.master.202508271122cicd.master.202508271122LCPD Automation Script2025-08-271-1/+1
| | | | | | | | | | Updated the value(s) for: k3conf: SRCREV Changelogs: k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=6700e5a7f417c1bb19daf2422b880a82b7315543..3de294db4f2cd75404f358768f4be8f8fa3132d7 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* conf: machine: Include merged device trees in the list of generated dtbsTelukula Jeevan Kumar Sahu2025-08-266-0/+28
| | | | | | | | | | | | Add support for dtbs that are generated by merging multiple .dtb and .dtbo files in the /boot directory of the root filesystem.These merged device trees are defined in ti-linux-kernel Makefile[1]. Include them using the KERNEL_DEVICETREE_DTBMERGE variable. [1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm64/boot/dts/ti/Makefile?h=ti-linux-6.12.y Signed-off-by: Telukula Jeevan Kumar Sahu <j-sahu@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: conf: drop BL32_BASE override for am62lxx-evmBryan Brattlof2025-08-251-2/+0
| | | | | | | | The BL32_BASE address is properly set in TF-A to jump to OP-TEE's entrypoint for the am62lxx SoC family, so we can safily drop this. Signed-off-by: Bryan Brattlof <bb@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: recipes-multimedia: Add udev rules for VPU and JPEG encoder symlinksThorsten Lannynd2025-08-254-0/+22
| | | | | | | | | | | | | | | | | | | This patch introduces udev rules to ensure consistent device naming for VPU decoders, encoders, and the JPEG encoder. These rules are essential for enabling hardware-accelerated video decoding in Chromium using the V4L2 Stateful decoder. The following udev rules are added: - Map vpu and vpu0 to /dev/video-dec0 and /dev/video-enc0. - Map vpu1 to /dev/video-dec1 and /dev/video-enc1. - Map the JPEG encoder to /dev/jpeg-enc0. These changes ensure proper operation of the VPU and JPEG encoder, especially when other video devices are connected, avoiding mismatches. Signed-off-by: Thorsten Lannynd <t-lannynd@ti.com> Reviewed-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202508250100cicd.master.202508260100cicd.master.202508250100LCPD Automation Script2025-08-256-8/+8
| | | | | | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV atf: SRCREV_tfa:am62lxx u-boot-ti-staging_2025.01: SRCREV k3conf: SRCREV linux-ti-staging-rt_6.12: PV_ARM32,SRCREV_ARM32 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=6506f9e1e5d8d62e9dd70123fae04bd07b90bcd5..33b0116556a8a57e8e456a99e45e8736db7652f3 u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=556593b8d5f39ad77327d2e7aa190d3faae5a350..f3f8c664b3001e40cbdf46687732b2c37e1b6b33 k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=4e8df1a41a1437b61562836e9478e8069d1a071c..6700e5a7f417c1bb19daf2422b880a82b7315543 linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=6246158ffbe4dfc005258a52780956f8baf04574..9085e19579dfb5074d05000dcca3b9b7d8afb106 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=fe4718a972cfcac11933e98f5a3986e084a7c43f..10c7960f9cf6c5e3ed0c8865596e07540bf9ba1b Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-ipc-examples-linux: Add missing SUMMARYRyan Eatmon2025-08-211-0/+1
| | | | | | The PRC script missed this. All recipes need a SUMMARY. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: add optee-os into am62lxx-evm buildsBryan Brattlof2025-08-212-1/+2
| | | | | | | | | | | | | Newer silicon revision of the AM62L family are capable of reliably booting with OP-TEE integrated in the bootflow with all bootmedia. However to support as many DDR densities as possible we cannot use the default 0x9e78000 location as with other K3 devices. So add OP-TEE back into the default build but modify the BL32 base address for TF-A so it will jump to the correct location. Signed-off-by: Bryan Brattlof <bb@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-ipc.inc: Bump SRCREV to latest for ipcdev projectBeleswar Padhi2025-08-211-2/+2
| | | | | | | | The latest tag in ipcdev project is 3.52.00.01. Update SRCREV to the latest tag. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-messageq-test-fw: Add a recipe to package prebuilt IPC firmwareBeleswar Padhi2025-08-214-13/+69
| | | | | | | | | | | | | | | | | The messageq IPC firmware example for AM57xx SoCs is available in ti-linux-firmware repository. Add a recipe to package the prebuilt messageq firmware into the rootfs. Additionally, make sure the firmware for IPU1 rproc is copied into boot partition by updating the dependency in omap-a15 machine conf to the above recipe. This is needed for Early Boot use cases and gets rid of dependency on meta-ti-extras layer. There is no need to deploy the vayu IPC firmware anymore. Remove the deploy task from ti-ipc-rtos recipe. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-ipc-examples-linux: Add a recipe to build messageq app_hostBeleswar Padhi2025-08-211-0/+65
| | | | | | | | | | | Add a recipe to build the Application Host (for A15 core) to demonstrate IPC with remote processors through messageq firmware. Also package this in the /usr/bin directory for testing IPC. This recipe only builds the app_host, and the firmwares are available in ti-linux-firmware repository. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202508210100cicd.master.202508210100LCPD Automation Script2025-08-215-7/+7
| | | | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV atf: SRCREV_tfa:am62lxx u-boot-ti-staging_2025.01: SRCREV linux-ti-staging-rt_6.12: PV_ARM32,SRCREV_ARM32 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=e89a348f4618a26812fb353a04ed9532ef890a2f..6506f9e1e5d8d62e9dd70123fae04bd07b90bcd5 u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=c5737097b4859362aa22260c5a1f2becd62af65c..556593b8d5f39ad77327d2e7aa190d3faae5a350 linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=90225824e8382c00e9628168922838a0702443eb..6246158ffbe4dfc005258a52780956f8baf04574 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=adbec2562ad14236717dc1c9dc3020c94ba27f7d..fe4718a972cfcac11933e98f5a3986e084a7c43f Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* meta-ti-bsp: Add all tiboot3.bin and sysfw.itb variants by wildcardAndrew Davis2025-08-1917-140/+5
| | | | | | | | | | U-Boot generates all the valid versions of tiboot3.bin and sysfw.itb based on the given defconfig. The defaults are also picked based on the board's binman files. No need to duplicate this logic here, simply deploy what U-Boot generates. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202508180100cicd.master.202508180100LCPD Automation Script2025-08-184-4/+4
| | | | | | | | | | | | | | | Updated the value(s) for: atf: SRCREV_tfa:am62lxx u-boot-ti-staging_2025.01: SRCREV linux-ti-staging-rt_6.12: SRCREV_ARM32 linux-ti-staging_6.12: SRCREV Changelogs: u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=05d141ca0739756a0cdd7a19268e3ad07279a17e..c5737097b4859362aa22260c5a1f2becd62af65c linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=2bcb6e9caabf65ef182dde7dc0332a7fe53622a2..90225824e8382c00e9628168922838a0702443eb linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=c94f90807b390a224fd087549b4bd5d84d5fc971..adbec2562ad14236717dc1c9dc3020c94ba27f7d Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-bsp: ti-img-encode-decode: Update SRCREVBrandon Brnich2025-08-151-1/+1
| | | | | | | | V4L2 has updated fh_add/delete to take another parameter in linux-next. The update has been made in out-of-tree module to fix build failure. Signed-off-by: Brandon Brnich <b-brnich@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-beagle: conf/machine rework all DTB listsDenys Dmytriyenko2025-08-116-26/+292
| | | | | | | | | | | Improve KERNEL_DEVICETREE lists for all Beagle platforms: * Expand the list with more overlays and related DTBs * Since in many cases the lists are slightly different between 6.6 and 6.12 kernels, explicitly provide both separate lists * PocketBeagle2 is only supported by 6.12, so one list for now Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-bb.org_6.12: upgrade to the latest 6.12.34Denys Dmytriyenko2025-08-111-9/+14
| | | | | | | Upgrade BB.org 6.12 kernel to the latest 6.12.34 tags. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-bb.org: upgrade 2025.04 -> 2025.07Denys Dmytriyenko2025-08-113-26/+19
| | | | | | | Upgrade BB.org U-boot from 2025.04 to 2025.07 Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-bb.org_6.6: update to the latestDenys Dmytriyenko2025-08-111-4/+4
| | | | | | | Update BB.org 6.6 kernel to the latest tags. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202508110100cicd.master.202508110100HEADLCPD Automation Script2025-08-111-1/+1
| | | | | | | | | | Updated the value(s) for: k3conf: SRCREV Changelogs: k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=b35ec6f6c6e11471c5d06f8c24ac396077f893be..4e8df1a41a1437b61562836e9478e8069d1a071c Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* CI/CD Auto-Merger: cicd.master.202508080100cicd.master.202508080100LCPD Automation Script2025-08-084-4/+4
| | | | | | | | | | | | | | | | Updated the value(s) for: u-boot-ti-staging_2025.01: SRCREV k3conf: SRCREV linux-ti-staging-rt_6.12: SRCREV_ARM32 linux-ti-staging_6.12: SRCREV Changelogs: u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=743712b9ee4b33cc9739a3cbeb5a8f14ae2ccf35..05d141ca0739756a0cdd7a19268e3ad07279a17e k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=2bcd5f52a88ef48f8bb5b7541cf05b10d2008cd7..b35ec6f6c6e11471c5d06f8c24ac396077f893be linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=60431d6c0e260d0b9404bcf325368a88daeef9ca..2bcb6e9caabf65ef182dde7dc0332a7fe53622a2 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=ce4785d01a0b962c7d9cb12f56dbae02514213eb..c94f90807b390a224fd087549b4bd5d84d5fc971 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* licenses: Add INSIDE-Secure LICENSEBeleswar Padhi2025-08-072-1/+20
| | | | | | | | Add the INSIDE-Secure LICENSE and update the PKA recipe to use this license. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-10-23 07:20:51 +0000