Mirror of git.yoctoproject.org/meta-ti.git https://git.enea.com/cgit/linux/meta-ti.git/atom?h=11.01.15 2025-09-25T09:12:13+00:00 2025-09-25T09:12:13+00:00 LCPD Automation Script lcpdbld@list.ti.com 2025-09-25T09:12:13+00:00 urn:sha1:bd71e17c75fce1237c40167c8358ecfa6c3b6b48 Updated the value(s) for: atf: SRCREV_tfa:am62lxx u-boot-ti-staging_2025.01: SRCREV Changelogs: u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=..c779c758475cb98e95d3c05744e0dcbca5fc9991 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> 2025-09-24T23:00:08+00:00 LCPD Automation Script lcpdbld@list.ti.com 2025-09-24T23:00:08+00:00 urn:sha1:58c58429ee8a127fb743acd334777d31e476301e 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=bb242f4eee42835066d83345e4d64bc02307f855..27344bea60be4f0410feb1c309b9de3cdc7f8c6d u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=..c779c758475cb98e95d3c05744e0dcbca5fc9991 linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=e2b759994f9ed141d13b2f7a3ae8b9c51eb7e295..2c04cd1373bf2cd53784cc10efad710f9fa5b5c8 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=ccfe8fee8026cbb23dcd9c69a2bd961c99c58567..3a3f87d0bf70131af74a85336c2785d933732825 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> 2025-09-22T14:36:44+00:00 Ryan Eatmon reatmon@ti.com 2025-09-22T14:36:44+00:00 urn:sha1:f6ea17b5da33d44c6d36c189b5f3eaef9ff1c3fa An upcoming patch series will optionally add in a second repository that will optionally be needed as part of the builds. To facilitate that, we need to name the uboot checkout so that the SRCREV can be tracked correctly in the recipe. Signed-off-by: Ryan Eatmon <reatmon@ti.com> 2025-09-22T14:33:53+00:00 Ryan Eatmon reatmon@ti.com 2025-09-22T14:14:07+00:00 urn:sha1:3dda9db49204710cef4310690925587615e8932e The TI_EXTRAS infrastructure needs a little tweaking to support turning on multiple extra options at the same time. 1) Since TI_EXTRAS can be a space separated list and not a single fixed value, we need to change how we detect when to include the TI_EXTRA values. 2) The tie-jailhouse overrides were being a little too heavy handed. All of the variables that are changed for any given extra feature needs to use the proper variable override. This was most important for the COMPATIBLE_MACHINE settings. 3) Move the ti-extras out of specific machine configs and into the ti-soc so that all machines can use the extras. Signed-off-by: Ryan Eatmon <reatmon@ti.com> 2025-09-18T17:57:12+00:00 LCPD Automation Script lcpdbld@list.ti.com 2025-09-18T17:57:12+00:00 urn:sha1:d99cff5534fa2def3e9ccdbc6d9ca568e4587f24 Updated the value(s) for: 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: u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=3c06cd621447331aeab0bbb2e5c063a2b1d79d1b..91c8a62c788c2d0efb733296336bf0e658727faf k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=6dd352f234ef19c5cb92c924101e1eab29d2939a..f63ccd27cba9550de04e8dbb04bc6003d8b5168e linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=4235794ce373baf55d9ff5cf920b1d44b7e31455..e2b759994f9ed141d13b2f7a3ae8b9c51eb7e295 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=af3896fca24b7945db015d2ac411ef50e93a11c9..ccfe8fee8026cbb23dcd9c69a2bd961c99c58567 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> 2025-09-17T22:42:13+00:00 Andrew Davis afd@ti.com 2025-09-17T22:09:26+00:00 urn:sha1:d89a382c3abce5f84d0a2b5edb0f7534b5b50171 Now that display controller aliases are not set using PACKAGECONFIG, instead of using PREFERRED_PROVIDER to add either "sgx" or "pvr" to PACKAGECONFIG, followed by reading it back out, simply use PREFERRED_PROVIDER directly. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> 2025-09-17T22:42:13+00:00 Andrew Davis afd@ti.com 2025-09-17T22:09:25+00:00 urn:sha1:f7230c48688cfaf554aa38062f1ddda9fb29020b Update mesa-pvr which includes a default set of display controller aliases for the supported display controllers. This means we do not have to manually set the alias for each device here in the integration layer. Remove that here. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> 2025-09-17T22:42:13+00:00 Andrew Davis afd@ti.com 2025-09-17T22:09:24+00:00 urn:sha1:903bc129627cec5032361d0bef0f44b40ffa2a96 The DRIVER and matching UMLIBS must always match, no need to define a version number for both. Keep this simple and remove the extra defines. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> 2025-09-17T22:42:13+00:00 Andrew Davis afd@ti.com 2025-09-17T22:09:23+00:00 urn:sha1:51cf5738f76c63009074747fccf0b298c4ce9c91 Setting or removing the gpu MACHINE_FEATURE does not actually change if the GPU driver is built or not. That is done based on the setting of the BSP_{SGX,ROGUE}_{DRIVER,UMLIBS}_{PROVIDER,VERSION} vars. These are default empty for BSP versions without supported GPU drivers, which will correctly cause a fallback to SW rendering when the GPU driver is not available. As the "gpu" MACHINE_FEATURE now has no uses, remove it from all the machine config include files. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> 2025-09-17T22:42:13+00:00 Andrew Davis afd@ti.com 2025-09-17T22:09:22+00:00 urn:sha1:954a631aa37450a3b37e8928b60bfd12975bfa82 This also matches what is done for ti-img-rogue-umlibs. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>