summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp
Commit message (Collapse)AuthorAgeFilesLines
* ti-img-rogue-driver_24.1: gcc 14 compatcicd.master.202407040100cicd.master.202407020100Randolph Sapp2024-07-011-1/+1
| | | | | | | | Bump this recipe to add a change to help with GCC 14 compatibility in the check-cc script used to check compiler flags before use. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-*_23.3: gcc 14 compat and branch selRandolph Sapp2024-07-012-3/+3
| | | | | | | | | | | Bump this recipe to add a change to help with GCC 14 compatibility in the check-cc script used to check compiler flags before use. Reset this back to the proper branches for kernel 6.1 since this recipe is only being used in 6.6 bsp providers. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux: cleanup and unify mainline and next kernel recipesDenys Dmytriyenko2024-07-012-33/+5
| | | | | | | | | | | | Share the most commonality between the recipes, except: * SRC_URI torvalds vs. linux-next * SRCREV and PV * Device Tree list vs. DT prefix * SUMMARY Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-metadata: removeDenys Dmytriyenko2024-07-012-48/+0
| | | | | | | | The use of external metadata file to control RTOS binary firmware integration has been deprecated some time ago. Remove it now. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202407010100cicd.master.202407010100LCPD Automation Script2024-07-014-6/+6
| | | | | | | | | | Updated the value(s) for: ti-linux-fw: PRUETH_FW_AM65X_SR2_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION u-boot-ti-staging_2024.04: SRCREV 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.202406240100cicd.master.202406250100cicd.master.202406240100LCPD Automation Script2024-06-244-6/+6
| | | | | | | | | | Updated the value(s) for: ti-linux-fw: CNM_WAVE521_FW_VERSION,TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV u-boot-ti-staging_2024.04: SRCREV linux-ti-staging-rt_6.6: SRCREV linux-ti-staging_6.6: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* conf/machine, ti-bsp: Add support for next BSP providercicd.master.202406210100Ryan Eatmon2024-06-201-1/+14
| | | | | | | For our upstream testing flow we have the need to have a "next" BSP for configuring various settings based on building the latest kernel/uboot. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* j722s: next BSP doesn't support all SR and HS variantsRyan Eatmon2024-06-201-1/+3
| | | | | | | Adjust IMAGE_BOOT_FILES list as next BSP does not support all combinations of SR1.0, HS-FS and HS-SE variants. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202406200100cicd.master.202406200100LCPD Automation Script2024-06-203-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 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* j7200: mainline BSP doesn't support all SR and HS variantsDenys Dmytriyenko2024-06-191-2/+6
| | | | | | | | | Adjust IMAGE_BOOT_FILES list as mainline BSP does not support all combinations of SR1.0, SR2.0, HS-FS and HS-SE variants. Suggested-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* beaglebone-ai64: BB.org does not support all SR and HS variantsDenys Dmytriyenko2024-06-191-0/+3
| | | | | | | | Adjust IMAGE_BOOT_FILES list as BB.org BSP does not support all combinations of SR1.1, SR2.0, HS-FS and HS-SE variants, same as J721e EVM in mainline. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Update am62xxsip-evm for multi-BSP supportChirag Shilwant2024-06-172-0/+6
| | | | | | | | Update am62xxsip-evm machine configuration to support TI kernel 6.1 & ti-u-boot-2023.04 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: add j721e-sk machine-configurationAniket Limaye2024-06-172-0/+27
| | | | | | | | | | | | As of commit [1] there will be a separate defconfig to build u-boot for j721e-evm and j721e-sk. Hence, introduce new yocto machine configs for j721e-sk. [1]: https://source.denx.de/u-boot/u-boot/-/commit/c9507f07a1d6c92bd1f73fd64384f8c5994be9c2 Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202406151518cicd.master.202406151518LCPD Automation Script2024-06-153-5/+5
| | | | | | | | | Updated the value(s) for: u-boot-ti-staging_2024.04: SRCREV linux-ti-staging-rt_6.6: PV,SRCREV linux-ti-staging_6.6: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* meta-ti: remove MACHINE_KERNEL_PR globallyDenys Dmytriyenko2024-06-1511-36/+0
| | | | | | | | MACHINE_KERNEL_PR is a remnant of the early OE days and hasn't been needed for quite some time. Let's finally remove it completely. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine: use the default TI BSP for BeaglePlayDenys Dmytriyenko2024-06-157-7/+8
| | | | | | | | | | | BeaglePlay gains official support from latest TI lts-6.6 baseline, so set it as the default. Other Beagle platforms will still use BB.org as default. And these defaults can still be changed with TI_PREFERRED_BSP setting in a distro config or by end user in the local.conf Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine/beagle*, linux-bb.org: update for multi-BSP supportDenys Dmytriyenko2024-06-157-120/+100
| | | | | | | Update all Beagle platform configurations to support multiple BSPs. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine/j721e: some BSPs don't support all SR and HS variantsDenys Dmytriyenko2024-06-151-8/+10
| | | | | | | | Adjust IMAGE_BOOT_FILES list as some BSPs do not support all combinations of SR1.1, SR2.0, HS-FS and HS-SE variants. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine, ti-bsp: add support for multiple BSP providersDenys Dmytriyenko2024-06-1520-43/+131
| | | | | | | | | This adds a facility to define multiple supported BSPs with their own preferences for individual components, as well as lets machine configs specify conditional configurations for different BSPs. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Update UBOOT_MACHINE for am62xxsip-evmChirag Shilwant2024-06-152-7/+2
| | | | | | | | | | Modify the U-Boot defconfig names for A53 and R5 machine configurations based on ti-u-boot-2024.04 [1] [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2024.04&id=df5181f8c6c41bf018ec043d565581b5d8a291c5 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-umlibs: update for new am62p binariesRandolph Sapp2024-06-151-1/+1
| | | | | | | | Bump the SRCREV to pick up some new binaries for AM62P. The allocation patch for Chromium was not included for this device previously. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: ti-rtos-bin: Drop references of am62-main-r5f0_0-fwChirag Shilwant2024-06-151-5/+0
| | | | | | | | | | | | | | | - Under ti-ipc, ti-linux-firmware repository never had a R5 firmware for AM62x [1] It only contains `am62-mcu-m4f0_0-fw` since AM62x firmwares were initially added [2] - Hence, remove this faulty code that used to create a R5 firmware symlink under /lib/firmware/ that ultimately used to point to the same M4 firmware under /lib/firmware/ti-ipc/am62xx/ of filesystem. [1]: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/tree/ti-ipc/am62xx?h=ti-linux-firmware [2]: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/commit/?h=ti-linux-firmware&id=c2e5d59c706969a9faf1f31350b32be67a20298d Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine, linux-bb.org: re-org DT lists for Beagle platformsDenys Dmytriyenko2024-06-156-104/+144
| | | | | | | | | | | | | | | | | | | | | In order to be able to switch between different kernel providers, as well as different versions of kernel LTS (e.g. 6.1 vs. 6.6), let's re-organize Device Tree lists as follows: * Move all Beagle-specific DTBs and overlays into corresponding linux-bb.org recipe for now, to be used when building beagleboard.org baseline * Update KERNEL_DEVICETREE in the machine configs to only list what already exists in the upstream/mainline kernel * Update KERNEL_DEVICETREE_PREFIX to match the list when building TI baseline With this change it is now very easy to switch the kernel between providers supported by meta-ti - linux-ti-mainline, linux-ti-staging and linux-bb.org Please note that 6.6 LTS has moved to "vendored" device tree layout even for 32-bit platforms, while BB.org still uses 6.1 LTS and flat DT layout. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: add AM68-SK machine configurationAniket Limaye2024-06-153-0/+50
| | | | | | | | | | | | | | As of commit [1] there will be a separate defconfig to build u-boot for j721s2-evm and am68-sk. Hence, introduce new yocto machine configs for am68-sk. This is done through a new am68.inc file as the am68-sk platform does not support GP. So j721s2-evm.inc is copied to am68.inc and updated accordingly. [1]: https://source.denx.de/u-boot/u-boot/-/commit/a96be9b8c05ea835d27f7c9bae03279b8bd5dcf2 Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-umlibs: bump SRCREV for alloc patchRandolph Sapp2024-06-151-1/+1
| | | | | | | | | | Bump the SRCREV to pick up rebuilt binaries. Upstream release notes: Regenerate all binaries with a fix for exportable buffer allocations that should improve Chromium compatibility. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: update BeagleBoard.org BSP to the latestDenys Dmytriyenko2024-06-153-11/+25
| | | | | | | | | * Update linux-bb.org to 6.1.80 for both 32 and 64 bit platforms * Update DTB/DTBO lists to include latest renames and additions * Re-enable vendored DTB layout by default Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee: Update to upstream 4.2.0Kamlesh Gurudasani2024-06-155-265/+7
| | | | | | | | | Update all of the optee components to the upstream 4.2.0 version. While at it, remove the patches and fixups which are not needed anymore. Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes: Remove DEFAULT_PREFERENCERyan Eatmon2024-06-157-14/+0
| | | | | | | | Now that are past the inital stages of our LTS migration, we can remove the DEFAULT_PREFERENCE settings that prevented these recipes from being the default. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Fallback to software renderingRyan Eatmon2024-06-154-4/+4
| | | | | | | | While we are working to finish our kernel migration 6.6, we are falling aback to software rendering for platforms that do not currently have a solution for GPU drivers (namely the boards that use SGX). Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* layer.conf, TODO: drop nanbield compatibilityDenys Dmytriyenko2024-06-151-1/+1
| | | | | | | As nanbield has been EOL-ed recently. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes: Switch away from S = WORKDIRRyan Eatmon2024-05-311-1/+2
| | | | | | | | Follow along with the corresponding patch in upstream. [1] [1] https://git.openembedded.org/openembedded-core/commit/?h=master-next&id=d9328e3b0b062f0621de3d114584b44f384a1c02 Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes: Update to UNPACKDIR for files going into WORKDIRRyan Eatmon2024-05-313-9/+9
| | | | | | | | | | | | For recipes that have file:// in SRC_URI, the files are placed into WORKDIR. Moving forward [1], that directory will be UNPACKDIR and eventually move to somewhere other than WORKDIR. So update all references to WORKDIR that are looking for these file to use UNPACKDIR instead. [1] https://git.openembedded.org/openembedded-core/commit/?id=e022d62ba917790af2121da57646271ef17c03fa Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202405210100cicd.master.202405210100LCPD Automation Script2024-05-217-10/+10
| | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: 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: SRCREV linux-ti-staging_6.1: PV,SRCREV linux-ti-staging_6.6: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* conf: am437x-evm: Bump up max_leb_cntChirag Shilwant2024-05-141-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>
* mesa-pvr_23.2.1: add recipe for 23.2.1Randolph Sapp2024-05-021-0/+58
| | | | | | | | | | | | | | | Add a recipe for mesa-pvr to use a newer branch based on mesa 23.2.1. This branch does not currently contain SGX patches so it is also being masked by the ltsprep branding to prevent regressing those devices currently. Please note that may run into sstate errors when switching to or away from the ltsprep tag. Please issue a clean to mesa and ti-img-rogue-umlibs if you get warnings from either package's do_create_runtime_spdx step. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr_23.2.1: import mesa patches from oe-core/masterRandolph Sapp2024-05-024-0/+150
| | | | | | | | | Locally overlay verbatim copies of mesa 22.3.5 patches from oe-core/master, so we get whatever QoL patches from core relevant to the current release. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-*: add ddk 24.1 recipes for ltsprepRandolph Sapp2024-05-022-0/+192
| | | | | | | | | Recipes for DDK 24.1, but lock them behind ltsprep tags because they require device tree changes that do not work on the current default kernel for this layer. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am69-sk: Create a new am69.inc fileRyan Eatmon2024-04-302-1/+20
| | | | | | | | Reusing the j784s4.inc file presents problems as the am69-sk platform does not support GP. So copy the j784s4.inc to am69.inc and update accordingly. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j784s4-evm: Add k3-am69-sk dtb back inRyan Eatmon2024-04-301-0/+1
| | | | | | | | | Currently, the 6.1 kernel is the default. Removing the k3-am69-sk dtb file only applies to the 6.6 kernel. Restoring this entry so that current builds work until such time as the 6.1 kernel is removed from the recipes. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202404300100cicd.master.202404300100LCPD Automation Script2024-04-303-5/+5
| | | | | | | | | Updated the value(s) for: u-boot-ti-staging_2024.04: SRCREV linux-ti-staging-rt_6.6: PV,SRCREV linux-ti-staging_6.6: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* conf: machine: add AM69-SK machine configurationBeleswar Padhi2024-04-293-1/+31
| | | | | | | | | | | | | | | As of commits [1] and [2] in ti-u-boot-2024.04 and upstream respectively there is a separate defconfig to build u-boot for j784s4-evm and am69-sk Hence, introduce new yocto machine configs for am69-sk. Also remove am69 devicetree builds from the j784s4-evm conf [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2024.04&id=8a46af7a39e6218e4de5c6195697af36201c778c [2]: https://source.denx.de/u-boot/u-boot/-/commit/740759d558e632e1540d620baadbcc46fdf24db2 Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: cnm-wave-fw: Change target firmware nameBrandon Brnich2024-04-261-1/+1
| | | | | | | | Upstream driver expects Wave5 firmware to be named "wave521c_k3_codec_fw.bin". Driver probe fails because this compatible isn't being found. Signed-off-by: Brandon Brnich <b-brnich@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* wic: prevent boot FAT partition mounting under /bootDenys Dmytriyenko2024-04-262-3/+4
| | | | | | | | | | | | | | | | | Separate FAT boot partition holds SPL, SYSFW and U-boot images, while rootfs places kernel images and DTBs into /boot directory. So it is not desirable to mount boot FAT partition into /boot directory of the rootfs and shadow its original content - adjust corresponding entry in wic templates. While at it, remove unused ondisk parameter when using use-uuid, which takes precedence and is more flexible. Note: boot FAT partition will be automounted at /run/media/boot-mmcblk0p1/ Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Reviewed-by: Jonathan Cormier <jcormier@criticallink.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am57/am33/am43: Add/fix DEVICETREE_FILERyan Eatmon2024-04-263-3/+7
| | | | | | | | | | | | | | | | | | The new kernel directory stucture for the DTBs is causing problems when assembing the image files. It produces errors like this: output: install: cannot stat 'deploy-ti/images/XXXX-evm/omap/XXXX.dtb': No such file or directory or output: install: cannot stat 'deploy-ti/images/XXXX-evm/ti/omap/XXXX.dtb': No such file or directory The issue comes from the UBOOT_EXTLINUX_BOOT_FILES list. am57 already had a mechanism but it was missing the omap/ dir to remove, and am33 and am43 were just takeing KERNEL_DEVICETREE directly. This patch fixes both cases. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* 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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-07 11:35:03 +0000