summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp/conf/machine
Commit message (Collapse)AuthorAgeFilesLines
* Revert "conf: machine: k3: disable all fit signing for uboot"Manorit Chawdhry8 days1-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | FIT signing was disabled in the past as it was interfering with multi DTB usecase in binman, and it was thought that the binman signing being done is equivalent to UBOOT_SIGN_ENABLE. Though looking at the sources, UBOOT_SIGN_ENABLE is actually used to sign the kernel FIT Image instead and the name UBOOT actually specifies that it's used in tandom with U-boot. During the signing process, mkimage from U-boot is used to pack the kernel FIT Image and along with that, one DTB from U-boot is also passed to the mkimage command. The DTB that gets passed gets the key embedded in it that is used to verify the kernel FIT image at runtime. Now this signed DTB is packed in U-boot by triggering a rebuild with EXT_DTB argument in the U-boot build process. However, this failed as there was a U-boot bug which was not looking at the packed sources properly with the multi DTB usecase. Now that a U-boot fix is available [0], revert that commit which disabled the FIT signing. This reverts commit 9656b79cb557a46d2611b67e7e51702f6da05594. [0]: https://lore.kernel.org/all/20250626-b4-upstream-fix-icssg-fit-v1-1-95eff1c853a4@ti.com/ Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: update config fragment for ti-falconAnshul Dalal12 days4-4/+4
| | | | | | | | | | | | | The U-Boot config fragment used to enable falcon mode was renamed from 'am62x_r5_falcon.config' to the more generic 'k3_r5_falcon.config' when adapting upstream patches to ti-u-boot[1]. Therefore this patch fixes the same in meta-ti. [1]: 90d2e960b4c at ti-u-boot-2025.01-next Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp, meta-beagle: switch to the new FIT image wrapperDenys Dmytriyenko12 days8-12/+12
| | | | | | | | | | | Switch all kernel recipes and K3 based platforms to use the new FIT image wrapper functionality. Update FIT default DTB entry to not contain vendor dubdir, as it is now handled through a conf prefix. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: linux: Remove extra dtc flags for DT OverlaysAndrew Davis12 days1-1/+0
| | | | | | | | | | This hides issues like missing flags that will cause issues for folks who build or re-build the kernel outside the Yocto environment. It is better to find these issues and fix them at the source in the Linux makefile, not mask issues here. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: move UBOOT_*ADDRESS to top level ti-socAnshul Dalal2025-06-276-24/+6
| | | | | | | | | | Since all k3 and legacy platforms share common load addresses for kernel and initrd in the fitImage, move them to top level ti-soc.inc. No functional change is intended from this patch. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: k3: update fitImage load addressAnshul Dalal2025-06-272-6/+4
| | | | | | | | | | | | | | | | | | | | | | | | | In yocto, the UBOOT_ENTRYPOINT and UBOOT_*LOADADDRESS variables specify the entry point and load addresses for the kernel image and the DTB when creating the fitImage[1]. Currently the load address for the kernel is set to 0x81000000 and 0x83000000 for the DTB for all k3 platforms. However the region 0x80080000 to 0x81880000 is reserved for OPTEE on am62xxsip-evm, leading to boot failure[2] when using the fitImage. This patch fixes the issue by changing the addresses to 0x82000000 for kernel and 0x88000000 for the DTB. This also allows us to load kernel images > 32MiB in size when not using initrd while also making the falcon and standard boot addresses consistent. [1]: https://docs.yoctoproject.org/ref-manual/variables.html#term-UBOOT_ENTRYPOINT [2]: https://raw.githubusercontent.com/ArchUsr64/ti_boot_logs/HEAD/am62xxsip-evm/failures/fitImage_load_addr_issue.log Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62xxsip: update kernel dtbsAnshul Dalal2025-06-271-1/+3
| | | | | | | | | | The new kernel dtb for am62x SiP have been merged to ti-linux-kernel as of f9579207b081 ("arm64: dts: ti: Add support for AM6254xxl SiP SK") on ti-linux-6.12.y-cicd. This patch modifies FIT_CONF_DEFAULT_DTB to pick the new dtb instead. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: optee: add build flags for am62xxsip-evmAnshul Dalal2025-06-271-0/+4
| | | | | | | | | | | | CFG_TZDRAM_START in OPTEE defines it's load address and is used to configure the page tables accordingly. Due to 512MiB DDR limitation of am62x SiP, the memory map has been modified with OP-TEE moved to bottom of DDR after atf to 0x80080000, this requires modifications to the OPTEE's CFG_TZDRAM_START. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: tfa: add build flags for am62xxsip-evmAnshul Dalal2025-06-271-0/+8
| | | | | | | | | | | Due to 512MiB DDR limitation of am62x SiP, the memory map has been modified with OP-TEE moved to bottom of DDR after atf to 0x80080000, this requires modifications to ATF's BL32_BASE. PRELOADED_BL33_BASE has also been updated to 0x82000000 to reflect the updated SPL_TEXT_BASE from u-boot. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62xxsip: update u-boot defconfig to am6254xxlAnshul Dalal2025-06-272-3/+5
| | | | | | | | | | | | | | | | | | | As of 35df864a0c26 ("configs: add defconfigs for am6254xxl") in ti-u-boot, new SiP sepcific defconfigs have been added with updated memory maps and OP-TEE load address. This requires changing the UBOOT_MACHINE variables inside machine configs for am62xxsip-evm. Note that AM6254xxl is the OPN for am62x SiP and expands as follows: AM6254XXL |||| |||+-- Feature Lookup (L indicates 512MiB of integrated LPDDR4) ||+--- Clock Speed |+---- Silicon PG Revision +----- Core configuration (4 indicates A53's in Quad core config) Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-bsp: Add TI TAD5212 DAC firmware recipeVishnu Singh2025-06-251-0/+2
| | | | | | | | | | | | | Add TAD5212 DAC firmware images for am62dxx-evm to support two DAC configurations: - tad5212_01.bin: Configures 1 DAC with stereo channel in i2s mode. - tad5212_04.bin: Configures 4 DAC with each having stereo channel support in i2s mode. Signed-off-by: Vishnu Singh <v-singh1@ti.com> Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Reviewed-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62pxx: Add support for HS-SE variantTelukula Jeevan Kumar Sahu2025-06-221-0/+3
| | | | | | | | | | | Since ti-u-boot supports HS-SE variant builds[1], Add support in the machine configurations to package this HS-SE variant tiboot3 binary in the built images. [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2025.01&id=75602edad16c840b2611afb9fc0e2718c026bb8a Signed-off-by: Telukula Jeevan Kumar Sahu <j-sahu@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux: Temporarily backport previous fitimage classesRyan Eatmon2025-06-102-2/+2
| | | | | | | | | | | | | | | A recent set of changes on oe-core has dramatically revamped the fitimage generation code. It is initially unclear how to fold those change into our flow, so in the short term we will copy the previous versions of the kernel bbclass files from a commit before [1] any changes to the class files. As soon as we figure it out, these files will be removed. This just help unblock anyone trying to build on master including meta-ti-bsp. [1] https://git.openembedded.org/openembedded-core/commit/?id=fdb0a51598156f99aa91f7495d7eada92a459e97 Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: conf: Package overlay for am62dxx-evmParesh Bhagat2025-06-041-0/+1
| | | | | | | | Package k3-am62a7-sk-edgeai.dtso for am62dxx-evm image. This overlay is required for audio analytics for am62dxx-evm. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: am62lxx: Do not deploy extra tiboot3.bin copyAndrew Davis2025-05-281-3/+0
| | | | | | | | | | | For AM62L there is no GP and both HS sub-types are supported by the same TIFS. This means we do not need multiple versions of tiboot3.bin. So no need to deploy an additional version which is identical to the default tiboot3.bin already deployed. Signed-off-by: Andrew Davis <afd@ti.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp : Add build support for am62dxx-evmParesh Bhagat2025-05-143-0/+41
| | | | | | | | | | | | | | | | | | | | | | | | | The AM62D SoC is a high-performance Digital Signal Processing (DSP) device with a quad-core Cortex-A53 cluster, dual Cortex-R5F cores, and a Cx7 DSP core with Matrix Multiplication Accelerator (MMA). It features a range of peripherals, including multichannel audio serial ports, Ethernet, UARTs, SPI, I2C, USB, and more. This SoC is part of K3-AM62x family, which includes the AM62A and AM62P variants. While the AM62A and AM62D are largely similar, the AM62D is specifically targeted for general-purpose DSP applications, whereas the AM62A focuses on edge AI workloads. A key distinction is that the AM62D does not include multimedia components such as the video encoder/decoder, MJPEG encoder, Vision Processing Accelerator (VPAC) for image signal processing, or the display subsystem. Additionally, the AM62D has a different pin configuration compared to the AM62A, which impacts embedded software development. The EVM board is a low-cost, expandable platform designed for the AM62D2 SoC, having 4GB LPDDR4 RAM, Gigabit Ethernet expansion connectors, audio jacks, USB ports, and more. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: k3: Add OP-TEE firmware TPM example TAAndrew Davis2025-05-131-1/+1
| | | | | | | | | | | This OP-TEE fTPM is a TA from Microsoft containing the reference implementation of the TPM 2.0 Specification. As K3 OP-TEE now has the necessary features supported to run this fTPM, enable it here. This will serve as an example of using OP-TEE on K3 as a TPM without needing an external harware TPM. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-linux-fw: Split firmware in to machine packagesAndrew Davis2025-05-134-4/+4
| | | | | | | | | | | | | | | | | | Firmware, like kernel modules, may be only relevant to a small subset of hardware. Shipping all firmware for all hardware can waste space. For this reason modules are split out into packages, and the same should be done for firmware. What we do currently is change the content of the package itself based on what device we are building for. Having a package change content for each machine means we cannot generate one image that supports multiple machines, nor host a common machine agnostic package repo. Instead we can generate different packages for the different firmwares and only include the firmware packages needed for each machine. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* bsp: u-boot: deploy tispl_falcon.bin to rootfsAnshul Dalal2025-05-131-0/+1
| | | | | | | | | | | | | Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage. This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in IMAGE_INSTALL when ti-falcon is enabled which allows us to deploy the required files to rootfs. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* bsp: conf: machine: add ti-falcon.incAnshul Dalal2025-05-132-0/+10
| | | | | | | | | | | ti-falcon.inc configures the following things for enabling falcon boot: 1. Change fitImage class to kernel-fitimage-legacyhs 2. Update kernel and dtb address for falcon boot 3. Disable kernel compression Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* am62: apply u-boot config fragment on ti-falconAnshul Dalal2025-05-134-0/+8
| | | | | | | | | The am62x_r5_falcon.config fragment in u-boot enables falcon boot support for R5 SPL, this patch enables the config fragment for am62a, 62p, 62x and 62lp evms based on ti-falcon distro override. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62axx: Exclude tiboot3.bin for GPChirag Shilwant2025-04-231-3/+0
| | | | | | | | | | | | * The GP variant of AM62A SoC was only used internally for initial device bring-up and is not publicly available. Hence, drop it from IMAGE_BOOT_FILES to ensure tiboot3-am62ax-gp-evm.bin is not packaged inside vfat boot partition of wic image Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am335x-evm: Bump up max_leb_cntChirag Shilwant2025-04-231-1/+1
| | | | | | | | | | New features added under meta-tisdk [0] require another increase to max_leb_cnt. [0]: https://github.com/TexasInstruments/meta-tisdk/commit/3985a7caeabe146dadc58fdb21e430d84642ee75 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62lxx-evm: Bump up max_leb_cntChirag Shilwant2025-04-231-1/+1
| | | | | | | | | | * New features added under meta-tisdk [0] require another increase to max_leb_cnt. * This patch fixes following errors observed with 11.00.09.04 tag on meta-tisdk, Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62xx-lp-evm: Add eqep overlayJudith Mendez2025-04-091-0/+1
| | | | | | | | This patch adds prefix string for eqep overlay to KERNEL_DEVICETREE_PREFIX. Signed-off-by: Judith Mendez <jm@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62: Add FIT_CONF_DEFAULT_DTBAnshul Dalal2025-03-255-0/+10
| | | | | | | | | | | | | | | | | FIT_CONF_DEFAULT_DTB config specifies the default dtb file for the FIT image when multiple ones are provided[1]. Since the variable is not set in current machine configs, the default is set to the first dtb read during FIT image creation which doesn't give us direct control over the default configuration. Therefore this patch adds default dtbs for am62 evms. [1]: https://docs.yoctoproject.org/ref-manual/variables.html#term-FIT_CONF_DEFAULT_DTB Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am57xx-evm: Enable gc320 machine feature for am57xxAntonios Christidis2025-03-201-3/+0
| | | | | | | | | MACHINE_FEATURE gc320, already gets set on omap-a15.inc. But ti-bsp.inc file, removes the feature. So, remove that portion of functionality from ti-bsp, in order to allow the building of gc320 in kernel 6.12. Signed-off-by: Antonios Christidis <a-christidis@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721e: Add BSP support for new out of tree moduleRyan Eatmon2025-03-131-1/+5
| | | | | | | | | | | | | The new out of tree module ti-vxe-vxd-driver is only for the 6.12 kernel and later. Since we support multiple BSPs we need to correctly wrap this addition behind some additional logic that can make sure to not include it for the 6.1 and 6.6 kernel builds where the module is still in the tree. Additionally, fix up the beaglebone-ai64 since it includes the j721e.inc file and will need to clear this variable for its BSPs as well. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721s2/j784s4: Fix overlays for DS90UB954Ryan Eatmon2025-03-112-2/+1
| | | | | | | | | | | | | | | | | | The previous commit incorrectly added the k3-j721s2-evm-ub954.dtbo to the KERNEL_DEVICETREE and it was missed during a quick review. The correct way to add dtbs is to add a prefix string to the KERNEL_DEVICETREE_PREFIX variable so that all files that match the string will be picked up. This allows for multiple kernels to be swapped out that may have different DTBs in their respective trees and not break a build. The upstream testing on the kernel will automatically update the KERNEL_DEVICETREE variable when the final kernel version is available. That way the KERNEL_DEVICETREE always points to what is available in the mainline. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721e: Fix overlays for DS90UB954Ryan Eatmon2025-03-111-1/+0
| | | | | | | | | | | | | | | | | | The previous commit incorrectly added the k3-j721e-evm-ub954.dtbo to the KERNEL_DEVICETREE and it was missed during a quick review. The correct way to add dtbs is to add a prefix string to the KERNEL_DEVICETREE_PREFIX variable so that all files that match the string will be picked up. This allows for multiple kernels to be swapped out that may have different DTBs in their respective trees and not break a build. The upstream testing on the kernel will automatically update the KERNEL_DEVICETREE variable when the final kernel version is available. That way the KERNEL_DEVICETREE always points to what is available in the mainline. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: J721e: Add Dependency for IMG DriverBrandon Brnich2025-03-071-1/+1
| | | | | | | | IMG codec drivers reside only on the J721e SoC. Ensure that the drivers are being built when building SDK. Signed-off-by: Brandon Brnich <b-brnich@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: k3: disable all fit signing for ubootBryan Brattlof2025-03-031-4/+0
| | | | | | | | | | All K3 SoCs utilize the binman packaging tools in U-Boot to package and sign the different boot firmware components needed to boot the various security variants of K3 platform. Disable UBOOT_SIGN_ENABLE to simplify the build Signed-off-by: Bryan Brattlof <bb@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721s2/j784s4: Pick overlays for DS90UB954Yemike Abhilash Chandra2025-02-262-0/+2
| | | | | | | | DS90UB954-Q1EVM can be used to connect FPDLink-III based sensors to TI EVMs. So pick the DS90UB954-Q1EVM overlay. Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721e-evm: Pick overlays for DS90UB954Yemike Abhilash Chandra2025-02-261-0/+1
| | | | | | | | DS90UB954-Q1EVM can be used to connect FPDLink-III based sensors to TI EVMs. So pick the DS90UB954-Q1EVM overlay. Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Update recipes to support jailhouse for am62lxxParesh Bhagat2025-02-141-0/+1
| | | | | | | | | | | | | Add am62lxx as compatible machine for ti-extras recipes and jailhouse recipes. This is to to control the kernel and u-boot repos, branches. So the am62lxx jailhouse build can be done by adding TI_EXTRAS=tie-jailhouse in local.conf. Update SRCREV and branch in ti-extras recipes for LTS migration. Also update jailhouse recipe to build and package jailhouse, cell files, device tree for inmate etc on am62lx image. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j722s: Change overlay in KERNEL_DEVICETREE_PREFIXAnurag Dutta2025-02-131-1/+1
| | | | | | | | | | | | | Currently, the overlay mentioned in KERNEL_DEVICETREE_PREFIX in case of j722s is "k3-j7200-evm-mcspi-loopback" which is incorrect. Change the overlay to "k3-am625-sk-mcspi-loopback.dtso" in order to carry out SPI loopback tests successfully. Fixes: 13b691a9bc2d ("conf: machine: j722s: Add overlay to KERNEL_DEVICETREE_PREFIX") Signed-off-by: Anurag Dutta <a-dutta@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sgx-ddk-km: bump revision for kernel 6.12Randolph Sapp2025-02-101-4/+3
| | | | | | | | | | | Bump the source revision to allow this module to work on kernel 6.12. Originally this was going to be a separate branch, but considering the bsp selector logic, this makes just as much sense. Also enable the sgx driver in the ti_6.12 bsp selector. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62lxx-evm: Add logic to generate UBI filesystem imagesChirag Shilwant2025-02-071-0/+6
| | | | | | | | Add logic to generate UBI filesystem images which can be used to directly flash into the NAND’s file-system partition. Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add Support for AM62LChirag Shilwant2025-02-072-0/+25
| | | | | | | | | - Add machine configuration for am62lxx-evm - Add TFA, OPTEE, firmware & u-boot overrides Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> 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>
* 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>
* 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-bsp: Disable GC320 support conditionally on BSP versionAndrew Davis2025-01-221-0/+15
| | | | | | | | | | | | 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>
* linux-ti-staging: Drop systest kernelAndrew Davis2025-01-221-1/+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-221-1/+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-221-2/+2
| | | | | | | 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: beagleplay*: Update defaults to mainlineRyan Eatmon2025-01-222-10/+5
| | | | | | | | | 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 to version: v6.12Ryan Eatmon2025-01-222-1/+5
| | | | | | | | | 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>
* conf/machine: move remaining Beagle platforms to meta-beagleDenys Dmytriyenko2024-12-164-134/+0
| | | | | | | 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-162-50/+2
| | | | | | | | | | | 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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-24 10:16:27 +0000