summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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-202-2/+2
| | | | | | | 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>
* pru-icss: update QA checksTrevor Woerner2023-08-231-2/+2
| | | | | | | | | | | Update the QA checks done on the build artifacts to include [buildpaths] since the PRU linker includes these paths in its output. This avoids build warnings or errors of the type: pru-icss-6.2.0-r1 do_package_qa: QA Issue: File /lib/firmware/pru/PRU_Halt.out in package pru-icss-halt contains reference to TMPDIR [buildpaths] Signed-off-by: Trevor Woerner <twoerner@gmail.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>
* linux-ti-next,conf/machine: Add support for new vendored dts dircicd.master.202308040100Ryan Eatmon2023-07-316-2/+15
| | | | | | | | | | The latest kernel has made the change to add vendor subdirectories into the arch/arm/boot/dts directory. This effectively breaks the KERNEL_DEVICETREE settings in the machine configs for 32bit platforms, so switch them over to using the PREFIX variable. Also change the linux-ti-next to use the PREFIX setting for KERNEL_DEVICETREE. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-kernel-devicetree-prefix: Add search function for DTBMERGERyan Eatmon2023-07-311-1/+21
| | | | | | | | With the change to the vendored arch/arm/boot/dts directory, we need to add support to the KERNEL_DEVICETREE_DTBMERGE to make it a search pattern instead of a fixed list. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: Add missing links and reformat file for consistencycicd.master.202307280100cicd.master.202307270100cicd.master.202307260100cicd.master.202307250100Ryan Eatmon2023-07-241-159/+194
| | | | | | | | Add in missing *-sec links pointing to signed files especially for j784s4. Reformat file a little to make the groupings easier to manage in the future when looking to see if -sec links are missing. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: Remove rwx patchcicd.master.202307240100cicd.master.202307221943Ryan Eatmon2023-07-222-48/+0
| | | | | | | Upstream meta-arm has picked up support for what this patch was doing, it can be removed. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am65xx: Remove SYSFW_SUFFIX from non-k3r5 configsAndrew Davis2023-07-212-4/+0
| | | | | | | This definition is only needed in the "-k3r5" multiconfig files. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: Remove old and no longer used MACHINE_FEATURESAndrew Davis2023-07-215-5/+5
| | | | | | | | | | The following MACHINE_FEATURES are not matched against anywhere, remove: * kernel26 * ethernet * mmc Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: Remove leftover UIO Device Tree overlay filesAndrew Davis2023-07-212-4/+0
| | | | | | | We do not use UIO anymore, remove these files. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: Update to v2.9 release tagKamlesh Gurudasani2023-07-211-2/+2
| | | | | | | | | Update to latest release tag, i.e. v2.9 https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=d3e71ead6ea5bc3555ac90a446efec84ef6c6122 Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202307210100LCPD Automation Script2023-07-211-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.202307210100LCPD Automation Script2023-07-211-2/+2
| | | | | | | | Updated the value(s) for: PV SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* k3conf: CI/CD Auto-Merger: cicd.master.202307210100LCPD Automation Script2023-07-211-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.202307210100LCPD Automation Script2023-07-211-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* meta-ti: conf: am62xx-lp-evm: Use common include am62xx.incPraneeth Bajjuri2023-07-182-16/+1
| | | | | | | | | | | | | | | | commit 5f9be228390b ("machine: Add AM62Q HS-SE evm configuration") has added am62xx-lp.inc which is used by am62xx-lp-evm machine. The features listed in am62xx.inc are common between machines am62xx-evm and am62xx-lp-evm. (Ex: MACHINE_FEATURES = "gpu") Hence updating the necessary include file to have common features to be enabled between these two platform variants. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Suggested-by: Randolph Sapp <rs@ti.com> Reviewed-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.202307180100LCPD Automation Script2023-07-181-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.202307180100LCPD Automation Script2023-07-181-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.202307180100LCPD Automation Script2023-07-181-1/+1
| | | | | | | Updated the value(s) for: SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-img-rogue-*: bump srcrev for jacinto fixesRandolph Sapp2023-07-112-2/+2
| | | | | | | | | | | | | | | | | | | | | Bump the SRCREV for the umlibs and driver package to include some fixes for Jacinto devices. These patches do the following: - Fix virtual memory addressing - Resolve an issue with APM and debug requests - Attempt to resolve most of the cache coherency related issues on Jacinto devices - Introduce some extra cache maintenance operations in the kernel module It also introduces the following known issues: - Visual artifacting on the second-to-last EGL/GLES context on BXS based devices (J721S2/J784S4) We're still working on that last one, but the stability improvements make this worth while for now. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: k3: Use ARM64 kernel load address in FITAndrew Davis2023-07-071-2/+2
| | | | | | | | | | | | | | | The address 0x80008000 was used in pre-K3 devices. ARM64 requires the kernel loaded to a 2MB aligned address when not using KASLR. For FIT set the address to 0x81000000 which gives the kernel 32MB before running into the FDT at 0x83000000. If you get this error someday then your kernel is too large and either it or FDT needs relocated in memory: ERROR: image is not a fdt - must RESET the board to recover. Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-09-26 15:32:20 +0000