| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
ti-linux-kernel tree has several prune config fragments for ARM/ARM64/RT
configurations. Enable the prune config fragments here.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Acked-by: Andrew Davis <afd@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All current K3 devices use either A53 or A72. Use the compile tune
configuration specific for these to allow the compiler to make
better optimizations.
Default tune here is weakly set to a lowest common denominator of
aarch64, as before, which is a recommended behavior for a BSP layer.
This allows for greater binary reuse (packages, sstate, etc.) across
different platforms of the same architecture in multi-BSP environments.
At the same time, since all the correct tunes are now configured for
K3 devices, one can elevate compiler optimization levels either from
local.conf or own Distro configuration on a per-SoC or per-device
basis, like so:
DEFAULTTUNE:k3 = "armv8a-crc"
DEFAULTTUNE:j721e = "cortexa72-cortexa53"
DEFAULTTUNE:beagleplay = "cortexa72-cortexa53"
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
| |
Rather than override the value for SPL_BINARY for all bsps, simply just
set the value to the correct value. This should be ok since all
beaglebone-ai64 variations should use tispl.bin_unsigned.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
| |
The defaults for UBOOT_MACHINE and SPL_BINARY are now aligned with the
mainline values and new ti-6_1 values for the previous defaults were
created to capture those. Also updated the meta-beagle beagleplay since
it inherits the beagleplay-ti settings.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
| |
The ti-cgt-arm compiler is a custom TI compiler. It does not
currently support reproducible builds and is provided via a
binary blob download that we cannot patch in the recipe to
address the issue.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update SRCREV to pick up patch that fixes some compile errors:
../git/memplugin_linux.c: In function 'memplugin_alloc':
../git/memplugin_linux.c:69:9: error: implicit declaration of function 'dsp_dce_buf_lock' [-Wimplicit-function-declaration]
69 | dsp_dce_buf_lock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~~~~~
../git/memplugin_linux.c:71:9: error: implicit declaration of function 'dce_buf_lock' [-Wimplicit-function-declaration]
71 | dce_buf_lock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~
../git/memplugin_linux.c: In function 'memplugin_free':
../git/memplugin_linux.c:91:17: error: implicit declaration of function 'dsp_dce_buf_unlock' [-Wimplicit-function-declaration]
91 | dsp_dce_buf_unlock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~~~~~~~
../git/memplugin_linux.c:93:17: error: implicit declaration of function 'dce_buf_unlock' [-Wimplicit-function-declaration]
93 | dce_buf_unlock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~~~
../git/memplugin_linux.c:95:13: error: implicit declaration of function 'close'; did you mean 'pclose'? [-Wimplicit-function-declaration]
95 | close(h->dma_buf_fd);
| ^~~~~
| pclose
and
../git/libdce_linux.c: In function 'dce_deinit':
../git/libdce_linux.c:90:9: error: implicit declaration of function 'close'; did you mean 'pclose'? [-Wimplicit-function-declaration]
90 | close(OmapDrm_FD);
| ^~~~~
| pclose
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
There were some errors related to ipk postinst. The issues were fixed
by going to the update-alternatives class instead of trying to create
the steps directly in the recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
The script that sends the automated patch does not currently handle
updating the KERNEL_REPRODUCIBILITY_PATCHES variable with the changes in
the patches.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
am65xx-evm: KERNEL_DEVICETREE
j722s-evm: KERNEL_DEVICETREE
linux-ti-mainline: PV,SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Like we do with GPU support, GC320 support is conditional on the
kernel we are building and so should be disabled here for kernels
on which it is not functional yet.
We can then remove these disabling lines as the driver is updated
for each supported kernel, instead of blanket disabling in the
distro layer as done currently.
Signed-off-by: Andrew Davis <afd@ti.com>
|
|
|
|
|
|
|
|
|
| |
This might have been useful for building development packages with
the pre-built binaries for deployment elsewhere, but there are
better ways to do this and these are no longer consumed. Remove
this packaging step.
Signed-off-by: Andrew Davis <afd@ti.com>
|
|
|
|
|
|
|
|
|
| |
This might have been useful for building development packages with
the pre-built binaries for deployment elsewhere, but there are
better ways to do this and these are no longer consumed. Remove
this packaging step.
Signed-off-by: Andrew Davis <afd@ti.com>
|
|
|
|
|
|
|
|
|
| |
This was used when the kernel had a different configuration for
the testing kernel. This has not been the case since v5.10 so
drop the systest kernel package as it will be the same as the
normal kernel package now.
Signed-off-by: Andrew Davis <afd@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We are moving to 6.12 to be our new LTS, so we are switching the default
BSP to that. You can still access the 6.6 kernel if you need to by using
the BSP system and setting TI_PREFERRED_BSP = "ti-6_6" in your
local.conf.
Current known issues:
- Hardware graphics is disabled until we get a patch that updates the
patches to work with the 6.12 kernel. Falling back to software
rendering.
- am62xxsip-evm and j742s2-evm are not supported in the 2025.01 u-boot
yet. They will fail to build until the u-boot recipe is updated to
point to a commit that fixes their support.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
We are moving to 2025.01 for the next LTS, so rename the previous ltsprep
recipe and update it.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
| |
There was a fix for "buildpaths" QA error in master that got backported
to scarthgap, but out of 2 references to the new UNPACKDIR, one got
corrected, but the other one was left behind. Since scarthgap has no
notion of UNPACKDIR, replace it with corresponding WORKDIR.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
| |
Add missing SECURITY file required by yocto-check-layer.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
Rogue graphics driver 24.1 currently fails to build against the kernel
that enables FORTIFY_SOURCE, such as bb.org. Disable this config for now,
until the driver is fixed.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
|
| |
Most Beagle platforms are switching to 6.6 based Linux kernel and U-boot
2024.10. Add corresponding recipes and extend beagle-bsp with required
settings.
BeagleY-AI for now remains on 6.1 BSP with U-boot 2023.04.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
| |
Rename "bb_org" BSP recipes to include version in the recipe names.
This way we can support multiple versions.
Also remove 2 unused kernel patches that were needed for 5.10
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
| |
Add machine configuration for BeagleY-AI platform.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
| |
Update Beagle BSP to the latest 6.1.83 kernel version.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
| |
Move "bb_org" kernel and U-boot providers that use corresponding official
BeagleBoard.org trees into own meta-beagle layer.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
| |
Include beagle-bsp.inc to define "bb_org" BSP settings and select that
as a default.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Extract "bb_org" BSP specific settings from beagleplay-ti in meta-ti-bsp and
move them to own beagleplay machine config in meta-beagle.
The differences between 2 configs are minimal, hence beagleplay in meta-beagle
inherits beagleplay-ti from meta-ti-bsp as a base and only adjusts what's
needed.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
| |
Define "bb_org" default BSP settings in meta-beagle layer that all Beagle
platforms will use.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
| |
OE-Core master has switched from lz4c to lz4 host tool, but a corresponding
change only appears in kernel 6.13. Since bb.org kernels 6.1 and 6.6 enable
LZ4 compression by default, also add a legacy lz4c tool in the list.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
| |
The new meta-beagle will host all supported Beagle platforms that
use TI SoCs and hence need to depend on meta-ti-bsp. The default
BSP for the platforms in this layer will use BeagleBoard.org
official trees for the Linux kernel and U-boot.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BeaglePlay is officially supported by TI "ti-6_6" BSP and is part
of the TI-SDK releases. Switching BSP to BeagleBoard.org "bb_org"
settings for the same machine is possible within the same layer.
But having different machine configs for the same machine name in
multiple layers can be confusing and prone to errors. Hence rename
the config to indicate BeaglePlay with official TI support in order
to re-use the canonical name in a separate layer.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
|
| |
Early Boot of remote processors is supported at the SPL stage of the
bootloader. Currently, SPL looks for the remoteproc firmwares in the
boot partition.
Therefore, add the rproc firmware to the boot partition of wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
|
|
|
|
|
|
|
|
|
| |
Early boot of remote processors from SPL stage of bootloader requires
the remoteproc firmware to be present in the boot partition. Deploy this
rproc IPC firmware so that it can be copied to the boot partitions of
the wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the latest TIFS fix [1], AM62P is able to leverage the hardware-TRNG
instead of having to fallback into the software-PRNG.
Background:
The default priv-id for A53 cores in SYSFW for AM62P was chosen to be 4
while the other K3 SOCs were configured at 1. Any firewall TISCI API
call that used 1 would not be able to run on AM62P. The TIFS fix changes
the AM62P value from 4 to 1.
[1] -
https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/commit/?h=ti-linux-firmware&id=98de0a4290ec200cc224d4a5a6f42d2126230e2f
Signed-off-by: Aashvij Shenai <a-shenai@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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=f704a778526ba38fa6c80b0374ea82a9424292f6..29d0c23d67ee7b88e46fe1753cd020e2b04c2ef6
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=e4498d814c9caa50b260bf1d31e981a23c8ec59f..c79d7ef3a56ff61dd83d5527520b419a4f0e32e2
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=d32074b73785eb57c675cef603517247f5f4f33b..a7758da17c2807e5285d6546b6797aae1d34a7d6
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: TI_LINUX_FW_SRCREV
u-boot-ti-staging_2023.04: SRCREV
u-boot-ti-staging_2024.04: SRCREV
linux-ti-staging-rt_6.1: PV,SRCREV
linux-ti-staging-rt_6.6: PV,SRCREV
linux-ti-staging_6.1: PV,SRCREV
linux-ti-staging_6.12: 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=0ae7605a6916edc146d103eeaf7c41f2cf237a4f..1eaf07dc4ec5cdeb98078f17a9d4635e88f43f75
u-boot-ti-staging_2023.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=0853d7725220d59130d8bcc59d01151cba64ffa0..0893e693e08f9fc864a6191051dccc818accf933
u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=a970f6e51043e6c41cc33ef18be78123994d806e..f704a778526ba38fa6c80b0374ea82a9424292f6
linux-ti-staging-rt_6.1: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=451df8c0a2a3bcf0656b2f6fdc49d6fb4d05f186..194ebd939bee3ffff36de9cf8dff28a77c671f5b
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=8e9437778527f81a4e34d6ed1982d487b51fe396..e4498d814c9caa50b260bf1d31e981a23c8ec59f
linux-ti-staging_6.1: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=92ce8d7d2ab679e10c1dda309a0fb2ceae78b908..4ef41ca7ad952c7b13b7e40808ab1025796f9a6c
linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=f8f8c0b547f67d2d4d653cc59753f85275ff54f2..ade72d105eb7c9a2a4addfd0204eb4551b8efa7a
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=541c20281af79a7df96bb94b4e3a923092d7ceff..d32074b73785eb57c675cef603517247f5f4f33b
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
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=95ec0608717727d17a97b7e51cd78d00d9c5d6e5..0ae7605a6916edc146d103eeaf7c41f2cf237a4f
u-boot-ti-staging_2024.04: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=2a7de06d57399e04738573622cbdaa3532e7ab4d..a970f6e51043e6c41cc33ef18be78123994d806e
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=b1a3afa3f5ce6da352debfa490dc410ecf63a19b..8e9437778527f81a4e34d6ed1982d487b51fe396
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=31f84fe16e6518d14c2f5e21631de19f161274db..541c20281af79a7df96bb94b4e3a923092d7ceff
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: TI_LINUX_FW_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=7179a74d1ed38e581bcd35e7b05632955e962c30..95ec0608717727d17a97b7e51cd78d00d9c5d6e5
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=d7b6ee144955d71f1c3d29b7dc08619961f12d64..b1a3afa3f5ce6da352debfa490dc410ecf63a19b
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=118cf0c8b392bed94437f1519de10b63705dbacd..31f84fe16e6518d14c2f5e21631de19f161274db
Signed-off-by: LCPD Automation Script <lcpdbld@list.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=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:
linux-ti-staging-rt_6.6: SRCREV
linux-ti-staging_6.12: SRCREV
linux-ti-staging_6.6: SRCREV
Changelogs:
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=9b67993ce6023909325ba366f07d88e37ab60d42..4143633c95dc50cb5e2c695629d8b6302ef8de81
linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=b0e715522353879e6c3c1b56dafad6fb681b1e55..f8f8c0b547f67d2d4d653cc59753f85275ff54f2
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=e3b431a6194fc1b074802d20c9eede8442382b2a..399452cd6d8ff30967ddc4baa444afd32cbbedeb
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
linux-ti-staging-rt_6.6: SRCREV
linux-ti-staging_6.6: SRCREV
Changelogs:
linux-ti-staging-rt_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=71c08e13f47a4b7e5fa65f1219544ae059b0efc7..9b67993ce6023909325ba366f07d88e37ab60d42
linux-ti-staging_6.6: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=126a8167b5915c6014b6a7d2b3bc710b040739b6..e3b431a6194fc1b074802d20c9eede8442382b2a
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>
|