| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
Add the PWM overlays: k3-am62x-sk-dmtimer-pwm and k3-am62x-sk-pwm
for AM62 LP SK.
Signed-off-by: Judith Mendez <jm@ti.com>
|
|
|
|
|
|
|
|
|
| |
This package provides Linux-side components for TI IPC and depends on
virtual/kernel Linux kernel for the build, so it is not compatible with
non-Linux builds, such as k3r5 baremetal multiconfig. Hence adjust
COMPATIBLE_HOST accordingly.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The V3Link camera fusion board [1] can be used to connect upto 4
OV5640 sensors to SK-AM62A.
Overlays for interfacing OV5640 sensor with V3Link are built
as part of the TI linux kernel. Pick these in the BSP filesystem.
[1]: https://www.arducam.com/product/arducam-v3link-camera-kit-for-ti-development-boards/
Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
|
|
|
|
|
|
|
|
|
| |
This IPC example is no longer supported nor recommended for new designs.
The documentation is no not available either (was on Processors Wiki).
Remove this example.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
Add a SECURITY file with hints for security researchers and other
parties who might report potential security vulnerabilities.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
u-boot-ti-staging_2024.04: SRCREV
linux-ti-staging-rt_6.6: SRCREV
linux-ti-staging_6.6: SRCREV
Changelogs:
u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=1d8a15d0fb56ae479dd3c11e3b17d7434b079acd..2a7de06d57399e04738573622cbdaa3532e7ab4d
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=4143633c95dc50cb5e2c695629d8b6302ef8de81..d7b6ee144955d71f1c3d29b7dc08619961f12d64
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=399452cd6d8ff30967ddc4baa444afd32cbbedeb..118cf0c8b392bed94437f1519de10b63705dbacd
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
|
| |
Bump versions of mesa-pvr and ti-sgx-ddk-km to support SGX with kernel
6.6 and the same version of mesa rogue is using.
Enable SGX by default in the 6.6 BSP provider section logic.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update to commit 58b25570c9ef91753b14c2103f45f4be9dddb696, which adds
the DM_MANAGED suspend feature.
https://git.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a.git/+/58b25570c9ef91753b14c2103f45f4be9dddb696
Also change the docs/license.rst checksum. The license file was
modified to include a reference to the pydevicetree project which uses
the Apache License 2.0.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
| |
The mesa.inc that we inherit from oe-core now has the required
parameters. This conditional append is no longer required.
This reverts commit dbc6afc46e55b247606dfad5238137c8fa807843.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
Backport two fixes from the latest mesa project to fix two builds issues
related to newer llvm versions.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
Backport two fixes from the latest mesa project to fix two builds issues
related to newer llvm versions.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: CNM_WAVE521_FW_VERSION,TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION
u-boot-ti-staging_2024.04: SRCREV
u-boot-ti-staging_2024.10: SRCREV
linux-ti-staging-rt_6.6: SRCREV
linux-ti-staging_6.12: PV,SRCREV
linux-ti-staging_6.6: SRCREV
Changelogs:
ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=ddb9cc251ace41dfad6650390f82e4a389d3967e..7179a74d1ed38e581bcd35e7b05632955e962c30
u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=cdac8b4cd3cc1d1e9ac6354c1cfe03ddbbdf01fa..1d8a15d0fb56ae479dd3c11e3b17d7434b079acd
u-boot-ti-staging_2024.10: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=c97ada2dc66934ee00a7a03d9ed078bdfb7b4039..f919c3a889f0ec7d63a48b5d0ed064386b0980bd
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=517163f797b81a8277a000d6a1c9dfd89b3711b8..4143633c95dc50cb5e2c695629d8b6302ef8de81
linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=9852d85ec9d492ebef56dc5f229416c925758edc..f8f8c0b547f67d2d4d653cc59753f85275ff54f2
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=32ae7316ddc6d9b6bb0d87706cf7daa44c4c1e92..399452cd6d8ff30967ddc4baa444afd32cbbedeb
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
|
| |
PREFERRED_VERSION matches against the PV in the recipe, not against the
file name. With the upcoming 6.12, the 6.1 kernel version string was a
little too loose. The "6.1%" could glob onto the 6.12 recipe. Take
this time to also clean up a couple of the other versions and narrow
them down.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
Add bsp-ti-6_12 overrides in A53 & R5 machine configuration
to ensure it picks the appropriate u-boot configs for beagleplay
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Enable TRNG in J722s, as bugs related to TRNG has been fixed now.
Following firmwares have the fix [0]
[0]: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/commit/?h=ti-linux-firmware-next&id=d9177916332be8887398d20e12ad48a9faa6cc9c
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
| |
Update all of the components to the upstream 4.4.0 version.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
We are planning on adding upstream u-boot testing against stable tagged
versions of u-boot and need a little more control over telling bitbake to
not point at a branch but point to a tag.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
| |
Update to the latest u-boot release v2024.10.
Additionally, take this time to clean up the mainline recipe and
streamline it a bit.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
| |
Our upstream testing needs to point to both master and master-next and
we need two different recipes to track that. This recipe mirrors the
linux-ti-next recipe and points to the master-next branch for the latest
bleeding edge changes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was suggested to move the reproducibility patches out of
ti-kernel.inc and into the respective recipes.
Taking this time to also rework all of the pieces that go into the SRC_URI
and create a standardization for how all of the kernel recipes are done.
Create KERNEL_GIT_URI, KERNEL_GIT_PROTOCOL, KERNEL_GIT_BRANCH,
KERNEL_DEFCONFIG, and KERNEL_REPRODUCIBILITY_PATCHES. The default for
the above new variables is to the git.ti.com repository and how we manage
the kernel settings. The other kernel recipes that do something other than
how TI does it can simply override the variables.
This change will make it easier to perform the upstream testing that we
do on a nightly basis. Additionally, it will simplify the auto generation
of the patches to move the mainline (stable kernel) recipes since the
required patches will be all done in the same recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
am57xx-evm: KERNEL_DEVICETREE
am62axx-evm: KERNEL_DEVICETREE
am62pxx-evm: KERNEL_DEVICETREE
am62xx-evm: KERNEL_DEVICETREE
am62xx-lp-evm: KERNEL_DEVICETREE
am68-sk: KERNEL_DEVICETREE
am69-sk: KERNEL_DEVICETREE
beagleplay: KERNEL_DEVICETREE
am64xx-evm: KERNEL_DEVICETREE
am65xx-evm: KERNEL_DEVICETREE
am335x-evm: KERNEL_DEVICETREE
am437x-evm: KERNEL_DEVICETREE
j7200-evm: KERNEL_DEVICETREE
j721e-evm: KERNEL_DEVICETREE
j721e-sk: KERNEL_DEVICETREE
j721s2-evm: KERNEL_DEVICETREE
j722s-evm: KERNEL_DEVICETREE
j784s4-evm: KERNEL_DEVICETREE
linux-ti-mainline: PV,SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Resolve some issues with J721E and compressed NPOT (Non-Power-Of-Two)
textures.
Also, add some additional allocation tracking in render process specific
tasks.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We got a bit more time to do a proper migration this time. A discovery
period to see what actually works and boy, it wasn't much.
This update resolves issues with:
- Macro redefinition
- Sparse NPOT texture allocations
- vec4 reductions
- Mesa image extensions
- Buffer allocations under weston
- Devices with both a RENDER and PRIMARY display node
- Underprivileged users being unable to allocate buffers
- Removed call to drm_map_legacy
- Replace deprecated kernel calls
- Fix some cache attributes for userspace allocations
- About 40 other various errors and warnings
This core was never fully GLES2 conformant. In fact, if you try to run
cts on any of the older releases you'll find yourself in a hardware
recovery loop pretty quickly. We've gotten it to about 94.2% conformance
with these patches.
There are still dragons here, but they are at least a little more
manageable.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION
u-boot-ti-staging_2023.04: SRCREV
u-boot-ti-staging_2024.04: SRCREV
linux-ti-staging-rt_6.1: SRCREV
linux-ti-staging-rt_6.6: SRCREV
linux-ti-staging_6.1: SRCREV
linux-ti-staging_6.6: SRCREV
Changelogs:
ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=64248dad39a9448ad191bc04130c49e0354cb2ce..ddb9cc251ace41dfad6650390f82e4a389d3967e
u-boot-ti-staging_2023.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=7044504f44002fe46b4598420852033d335d56c7..0853d7725220d59130d8bcc59d01151cba64ffa0
u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=b78dde22088773147d80c3b85c885d9be7a2bfab..cdac8b4cd3cc1d1e9ac6354c1cfe03ddbbdf01fa
linux-ti-staging-rt_6.1: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=258616ead12edc4acf7ac38e741d588b372144e4..451df8c0a2a3bcf0656b2f6fdc49d6fb4d05f186
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=d05688f353d10af170286db56535443184202eab..517163f797b81a8277a000d6a1c9dfd89b3711b8
linux-ti-staging_6.1: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=da449d8c3cf600b0346a6696e1e3cc431422e765..92ce8d7d2ab679e10c1dda309a0fb2ceae78b908
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=325ad3650d0b50a4943b9151fb43411f08ad5d0c..32ae7316ddc6d9b6bb0d87706cf7daa44c4c1e92
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
| |
The next Yocto Project release is called walnascar and OE-Core master branch
is now marked accordingly. Add layer compatibility with walnascar.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were missing controlling the versions for linux-ti-staging-rt and
linux-ti-staging-systest using the BSP framework. Since the
PREFERRED_VERSION is not tied to the virtual/kernel we need two
additional settings for those alternate kernel package names.
For BSPs that do not have the -rt and -systest recipes then the two
new variable settings should effectively be ignored and cause no issues.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
| |
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: TI_LINUX_FW_SRCREV
u-boot-ti-staging_2023.04: SRCREV
linux-ti-staging-rt_6.1: PV,SRCREV
linux-ti-staging_6.1: PV,SRCREV
Changelogs:
ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=821faad142f51304bf2f8e0526838f17dc247825..64248dad39a9448ad191bc04130c49e0354cb2ce
u-boot-ti-staging_2023.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=83660642085462346fbeb410f83bc99448ec7042..7044504f44002fe46b4598420852033d335d56c7
linux-ti-staging-rt_6.1: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=96b0ebd82722d16e9ab646cd3a73080e6f790747..258616ead12edc4acf7ac38e741d588b372144e4
linux-ti-staging_6.1: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=c1c2f1971fbf6ddad93a8c94314fe8221e7aa6be..da449d8c3cf600b0346a6696e1e3cc431422e765
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
| |
Update all of the components to the upstream 4.3.0 version.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
There was a change to the return value for a function pointer in the
kernel v6.11. This patch adapts the module to the kernel change.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
| |
Add new BSP for the 6.12 kernel and u-boot 2024.10 versions.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
Adding needed recipe for initial testing and development of the 2024.10
version of u-boot for the next LTS.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
Adding needed recipes for initial testing and development of the 6.12
kernel for the next LTS.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will prevent a lot of noise on the build logs.
Currently we have some erros:
rm: cannot remove 'file'
No such file or directory
Like the following:
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5 /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5-2024.04+git-r0
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5-2024.04+git-r0*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5-2024.04+git-r0*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5-2024.04+git-r0*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5-2024.04+git-r0*'
| : No such file or directory
| + true
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: TI_LINUX_FW_SRCREV
u-boot-ti-staging_2024.04: SRCREV
linux-ti-staging-rt_6.6: PV,SRCREV
linux-ti-staging_6.6: PV,SRCREV
Changelogs:
ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=35fa44a93549d8d91b1c37a7b9f8767dbe7d37eb..821faad142f51304bf2f8e0526838f17dc247825
u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=7986fd679935818d0ef11e6a334377df178774f6..b78dde22088773147d80c3b85c885d9be7a2bfab
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=85d46cfcef8242e37cbd99a6591cab2b90d0d8ed..d05688f353d10af170286db56535443184202eab
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=d5b1bee95de93e6ab87e73242c20910e7d7d3d83..325ad3650d0b50a4943b9151fb43411f08ad5d0c
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
| |
The upcoming SRCREV change to the linux-ti 6.6 kernel version no longer
needs these two patches, and they are blocking the CICD promotion being
in place.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
Last user was dspdce-fw which is removed. Remove this now unused
support library.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
| |
This was an attempt to run the DCE server firmware on the DSP instead
of on the IPU M4 cores. Not widely used and not used at all anymore,
remove the firmware for this.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CMEM has been deprecated for removal for some time now. All users should
have migrated to the Linux upstream DMA-BUF Heaps framework. Remove CMEM.
We have already removed the CMEM kernel module but left the CMEM userspace
recipe to prevent breaking meta-arago builds which had some leftover
packages that still had a dependency on it. Nothing we now build still
needs this now so drop it out also.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- While implementing k3.inc, there was an assumption that all
k3 based TI SOC's would always have a Cortex-R5F core [1]. This
assumption is not true.
- Hence, create a new mc_k3r5 include file & move the multiconfig
dependencies to it. Also, include this file only in those k3 platforms
which needs the R5 multiconfig support.
[1]: https://git.ti.com/cgit/arago-project/meta-ti/commit/conf/machine/include/k3.inc?h=scarthgap&id=f814840465358a6b5429ad20165742ac6e6e6a29
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
A recent change in oe-core [1] to refactor the uboot flow allows for a more
targeted refactoring of our override code as well.
Additionally, fix the UBOOT_CONFIG code to work correctly for k3r5
builds.
[1] https://git.openembedded.org/openembedded-core/commit/?id=e29d006a118643b276c6977cb70b0fb56635fc33
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
u-boot-ti-staging_2024.04: SRCREV
linux-ti-staging-rt_6.6: SRCREV
linux-ti-staging_6.6: SRCREV
Changelogs:
u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=818c76aed67f94059b9ebb94d237418802620b81..7986fd679935818d0ef11e6a334377df178774f6
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=f9bceb7343387ac6fab003518f1cd31987d6eb05..85d46cfcef8242e37cbd99a6591cab2b90d0d8ed
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=db88712931433e92a5f73cec57c82c5c7ebee593..d5b1bee95de93e6ab87e73242c20910e7d7d3d83
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
| |
Remove openmp-rtos component as deprecated and not maintained.
This used to provide OpenMP DSP runtime components for legacy devices.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
openembedded-core commit f5cfb3e23603 ("mesa: set PV from the .inc
file and not via filenames") now sets PV in the mesa.inc file
explicitely to whatever version oe-core is using.
Override that setting to the actual version here to prevent the
following parse error and whatever else would go wrong afterwards.
| ERROR: .../mesa-pvr_23.2.1.bb: Unable to get checksum for mesa-pvr SRC_URI entry 0001-meson-Disable-cmake-dependency-detector-for-llvm.patch: file could not be found
| The following paths were searched:
| .../meta-ti-bsp/recipes-graphics/mesa/mesa-pvr-24.0.7/bsp-ti-6_1/0001-meson-Disable-cmake-dependency-detector-for-llvm.patch
| ...
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update to latest release tag, i.e. v2.11.
Also update the LIC_FILES_CHKSUM since the license file changed since
the last SRCREV change.
Commit:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a/+/f2735ebccf5173f74c0458736ec526276106097e
Tag:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a/+/refs/tags/v2.11
Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
Tested-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: PRUETH_FW_AM65X_SR2_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION
u-boot-ti-staging_2024.04: SRCREV
k3conf: SRCREV
linux-ti-staging-rt_6.6: SRCREV
linux-ti-staging_6.6: SRCREV
Changelogs:
ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=af745923679b12f9872ed43e510e74335149de1c..35fa44a93549d8d91b1c37a7b9f8767dbe7d37eb
u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=79b13d5cb02d619cfb1842ee28ea2e7b77be54cc..818c76aed67f94059b9ebb94d237418802620b81
k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=85a7433202aafafbccea8a7b2491f4df8b1ecd80..30a1d5b2d08c0da39d4e62b3ebee591a9882fa21
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=30b405326c30368375e58551f85c9e531ec4aef2..f9bceb7343387ac6fab003518f1cd31987d6eb05
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=15f828fd0fc706919f64551afbe431eb66ba927f..db88712931433e92a5f73cec57c82c5c7ebee593
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
| |
omapzoom has been down since a long time. Point the repository to the
mirror in git.ti.com
Reported-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
Update the entry for KERNEL_DEVICETREE to match what is in the 6.10
kernel.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
| |
Update to the latest u-boot release v2024.07.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A compile error has apperaed when building againt the v6.10 kernel.
git/debugss_module/debugss-mod/debugss_kmodule.c:1149:34: error: array type has incomplete element type 'struct of_device_id'
1149 | static const struct of_device_id dra7xx_debugss_of_match[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~
The easy fix is just to add an include for the header that defines the
missing struct.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|