summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp
Commit message (Collapse)AuthorAgeFilesLines
...
* Revert "recipes-bsp: u-boot-ti.inc: Remove ti-sci-fw from DEPENDS for k3 ↵Aniket Limaye2023-10-121-0/+1
| | | | | | | | | | machine" This reverts commit cd13cafd659f7784f4131fd0bafb8a3c7c9ef126. Some devices need ti-fs-stub-* firmware for the uboot aarch64 build Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Remove COMPATIBLE_MACHINE and extend recipe to k3 machinesAniket Limaye2023-10-121-2/+4
| | | | | | | | | | | | | Revert ebcf15bf0f31208e87ce60a4696e585940b46777 : "recipes-bsp:ti-sci-fw: Add k3r5 as COMPATIBLE_MACHINE" Extend recipe to k3 machines too, to provide ti-fs-stub-* firmware for u-boot aarch64 build. Update do_deploy() to allow multiconfig builds for k3 machines Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* amx3-cm3: use debug-prefix-mapDan McGregor2023-10-121-1/+1
| | | | | | | Fixes the QA warnings about package contains reference to TMPDIR. Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* uboot: Handle UBOOT_CONFIG for multiple R5 defconfigsGarrett Giordano2023-10-111-2/+20
| | | | | | | | | | | Currently the do_compile step fails if we try to implement UBOOT_CONFIG in an attempt to build U-Boot with multiple R5 defconfigs. This commit adds a condition to handle linking the UBOOT_BINARY if UBOOT_CONFIG is used in place of UBOOT_MACHINE. Signed-off-by: Garrett Giordano <ggiordano@phytec.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: Correctly fix SPL binary name for SD/MMC media on HS boardscicd.master.202310120100Ryan Eatmon2023-10-091-3/+30
| | | | | | | | | | The previous patch is incorrectly accepted and released. This patch applies the logic that was discussed on the mailing list. - Create a new variable grouping for SPL_HS_MLO - Update the install/deploy code to reference the new variables. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202310090100cicd.master.202310090100LCPD Automation Script2023-10-091-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-ti-staging-rt_6.1: CI/CD Auto-Merger: cicd.master.202310090100LCPD Automation Script2023-10-091-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* k3conf: CI/CD Auto-Merger: cicd.master.202310090100LCPD Automation Script2023-10-091-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot-ti-staging_2023.04: CI/CD Auto-Merger: cicd.master.202310090100LCPD Automation Script2023-10-091-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-linux-fw: CI/CD Auto-Merger: cicd.master.202310090100LCPD Automation Script2023-10-091-1/+1
| | | | | | | Updated the value(s) for: TI_LINUX_FW_SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot: set the correct latest LIC_FILES_CHKSUM genericallyDenys Dmytriyenko2023-10-053-5/+1
| | | | | | | | | | | | | | | The common u-boot-ti.inc file still uses the old license checksum from 2021 U-boot. There were formatting changes in the license text between 2021 and 2023 and version-specific recipes had the license checksum updated to the new value. Since there are no 2021 recipes remaining, the new license checksum can be set in the common .inc file generically. Note: U-boot license hasn't changed and the same checksum is simply being moved from the recipes to the common .inc file. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: Update to sha fixing deep sleep on AM62xKamlesh Gurudasani2023-10-051-1/+1
| | | | | | | | | | | Update to commit d7a7135d32a8c7da004c0c19b75bd4e2813f9759, which fixes deep sleep bug on AM62x https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=d7a7135d32a8c7da004c0c19b75bd4e2813f9759 Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com> Tested-by: Dhruva Gole <d-gole@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-dm-dw: Preserve structure of the deployed ti-dm-fw binariesAniket Limaye2023-10-051-3/+3
| | | | | | | | | | | Preserve the directory structure of the deployed dm firmware so that one can directly specify the deploy directory for binman based u-boot build. Additionally, this makes it easier to preserve the same structure inside the prebuilt-images directory of the tisdk-core-bundle for the same reason. Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Deploy the fw binaries to the deploy directoryAniket Limaye2023-10-051-0/+11
| | | | | | | | Deploy the sysfw binaries to the DEPLOYDIR, to be picked up by the tisdk-core-bundle... for the prebuilt binaries directory Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: Fix SPL binary name for SD/MMC media on HS boardsJulien Panis2023-09-291-3/+3
| | | | | | | | | The SPL binary built by u-boot for SD/MMC/eMMC media on HS platforms is u-boot-spl_HS_MLO. Thanks to this fix, the binary is properly installed and deployed. Signed-off-by: Julien Panis <jpanis@baylibre.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-bsp:ti-sci-fw: Add k3r5 as COMPATIBLE_MACHINEAniket Limaye2023-09-291-0/+1
| | | | | | | This recipe only provides the sysfw binaries compiled for the r5 Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-bsp: u-boot-ti.inc: Remove ti-sci-fw from DEPENDS for k3 machineAniket Limaye2023-09-291-1/+0
| | | | | | | | ti-sci-fw should be needed by the binman u-boot build only for the k3r5 machines and not for the k3 machines Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: Install OP-TEE OS provided TAsAndrew Davis2023-09-291-0/+6
| | | | | | | | | OP-TEE OS provides a handful of TAs itself. While these are often meant to be built-in, when they are not we should deploy them as part of the OP-TEE OS package so they can be loaded at runtime. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-umlibs: harden handling of usrmergeMax Krummenacher2023-09-291-1/+3
| | | | | | | | | | Only move directories which haven't already been moved. This prevents a build error should a subsequent bitbake execution rerun do_install where the sources to 'mv' no longer exist. | mv: cannot stat 'ti-img-rogue-umlibs/23.1.6404501/git/targetfs/am62_linux/lws-generic/release/lib/firmware': No such file or directory Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging: am335x/am437x: Add no_smp optioncicd.master.202310050100cicd.master.202310030100Praneeth Bajjuri2023-09-294-0/+8
| | | | | | | | | | | | | | | | | | multi_v7_defconfig that is used for legacy platforms enables SMP by default. Platforms like am335x and am473x are single core platforms that doesnt need this option to be enabled. This config cannot go in multi_v7_defconfig as well, since there will be systems like am57x/dra7x or other community platforms which can have multiple arm cores. Adding the provision to disable SMP configuration for applicable platforms like am335x and am437x. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202309290100cicd.master.202310020100cicd.master.202309290100LCPD Automation Script2023-09-291-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-ti-staging-rt_6.1: CI/CD Auto-Merger: cicd.master.202309290100LCPD Automation Script2023-09-291-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* k3conf: CI/CD Auto-Merger: cicd.master.202309290100LCPD Automation Script2023-09-291-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot-ti-staging_2023.04: CI/CD Auto-Merger: cicd.master.202309290100LCPD Automation Script2023-09-291-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-linux-fw: CI/CD Auto-Merger: cicd.master.202309290100LCPD Automation Script2023-09-291-1/+1
| | | | | | | Updated the value(s) for: TI_LINUX_FW_SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-bb.org: update to 5.10.168 for armv7a targetsAnthony J. Martinez2023-09-262-35/+4
| | | | | | | | | | | | | | | | | | | | | Updates SRCREV, PV, and BRANCH for armv7a targets and fixes failure to mount /boot when using poky with systemd. The kernel selected supports VFAT without initramfs as noted here - https://lists.yoctoproject.org/g/meta-ti/message/16913 Removes defconfig patch setting LZMA, as the new kernel already defaults to LZ4. Tested by running `bitbake core-image-base` with this patchset, and then booting a pair of Beaglebone Black devices from the resulting image. Prior to the change, systemd boots to a maintenance mode having failed to mount /boot. After the change, the system boots normally and /boot is mounted. Suggested-by: Robert Nelson <robertcnelson@gmail.com> Signed-off-by: Anthony J. Martinez <anthony@ajmartinez.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ipc: ti-rpmsg-char: Update library to 0.6.3Hari Nagalla2023-09-251-3/+3
| | | | | | | | Update library to 0.6.3 as it adds support for AM62P SoC. Signed-off-by: Hari Nagalla <hnagalla@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: cleanup leftover alternative entries for JacintoDenys Dmytriyenko2023-09-251-12/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Jacinto platforms use first R5 MCU core for DM firmware. When DM firmware was split out into own recipe[1], ALTERNATIVE_TARGET entries got removed from ti-rtos-firmware recipe, but corresponding ALTERNATIVE_LINK_NAME entries remained, causing warnings. Clean up those now. [1] https://git.yoctoproject.org/meta-ti/commit/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb?id=b21d29d94694ac49b97a1f4ba428c7d8cd6fb64a Fixes these warnings: | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7-mcu-r5f0_0-fw or /usr/lib/firmware/j7-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7-mcu-r5f0_0-fw: /usr/lib/firmware/j7-mcu-r5f0_0-fw.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7-mcu-r5f0_0-fw == /usr/lib/firmware/j7-mcu-r5f0_0-fw | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7200-mcu-r5f0_0-fw or /usr/lib/firmware/j7200-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7200-mcu-r5f0_0-fw: /usr/lib/firmware/j7200-mcu-r5f0_0-fw.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7200-mcu-r5f0_0-fw == /usr/lib/firmware/j7200-mcu-r5f0_0-fw | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j721s2-mcu-r5f0_0-fw or /usr/lib/firmware/j721s2-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j721s2-mcu-r5f0_0-fw: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw == /usr/lib/firmware/j721s2-mcu-r5f0_0-fw | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j784s4-mcu-r5f0_0-fw or /usr/lib/firmware/j784s4-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping... | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j784s4-mcu-r5f0_0-fw: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw == /usr/lib/firmware/j784s4-mcu-r5f0_0-fw | WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-mainline: update to the latest 2023.07Ryan Eatmon2023-09-251-2/+2
| | | | | | Update to the latest release version. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-next: Update to v6.6-rc3 next versionRyan Eatmon2023-09-251-3/+3
| | | | Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: switch k3r5 multiconfig to baremetalDenys Dmytriyenko2023-09-252-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are couple of k3r5 components that need to be built for the target and they are self-contained and don't use glibc. Moreover, when building a cross-compile toolchain for k3r5, there's no need to build glibc and all its dependencies. While build-time speed up is nice, the main benefit comes when packaging a nativesdk toolchain for distribution, reducing the number of packages and the resulting size of the toolchain installer. To avoid potential namespace conflict in package feeds between nativesdk binary packages of Linux glibc and k3r5 baremetal toolchains, adjust the package suffix accordingly. This also requires a rather impactful change in the deployment structure, which affects CIs and user experience. By default different TCLIBC builds (e.g. glibc and baremetal in this case) are built in separate TMPDIRs to avoid conflicts, especially on the nativesdk side. Also the default config has DEPLOY_DIR residing under corresponding TMPDIR. Of course, this can be changed by local.conf or <distro>.conf, which meta-ti-bsp has no control over. Unlike multiconfig-image-packager example that can access deployed artifacts across multiconfigs to package in an image, we use wic and its IMAGE_BOOT_FILES list to package a final image. Unfortunately, wic cannot access deployed artifacts across multiconfigs in separate TMPDIRs, as it uses DEPLOY_DIR_IMAGE to collect the artifacts. To overcome this, we need to set up a "common" deploy directory for images and sdks produced by multiconfigs, which is located outside of TMPDIRs, set by TI_COMMON_DEPLOY variable that can be changed or adjusted by distros as needed. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: Patches for LLVM 17 supportRyan Eatmon2023-09-253-0/+188
| | | | | | | There are a number of issues in gallium when moving to LLVM 17. These patches fix those compile issues. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* k3r5: u-boot: prevent overlapping deployed SPL symlinksDenys Dmytriyenko2023-09-252-16/+3
| | | | | | | | | | | | Make sure shortname R5 SPL symlink is not the same as the main K3 SPL one, as they will overlap/overwrite each other when deployed into a common location. Latest code in master now checks for this and errors out. Also remove unused UBOOT_SPI_* variables. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Add am62xxsip-evm configurationChirag Shilwant2023-09-202-0/+29
| | | | | | | | | | - Add A53 and R5 machine configurations for am62xxsip-evm. - Use UBOOT_CONFIG_FRAGMENTS as am62xsip_sk_r5.config in R5 machine configuration. This will ensure we build u-boot-r5 with baseconfig as am62x_evm_r5_defconfig and config fragment as am62xsip_sk_r5.config. Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Reviewed-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-bsp: u-boot: Add u-boot-mergeconfig.inc to handle fragment u-boot configChirag Shilwant2023-09-202-0/+8
| | | | | | | | | | | | | | | | - U-boot recipe in OE-Core supports out-of-tree config fragments that are passed via SRC_URI and automatically merges all *.cfg files as fragments. This makes specifying config fragments in the machine configuration a bit difficult. Hence, add a logic which will ensure we handle u-boot config fragments using a new variable UBOOT_CONFIG_FRAGMENTS. - The u-boot-mergeconfig.inc will allow us to build u-boot with list of config fragments specified in UBOOT_CONFIG_FRAGMENTS along with the base defconfig mentioned in UBOOT_MACHINE. - Include u-boot-mergeconfig.inc in u-boot-ti.inc Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti: layer.conf: add compatibility with nanbieldDenys Dmytriyenko2023-09-201-1/+1
| | | | | | | OE-Core is switching layer compatibility to nanbield for the upcoming release. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: add dynamic-layer append for llvmpipeRandolph Sapp2023-09-202-0/+18
| | | | | | | | | | | | | | | Meta-clang provides a bbappend for mesa to use clang to accelerate it's rasterization with runtime code generation through the use of llvmpipe. With the addition of mesa-pvr we no longer get this for free with the blanket mesa bbappend on the devices that explicitly request mesa-pvr so lets add a dynamic layer to append the same args meta-clang does. Though the number of devices that would select pvr-mesa and still want to use software rendering is small, it's not zero due to debug and testing purposes. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202309200100cicd.master.202309200100LCPD Automation Script2023-09-201-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-ti-staging-rt_6.1: CI/CD Auto-Merger: cicd.master.202309200100LCPD Automation Script2023-09-201-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot-ti-staging_2023.04: CI/CD Auto-Merger: cicd.master.202309200100LCPD Automation Script2023-09-201-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* conf/am65xx-hs-evm: Fix UBOOT_MACHINE to match u-boot configRyan Eatmon2023-09-052-2/+2
| | | | | | | | The uboot config for am65 is moving to a merged build for both GP and HS. Until the yocto configs catch up, we need to keep am65xx-hs-evm working. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* k3conf: Update SRCREV and move to cmakecicd.master.202309010100Ryan Eatmon2023-08-301-9/+3
| | | | | | | The SRCREV change corresponds to a commit that changes from make to cmake for building k3conf, so we need to update the recipe as well. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202308290957cicd.master.202308290957LCPD Automation Script2023-08-291-2/+2
| | | | | | | | Updated the value(s) for: PV SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux-ti-staging-rt_6.1: CI/CD Auto-Merger: cicd.master.202308290957LCPD Automation Script2023-08-291-2/+2
| | | | | | | | Updated the value(s) for: PV SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot-ti-staging_2023.04: CI/CD Auto-Merger: cicd.master.202308290957LCPD Automation Script2023-08-291-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-linux-fw: CI/CD Auto-Merger: cicd.master.202308290957LCPD Automation Script2023-08-291-1/+1
| | | | | | | Updated the value(s) for: TI_LINUX_FW_SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-img-rogue-umlibs: Reset INHIBIT_DEFAULT_DEPSRyan Eatmon2023-08-291-0/+2
| | | | | | | | | | | | | | | A recent change to oe-core [1], has caused a pile of QA errors during packaging for this binary package. The effect of the change in oe-core was to remove the dependency on the compiler and other compiler adjacent libraries. But the binary packages need some of the compiler tools as part of the packaging flow (ie. objdump). Until the above gets reverted, this patch will fix the issue and can be reverted itself once oe-core is fixed. [1] https://git.openembedded.org/openembedded-core/commit/?h=master&id=d1d09bd4d7be88f0e341d5fccbfbefeb98d4b727 Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/k3: switch mcdepends from do_image_completeDenys Dmytriyenko2023-08-231-1/+1
| | | | | | | | | | Previously k3 mcdepends for k3r5 artifacts has been changed from do_image_wic to support non-wic builds in other layers and do_image_complete was believed to be sufficient. Switching k3r5 to baremetal builds has exposed another race when some pieces come from sstate and hence requires using do_image instead. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am335x-evm and am437x-evm: bump max_leb_cntRyan Eatmon2023-08-231-1/+1
| | | | | | New features added require another increase to max_leb_cnt. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: ti33x: Add earlycon parameter to kernel command lineJulien Panis2023-08-231-0/+1
| | | | | | | | | Sometimes on am335x devices, no more output is printed after "Starting kernel..." message. Modify UBOOT_EXTLINUX_KERNEL_ARGS to enable the console before standard serial driver is probed. Signed-off-by: Julien Panis <jpanis@baylibre.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-09-29 19:28:22 +0000