| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
k3conf: SRCREV
Changelogs:
k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=6700e5a7f417c1bb19daf2422b880a82b7315543..3de294db4f2cd75404f358768f4be8f8fa3132d7
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add support for dtbs that are generated by merging multiple .dtb and .dtbo
files in the /boot directory of the root filesystem.These merged device trees
are defined in ti-linux-kernel Makefile[1]. Include them using the
KERNEL_DEVICETREE_DTBMERGE variable.
[1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm64/boot/dts/ti/Makefile?h=ti-linux-6.12.y
Signed-off-by: Telukula Jeevan Kumar Sahu <j-sahu@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
The BL32_BASE address is properly set in TF-A to jump to OP-TEE's
entrypoint for the am62lxx SoC family, so we can safily drop this.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch introduces udev rules to ensure consistent device naming for
VPU decoders, encoders, and the JPEG encoder. These rules are essential
for enabling hardware-accelerated video decoding in Chromium using the
V4L2 Stateful decoder.
The following udev rules are added:
- Map vpu and vpu0 to /dev/video-dec0 and /dev/video-enc0.
- Map vpu1 to /dev/video-dec1 and /dev/video-enc1.
- Map the JPEG encoder to /dev/jpeg-enc0.
These changes ensure proper operation of the VPU and JPEG encoder,
especially when other video devices are connected, avoiding mismatches.
Signed-off-by: Thorsten Lannynd <t-lannynd@ti.com>
Reviewed-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: TI_LINUX_FW_SRCREV
atf: SRCREV_tfa:am62lxx
u-boot-ti-staging_2025.01: SRCREV
k3conf: SRCREV
linux-ti-staging-rt_6.12: PV_ARM32,SRCREV_ARM32
linux-ti-staging_6.12: PV,SRCREV
Changelogs:
ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=6506f9e1e5d8d62e9dd70123fae04bd07b90bcd5..33b0116556a8a57e8e456a99e45e8736db7652f3
u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=556593b8d5f39ad77327d2e7aa190d3faae5a350..f3f8c664b3001e40cbdf46687732b2c37e1b6b33
k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=4e8df1a41a1437b61562836e9478e8069d1a071c..6700e5a7f417c1bb19daf2422b880a82b7315543
linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=6246158ffbe4dfc005258a52780956f8baf04574..9085e19579dfb5074d05000dcca3b9b7d8afb106
linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=fe4718a972cfcac11933e98f5a3986e084a7c43f..10c7960f9cf6c5e3ed0c8865596e07540bf9ba1b
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
| |
The PRC script missed this. All recipes need a SUMMARY.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Newer silicon revision of the AM62L family are capable of reliably
booting with OP-TEE integrated in the bootflow with all bootmedia.
However to support as many DDR densities as possible we cannot use the
default 0x9e78000 location as with other K3 devices.
So add OP-TEE back into the default build but modify the BL32 base
address for TF-A so it will jump to the correct location.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
The latest tag in ipcdev project is 3.52.00.01. Update SRCREV to the
latest tag.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The messageq IPC firmware example for AM57xx SoCs is available in
ti-linux-firmware repository. Add a recipe to package the prebuilt
messageq firmware into the rootfs.
Additionally, make sure the firmware for IPU1 rproc is copied into boot
partition by updating the dependency in omap-a15 machine conf to the
above recipe. This is needed for Early Boot use cases and gets rid of
dependency on meta-ti-extras layer.
There is no need to deploy the vayu IPC firmware anymore. Remove
the deploy task from ti-ipc-rtos recipe.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Add a recipe to build the Application Host (for A15 core) to demonstrate
IPC with remote processors through messageq firmware. Also package this
in the /usr/bin directory for testing IPC. This recipe only builds the
app_host, and the firmwares are available in ti-linux-firmware
repository.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: TI_LINUX_FW_SRCREV
atf: SRCREV_tfa:am62lxx
u-boot-ti-staging_2025.01: SRCREV
linux-ti-staging-rt_6.12: PV_ARM32,SRCREV_ARM32
linux-ti-staging_6.12: PV,SRCREV
Changelogs:
ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=e89a348f4618a26812fb353a04ed9532ef890a2f..6506f9e1e5d8d62e9dd70123fae04bd07b90bcd5
u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=c5737097b4859362aa22260c5a1f2becd62af65c..556593b8d5f39ad77327d2e7aa190d3faae5a350
linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=90225824e8382c00e9628168922838a0702443eb..6246158ffbe4dfc005258a52780956f8baf04574
linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=adbec2562ad14236717dc1c9dc3020c94ba27f7d..fe4718a972cfcac11933e98f5a3986e084a7c43f
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
|
| |
U-Boot generates all the valid versions of tiboot3.bin and sysfw.itb
based on the given defconfig. The defaults are also picked based on
the board's binman files. No need to duplicate this logic here,
simply deploy what U-Boot generates.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
atf: SRCREV_tfa:am62lxx
u-boot-ti-staging_2025.01: SRCREV
linux-ti-staging-rt_6.12: SRCREV_ARM32
linux-ti-staging_6.12: SRCREV
Changelogs:
u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=05d141ca0739756a0cdd7a19268e3ad07279a17e..c5737097b4859362aa22260c5a1f2becd62af65c
linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=2bcb6e9caabf65ef182dde7dc0332a7fe53622a2..90225824e8382c00e9628168922838a0702443eb
linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=c94f90807b390a224fd087549b4bd5d84d5fc971..adbec2562ad14236717dc1c9dc3020c94ba27f7d
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
| |
V4L2 has updated fh_add/delete to take another parameter in linux-next.
The update has been made in out-of-tree module to fix build failure.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Improve KERNEL_DEVICETREE lists for all Beagle platforms:
* Expand the list with more overlays and related DTBs
* Since in many cases the lists are slightly different between
6.6 and 6.12 kernels, explicitly provide both separate lists
* PocketBeagle2 is only supported by 6.12, so one list for now
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
Upgrade BB.org 6.12 kernel to the latest 6.12.34 tags.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
Upgrade BB.org U-boot from 2025.04 to 2025.07
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
Update BB.org 6.6 kernel to the latest tags.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
k3conf: SRCREV
Changelogs:
k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=b35ec6f6c6e11471c5d06f8c24ac396077f893be..4e8df1a41a1437b61562836e9478e8069d1a071c
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
u-boot-ti-staging_2025.01: SRCREV
k3conf: SRCREV
linux-ti-staging-rt_6.12: SRCREV_ARM32
linux-ti-staging_6.12: SRCREV
Changelogs:
u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=743712b9ee4b33cc9739a3cbeb5a8f14ae2ccf35..05d141ca0739756a0cdd7a19268e3ad07279a17e
k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=2bcd5f52a88ef48f8bb5b7541cf05b10d2008cd7..b35ec6f6c6e11471c5d06f8c24ac396077f893be
linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=60431d6c0e260d0b9404bcf325368a88daeef9ca..2bcb6e9caabf65ef182dde7dc0332a7fe53622a2
linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=ce4785d01a0b962c7d9cb12f56dbae02514213eb..c94f90807b390a224fd087549b4bd5d84d5fc971
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
| |
Add the INSIDE-Secure LICENSE and update the PKA recipe to use this
license.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
k3conf: SRCREV
Changelogs:
k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=6034420195cf763c9470fb2113810695e5e37a23..2bcd5f52a88ef48f8bb5b7541cf05b10d2008cd7
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
| |
Add a recipe to install the PKA firmware in root filesystem needed by
sa2_ul driver for PKA operations across all K3 platforms.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
| |
Seems having hyphens in the revision tag causes issues with
RPM packaging. Remove this hyphen.
Reported-by: Daniel Schultz <D.Schultz@phytec.de>
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
If you are not building a TI machine then KERNEL_BASE_CLASS is not
defined and you get a parse error. Move the default setting out of
ti-soc.inc and into ti-kernel.inc.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: TI_LINUX_FW_SRCREV
u-boot-ti-staging_2025.01: SRCREV
linux-ti-staging-rt_6.12: SRCREV_ARM32
linux-ti-staging_6.12: SRCREV
Changelogs:
ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=f59a711599249ecac75fea38b7a15ef9137d650d..e89a348f4618a26812fb353a04ed9532ef890a2f
u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=3bcfad6cee95403f7f62dd9d871cc3ea948c0761..743712b9ee4b33cc9739a3cbeb5a8f14ae2ccf35
linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=b5ee9420d81f46861c4f0a172154e477feda1980..60431d6c0e260d0b9404bcf325368a88daeef9ca
linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=72f48d59b8f087fa0dd1f1e8c2c0b5bc0baa537c..ce4785d01a0b962c7d9cb12f56dbae02514213eb
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
|
| |
This change is needed due to the SGX driver, any distro, not just Arago,
using a TI SoC with SGX will need this fix, so it should go in meta-ti.
Signed-off-by: Andrew Davis <afd@ti.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Convert devicetree prefix matching functionality into a generic
class that can be used by the kernel and wic images. That way
dynamically generated KERNEL_DEVICETREE list will be the same
when populating /boot dir of rootfs and/or FAT boot partition
of a wic image.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
Automatically generate non-vendored DTBs list in DEVICETREE_FILES from
vendored KERNEL_DEVICETREE list for all platforms to use.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
Move KERNEL_DTBVENDORED settings from the kernel to ti-soc.inc
in the config scope.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
update to PSSP release v6.5.0. This release is compatible to linux
v6.12 and other fixes for RP message size.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
| |
Minor comment changes, fix versions listed for some items.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
|
| |
This was used when the DT_VENDOR_PREFIX was different between supported
BSP versions. All supported now use the new prefix so drop this var.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove support for the v6.1 TI and Beagle BSPs. This was originally
split into meta-ti-bsp and meta-beagle changes, but there are some
hidden interdependencies that made that more painful than needed.
Remove v6.1 support from both BSP layers here.
This includes packages specific to those BSPs:
- TI and BB.org v6.1 Linux kernel
- TI and BB.org 2023.04 U-Boot
- Rogue GPU driver 23.3 and Mesa 22.3.5
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
|
|
|
|
|
|
|
|
|
| |
A recent change in bitbake requires that all variable assignments have
whitespace between the variable, the operator and the value.
FOO = "1"
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
We have a need for some platforms to add kernel options to the bootloader
during wic creation time. Create a new variable and add that to the
sdimage-2part-efi.wks.in file so that a machine can override it if
needed.
Add an override for am64 to point the kernel at console=ttyS2.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The legacy HS platforms (am335x-hs-evm, am437x-hs-evm, and
am57xx-hs-evm) are not using the new fitImage flow, but the kernels all
include the kernel.bbclass which disallows the old fitImage flow.
Copy in the last version of the kernel.bbclass and name it
kernel_legacyhs.bbclass, and update the machine configs to defined a
variable to use as the KERNEL_BASE_CLASS to inherit.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
| |
Since meta-ti-bsp requires the new fitImage code, we are no longer
backwards compatible with walnascar.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
ti-linux-fw: TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION
atf: SRCREV_tfa:am62lxx
u-boot-ti-staging_2025.01: SRCREV
k3conf: SRCREV
linux-ti-staging-rt_6.12: SRCREV_ARM32
linux-ti-staging_6.12: SRCREV
Changelogs:
ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=373c2f5646e3947b3b4a340da729288ee3f07833..f59a711599249ecac75fea38b7a15ef9137d650d
u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=827c35b4d141865e25d234e3d298614e6c47150c..3bcfad6cee95403f7f62dd9d871cc3ea948c0761
k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=e6abc1b87f1d5bc4c2ab5f1ebfbf5a70e437dcb4..6034420195cf763c9470fb2113810695e5e37a23
linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=f0e4f5ca0905956c70779b31663f594c08c6a3bc..b5ee9420d81f46861c4f0a172154e477feda1980
linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=78e6abff322081d53c5a685d927476086c9b2846..72f48d59b8f087fa0dd1f1e8c2c0b5bc0baa537c
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
| |
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
| |
- The S change needs to skip the APPEND-2 check since S should never
have a space in a path.
- The UBOOT_VERSION bbappend does not need a guard since we are
modifying our own layer.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FIT signing was disabled in the past as it was interfering with multi
DTB usecase in binman, and it was thought that the binman signing being
done is equivalent to UBOOT_SIGN_ENABLE.
Though looking at the sources, UBOOT_SIGN_ENABLE is actually used to
sign the kernel FIT Image instead and the name UBOOT actually specifies
that it's used in tandom with U-boot. During the signing process, mkimage
from U-boot is used to pack the kernel FIT Image and along with that,
one DTB from U-boot is also passed to the mkimage command. The DTB that
gets passed gets the key embedded in it that is used to verify the
kernel FIT image at runtime.
Now this signed DTB is packed in U-boot by triggering a rebuild with
EXT_DTB argument in the U-boot build process. However, this failed as
there was a U-boot bug which was not looking at the packed sources
properly with the multi DTB usecase.
Now that a U-boot fix is available [0], revert that commit which
disabled the FIT signing.
This reverts commit 9656b79cb557a46d2611b67e7e51702f6da05594.
[0]: https://lore.kernel.org/all/20250626-b4-upstream-fix-icssg-fit-v1-1-95eff1c853a4@ti.com/
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
In order to turn the fitImage signing back on, we need to inherit the
ti-secdev class to setup all of the needed signing variables.
Remove the inherit ti-secdev from the kernel recipes since the fitImage
signing is handled in the ti-kernel-fitimage recipe and not in the
kernel recipes anymore.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The CICD flow needs to control the value for BRANCH in order to have the
recipe updated with the next SRCREV, but point to the CICD/next branch
for initial build/test.
With this split in linux-ti-staging-rt we cannot just have an override
for BRANCH in the local.conf because it trumps the new BRANCH_ARM32
system.
This patch creates an additional "default" variable BRANCH_ARM64 (or not
arm32), which can be controlled separately by the CICD flow. Then BRANCH
simply is picking between the two and so can be controlled by overrides
in the recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
Since the kernel branches could theoretically drift apart, we need to
track the PV of the kernel on the RT branch for the ARM32 platforms as
well.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
atf: SRCREV_tfa:am62lxx
linux-ti-staging-rt_6.12: PV_ARM32
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
|
|
|
|
|
|
|
| |
Updated the value(s) for:
u-boot-ti-mainline: PV,SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
| |
While all ARM64 devices use the same branch for RT and non-RT builds,
the ARM32 devices have a separate branch for RT Kernel which is
"ti-rt-linux-6.12.y-arm32". Update the BRANCH and SRCREV for ARM32
devices for RT builds.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The payload containing ATF, OP-TEE and DM in falcon mode was renamed
from 'tispl_falcon.bin' to 'tifalcon.bin' when adapting upstream patches
to ti-u-boot[1].
Therefore this patch fixes the same in meta-ti.
[1]:
https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/configs/k3_r5_falcon.config?h=ti-u-boot-2025.01-next#n36
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The U-Boot config fragment used to enable falcon mode was renamed from
'am62x_r5_falcon.config' to the more generic 'k3_r5_falcon.config' when
adapting upstream patches to ti-u-boot[1].
Therefore this patch fixes the same in meta-ti.
[1]: 90d2e960b4c at ti-u-boot-2025.01-next
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|