summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp
Commit message (Collapse)AuthorAgeFilesLines
...
* recipes-bsp: Add DM_FIRMWARE override for am62pxx display clusterChirag Shilwant2025-05-132-0/+2
| | | | | | | | | | | | | | * For AM62P display cluster usecase, we need to pick "dss_display_share.wkup-r5f0_0.release.strip.out" from ti-linux-firmware [0] Hence, pick the display cluster firmware only when DISPLAY_CLUSTER_ENABLE is set to 1. * When DISPLAY_CLUSTER_ENABLE is not set to 1, fallback to pick the "ipc_echo_testb_mcu1_0_release_strip.xer5f" DM firmware. [0]: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/tree/ti-dm/am62pxx?h=11.00.12 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-linux-fw: Split firmware in to machine packagesAndrew Davis2025-05-135-38/+46
| | | | | | | | | | | | | | | | | | 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>
* ti-linux-fw: Set INHIBIT_DEFAULT_DEPSAndrew Davis2025-05-134-6/+3
| | | | | | | | | Firmware here are not built, no need for C compiler nor std libs. Add INHIBIT_DEFAULT_DEPS=1 and remove the same from all recipes that include this file. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-eth-fw: Only include information for supported machinesAndrew Davis2025-05-131-17/+1
| | | | | | | | These other machines are not compatible with this recipe, no need to setup definitions for these. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp recipes: fix whitespace warningsMax Krummenacher2025-05-133-3/+3
| | | | | | | | | | | | | | | | Since OE bitbake commit 24772dd2ae6c ("parse/ConfHandler: Add warning for deprecated whitespace usage"), the current build generates the following warning (as example): | WARNING: ...meta-ti/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb: | meta-ti/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb:2 | has a lack of whitespace around the assignment: | 'HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC"' Fix all the warnings. Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* bsp: tfa: add build flags for ti-falconAnshul Dalal2025-05-131-0/+1
| | | | | | | | | | | | | In falcon mode, ATF jumps straight to the linux kernel which requires a 2MiB aligned load address. Hence this patch changes the ATF jump address (PRELOADED_BL33_BASE) to a 2MiB aligned value 0x82000000 and the DTB address (K3_HW_CONFIG_BASE) to 0x88000000. These values are chosen to be consistent with the addresses used by u-boot when booting in the normal flow. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* bsp: u-boot: deploy tispl_falcon.bin to rootfsAnshul Dalal2025-05-132-0/+3
| | | | | | | | | | | | | 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-133-0/+22
| | | | | | | | | | | 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>
* recipes-bsp: Add DM_FIRMWARE override for am62axxChirag Shilwant2025-04-292-0/+2
| | | | | | | | | | | | | | | | | | | | * With [0], the EdgeAI DM R5 firmware for am62axx will now be maintained at ti-linux-firmware. Until now, the same firmware was maintained on psdk_fw [1] with a different name & fetched in TI SDK via meta-edgeai [2] * Hence, add a am62axx specific override for DM_FIRMWARE inorder to match the firmware name as maintained in "ti-dm/am62axx" of ti-linux-firmware. [0]: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/commit/?h=ti-linux-firmware&id=eee26bfeb6469af30e5309ba8859e9b65670fcc3 [1]: https://git.ti.com/cgit/processor-sdk/psdk_fw/ [2]: https://git.ti.com/cgit/edgeai/meta-edgeai/tree/recipes-tisdk/ti-psdk-rtos/ti-edgeai-firmware.bb?h=EDGEAI_CICD_20250417 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-ti: ti-rtos-echo-test-fw: Add C7X_1_FW override for am62axxChirag Shilwant2025-04-291-14/+15
| | | | | | | | | | | | | | | | | | | | * With [0], the C7x IPC EdgeAI firmware for am62axx will now be maintained at ti-linux-firmware. Until now, the same firmware was maintained on psdk_fw [1] with a different name & fetched in TI SDK via meta-edgeai [2]. * Hence, add a am62axx specific override for C7X_1_FW inorder to match the firmware name as maintained in "ti-ipc/am62axx" of ti-linux-firmware. [0]: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/commit/?h=ti-linux-firmware&id=1e5d64d9385d6472d29e11ac7021765004ddff27 [1]: https://git.ti.com/cgit/processor-sdk/psdk_fw/ [2]: https://git.ti.com/cgit/edgeai/meta-edgeai/tree/recipes-tisdk/ti-psdk-rtos/ti-edgeai-firmware.bb?h=EDGEAI_CICD_20250417 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-bsp: u-boot: Fix PACKAGECONFIG[dm] argumentsChirag Shilwant2025-04-291-1/+1
| | | | | | | | | | | | | | | | | | | * As observed in the u-boot makefile [0][1], the argument anticipated by u-boot binman is "TI_DM" instead of "DM". Hence, fix the same in meta-ti-bsp. * The behavior went unnoticed until now because "ti-dm" was still being sourced from BINMAN_INDIRS, which referred to "ti-linux-firmware" and the PACKAGECONFIG[dm] feature was redundant. [0]: https://github.com/u-boot/u-boot/blob/v2025.01/Makefile#L1408 [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/Makefile?h=ti-u-boot-2025.01#n1409 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Acked-by: Andrew Davis <afd@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>
* recipes-bsp: u-boot: Remove do_install from bootsplash imageChirag Shilwant2025-04-231-10/+0
| | | | | | | | | | | | | * U-Boot reads the bootsplash image file from the vfat boot partition & displays it during boot-up showcasing early splash screen support. * There's no significance of having an additional do_install as the logo file need not be added in the rootfs/image. * Fixes 277f04df4c94de44bcea95b46d59cf057f571e45 & 1fed958bfe8a8825996134f62097ac02206f43b2 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* bsp: fitimage-legacyhs: add default dtb supportAnshul Dalal2025-04-231-7/+16
| | | | | | | | | | | | | | | | | FIT_CONF_DEFAULT_DTB config specifies the default dtb file for the FITimage when multiple ones are provided[1]. Legacyhs fitimage does not currently support this feature set which is required for repurposing the same class for falcon boot. This patch adds support for FIT_CONF_DEFAULT_DTB without affecting existing platforms that rely on legacyhs fitImage. [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>
* ti-hsm-demo-fw: Add a recipe to export prebuilt HSM demo firmwareBeleswar Padhi2025-04-233-0/+29
| | | | | | | | | | Add a recipe to deploy the HSM demo firmware to the DEPLOYDIR, to be picked up by the tisdk-core-bundle for the prebuilt binaries directory. This firmware is then further picked by U-Boot and packaged inside tispl.bin FIT image for loading the HSM M4 core in applicable SoCs. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-mainline: Update to version: v2025.04LCPD Automation Script2025-04-231-4/+2
| | | | | | | | Updated the value(s) for: u-boot-ti-mainline: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* 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>
* mesa-pvr: add local copy of mesa.incMax Krummenacher2025-04-233-2/+382
| | | | | | | | | | | | | | OE-core updated mesa to 25.0.2 [1]. The resulting mesa.inc file no longer matches mesa recipes building older versions. Copy the mesa.inc version from before the update renamed to mesa-pvr.inc to work around the issue. | ../git/meson.build:21:0: ERROR: Value "softpipe" for option "gallium-drivers" is not in allowed choices: "auto, kmsro, radeonsi, r300, r600, nouveau, freedreno, swrast, v3d, vc4, etnaviv, tegra, i915, svga, virgl, panfrost, iris, lima, zink, d3d12, asahi, crocus, pvr, sgx, all" [1] https://git.openembedded.org/openembedded-core/commit/?id=f9eb0468e45ee5a6a3b3195ef5e78c328c4347c9 Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202504100100cicd.master.202504100100LCPD Automation Script2025-04-103-3/+3
| | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV u-boot-ti-staging_2025.01: SRCREV linux-ti-staging_6.12: SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=27003b6bff61a55dd1fff2cc777e5e07b092b1f7..c3ad8113c766bee7b8ddfae222e9b8017b565ea3 u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=cd91d73601810374d16a1f17505ab2e72e31f75d..70667128cb5b2c2a7621965ba948b5a56a2e756f linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=c85877d40f8e70e1e201eca2ae1648781f238a37..cdcaeac783e31f18edb6cb44b526228f44023b45 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* CI/CD Auto-Merger: cicd.master.202504090937cicd.master.202504090937LCPD Automation Script2025-04-093-3/+3
| | | | | | | | | | | | | Updated the value(s) for: atf: SRCREV_tfa u-boot-ti-staging_2025.01: SRCREV 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=e7eeb7586fab6cd9e91d49d5b5ad68287d9bc8b6..cd91d73601810374d16a1f17505ab2e72e31f75d linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=1ac80adecb8ebffa654be744e5e5f7343b0abf78..c85877d40f8e70e1e201eca2ae1648781f238a37 Signed-off-by: LCPD Automation Script <lcpdbld@list.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>
* optee-client: remove patch that got accepted upstreamDenys Dmytriyenko2025-04-081-0/+4
| | | | | | | | meta-arm adds a patch that was sent and accepted upstream, remove it since mta-ti pulls a more recent verstion. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-driver: resolve issues with fdinfoRandolph Sapp2025-04-011-1/+1
| | | | | | | | | | | | | Bump the srcrev to include a fix for events where the driver is requested to show advanced information about file descriptors that are associated with the device but are not currently associated with a rendering task. This should address the kernel fault in pvr_show_fdinfo associated with fdinfo/lsof. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sgx-ddk-um: fixup packageconfig paramsRandolph Sapp2025-04-011-4/+15
| | | | | | | | | | Fix the package config params to make it obvious what combinations are allowed. Also, rework the way we are inheriting init related classes so that we don't accidentally do any additional postinstall steps. While we're at it, don't execute anything for the compile or configure stage. Signed-off-by: Randolph Sapp <rs@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>
* ti-linux-fw: Split out SRC_URI into variablesRyan Eatmon2025-03-241-1/+5
| | | | | | | | To facilitate better testing we need to control all aspects of the SRC_URI. Create TI_LINUX_FW_GIT_URI, TI_LINUX_FW_GIT_PROTOCOL, and TI_LINUX_FW_GIT_BRANCH and build SRC_URI using them. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202503210100cicd.master.202503210100LCPD Automation Script2025-03-214-5/+5
| | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV atf: SRCREV_tfa u-boot-ti-staging_2025.01: SRCREV linux-ti-staging_6.12: SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=1faf5974a93eb35ac31ed27e5693739edb08824c..27003b6bff61a55dd1fff2cc777e5e07b092b1f7 u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=c8badfb165815c648052309418987f302e48aeef..e7eeb7586fab6cd9e91d49d5b5ad68287d9bc8b6 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=8c8cc002ab65149491f9b75cadfaeb2342150800..1ac80adecb8ebffa654be744e5e5f7343b0abf78 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* recipes-graphics: port gc320 libs to work on kernel 6.12Antonios Christidis2025-03-201-2/+6
| | | | | | | | | The user mode libraries needed recompiling with the scarthgap revision of gcc to remove all the warnings about 32bit API usage during the linking stage, new SRCREV includes this changes. Versions of the libraries remain the same. Signed-off-by: Antonios Christidis <a-christidis@ti> 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>
* recipe-graphics: port gc320 driver to work on kernel 6.12Antonios Christidis2025-03-201-2/+2
| | | | | | | | | Changes made on the gc320 kernel mode driver in order to work with kernel 6.12. There is no other change in functionality with this update, and the driver version remains the same. Signed-off-by: Antonios Christidis <a-christidis@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ipc: ti-rpmsg-char: Update library to 0.6.9Praneeth Bajjuri2025-03-201-3/+3
| | | | | | | | | | | | | update from 0.6.7 to 0.6.9. This update brings the following fixes from ti-rpmsg-char repo. 09b064c src: fix misc warnings 5a9ec97 src: fix warnings for resource leak & string null b4ef987 Fix Werror=stringop-truncation dabdc21 lib: Fix klockwork warnings Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sgx-ddk-km: rework preferred_target selectionRandolph Sapp2025-03-201-1/+1
| | | | | | | | | | | Bump SRCREV to include a patch that changes the way compiler_preferred_target is selected for a given toolchain. This now checks specified SYS_CFLAGS to see if hardfloat is set explicitly and will override the default target selection if necessary. Signed-off-by: Randolph Sapp <rs@ti.com> Tested-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: drop custom handling of embedded TAscicd.master.202503181422Francesco Valla2025-03-171-5/+2
| | | | | | | | | | | | | | | | | | | | | The meta-arm layer, which is the provider of the base recipe for optee-os, added [1] a separate optee-os-ta package for the embedded TAs that are compiled as part of the OPTEE OS build process. However, the TI overrides for optee-os include the embedded TAs inside the base package, leaving the optee-os-ta package empty (and thus not installable). Align to the meta-arm behaviour and simply add a runtime dependency on optee-os-ta for optee-os. While keeping backward compatibility, this allows to install only the embedded TAs - reducing the required disk space - on platforms on which the OPTEE OS is loaded from an external boot image rather than being fetched from the root filesystem, like the K3 SoCs. [1] https://patchwork.yoctoproject.org/project/arm/patch/20230630112340.3314395-1-r.czerwinski@pengutronix.de/ Signed-off-by: Francesco Valla <francesco@valla.it> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-encode-decode: bump revision to fix build failureBrandon Brnich2025-03-171-1/+1
| | | | | | | | Out-of-tree module failing to build against linux-next as a result of changes to platform driver remove function. Signed-off-by: Brandon Brnich <b-brnich@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-driver: fix os amp interactionsRandolph Sapp2025-03-171-1/+1
| | | | | | | | | | | Fix OS APM interactions when uninitialized. Because this driver uses lazy initialization, if the GPU is never given a task it will not be initialized. Even if the device is not fully initialized it is still registered with the DRM subsystem and capable of receiving OS APM signals. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: zephyr-fw: Update Zephyr to latest with AM64xx supportAndrew Davis2025-03-171-1/+3
| | | | | Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202503140100cicd.master.202503140100LCPD Automation Script2025-03-143-5/+5
| | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: PRUETH_FW_AM65X_SR2_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION u-boot-ti-staging_2025.01: SRCREV linux-ti-staging_6.12: SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=e089c2f8db0577aa4acd3b3ef3ab229be2e804e1..1faf5974a93eb35ac31ed27e5693739edb08824c u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=baf3aaa8ecfa20b9d9f497621b6c11915223f502..c8badfb165815c648052309418987f302e48aeef linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=1a22c2fb64485a5dea9a9247eb007ddd4ea8a81d..8c8cc002ab65149491f9b75cadfaeb2342150800 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* CI/CD Auto-Merger: cicd.master.202503131229cicd.master.202503131229LCPD Automation Script2025-03-131-1/+1
| | | | | | | Updated the value(s) for: atf: SRCREV_tfa Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-img-rogue-umlibs: ship module blacklistRandolph Sapp2025-03-131-8/+15
| | | | | | | | | | | | | Well, this is the evil vendor driver. Time to start acting like it. Blacklist the upstream powervr module if this driver is present. This patch also does away with the bin_package components. It was cool and found some interesting bugs, but we might as well start leveraging that Makefile more now that we're starting to get some more common files between devices. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: ti-img-encode-decode: Out-of-Tree Recipe CleanupBrandon Brnich2025-03-131-2/+2
| | | | | | | | | | Module recipe is missing SUMMARY and a proper SRC_URI leading to warnings during the build process. Fixes: 296344c8 ("ti-bsp: ti-img-encode-decode: Add Recipe for Building VXE-VXD Out-of-Tree Module") Reported-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Brandon Brnich <b-brnich@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>
* ti-rpmsg-char: Change to COMPATIBLE_MACHINERyan Eatmon2025-03-131-2/+1
| | | | | | | | | Rather than using COMPATIBLE_HOST move to using COMPATIBLE_MACHINE to limit the recipe to being TI specific. Also, this package is "k3" specific so further limit it down to just those matching machines and not all TI SOCs. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202503111223cicd.master.202503111223LCPD Automation Script2025-03-114-8/+8
| | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: PRUETH_FW_AM65X_SR2_VERSION,TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION atf: SRCREV_tfa u-boot-ti-staging_2025.01: SRCREV linux-ti-staging_6.12: PV,SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=e38a05e2ef5f6a6f2387742864042beba01972bb..e089c2f8db0577aa4acd3b3ef3ab229be2e804e1 u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=9c89e8b0a82fabe55c6366aa65eb987f05bb4472..baf3aaa8ecfa20b9d9f497621b6c11915223f502 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=6423e6bb6191982da1c09a21a46c68b494f5b1b5..1a22c2fb64485a5dea9a9247eb007ddd4ea8a81d Signed-off-by: LCPD Automation Script <lcpdbld@list.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>
* ti-bsp: ti-img-encode-decode: Add Recipe for Building VXE-VXD Out-of-Tree ModuleBrandon Brnich2025-03-071-0/+23
| | | | | | | | | | During 10.0 LTS bringup, the decision was made that it would be the last LTS that carried the IMG VXE and VXD driver in tree. Driver is now hosted on git.ti.com. This recipe is responsible for pulling in the driver, building it, and packaging it within the J721e 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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-23 15:30:16 +0000