<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-ti.git, branch cicd.master.202510200100</title>
<subtitle>Mirror of git.yoctoproject.org/meta-ti.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-ti.git/atom?h=cicd.master.202510200100</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-ti.git/atom?h=cicd.master.202510200100'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/'/>
<updated>2025-10-20T06:00:50+00:00</updated>
<entry>
<title>CI/CD Auto-Merger: cicd.master.202510200100</title>
<updated>2025-10-20T06:00:50+00:00</updated>
<author>
<name>LCPD Automation Script</name>
<email>lcpdbld@list.ti.com</email>
</author>
<published>2025-10-20T06:00:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=79836f10b9b3a08905a13a8f09cd045191f03c8b'/>
<id>urn:sha1:79836f10b9b3a08905a13a8f09cd045191f03c8b</id>
<content type='text'>
Updated the value(s) for:
  ti-linux-fw: TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION
  atf: SRCREV_tfa:am62lxx
  u-boot-ti-staging_2025.01: SRCREV_uboot
  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&amp;q=27344bea60be4f0410feb1c309b9de3cdc7f8c6d..237071793594723bf1c2e9eef8ff836ffa3b09df
  u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&amp;q=c779c758475cb98e95d3c05744e0dcbca5fc9991..b5956eebf45b7b604c046a21792883a42cd9c198
  linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&amp;q=2c04cd1373bf2cd53784cc10efad710f9fa5b5c8..dd80e6d61d8ccba753eb372040107ff195c8550d
  linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&amp;q=3a3f87d0bf70131af74a85336c2785d933732825..2ce6f0999344a368217d04cdbee0922144ecc899

Signed-off-by: LCPD Automation Script &lt;lcpdbld@list.ti.com&gt;
</content>
</entry>
<entry>
<title>u-boot-ti-mainline: Update to version: v2025.10</title>
<updated>2025-10-14T20:37:09+00:00</updated>
<author>
<name>LCPD Automation Script</name>
<email>lcpdbld@list.ti.com</email>
</author>
<published>2025-10-11T04:23:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=b83421c9869fc1370d5d451ed61fa963985735be'/>
<id>urn:sha1:b83421c9869fc1370d5d451ed61fa963985735be</id>
<content type='text'>
Updated the value(s) for:
  u-boot-ti-mainline: PV,SRCREV_uboot

Signed-off-by: LCPD Automation Script &lt;lcpdbld@list.ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-extras: dsptop: Explicitly allow build for AM57x</title>
<updated>2025-10-14T20:37:09+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2025-10-02T13:54:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=1602320551c79732e4f55323c6b2ab4b8a1ee1ec'/>
<id>urn:sha1:1602320551c79732e4f55323c6b2ab4b8a1ee1ec</id>
<content type='text'>
This recipe builds and runs fine on both DRA7x and AM57x machines.
The COMPATIBLE_MACHINE is set to just DRA7x, but this was okay as AM57x
machines also set themselves as DRA7x family devices. The issue is then
we cannot then differentiate between packages that are actually DRA7x-
only and those that just use that family to mean both machine types. To
fix this when we mean both are allowed use "omap-a15" as done here.

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-extras: gdbc6x: Explicitly allow build for AM57x</title>
<updated>2025-10-14T20:37:09+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2025-10-02T13:54:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=45b06e3a9ee563234786531889d561d69f7a16e3'/>
<id>urn:sha1:45b06e3a9ee563234786531889d561d69f7a16e3</id>
<content type='text'>
This recipe builds and runs fine on both DRA7x and AM57x machines.
The COMPATIBLE_MACHINE is set to just DRA7x, but this was okay as AM57x
machines also set themselves as DRA7x family devices. The issue is then
we cannot then differentiate between packages that are actually DRA7x-
only and those that just use that family to mean both machine types. To
fix this when we mean both are allowed use "omap-a15" as done here.

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-extras: dsptop: Simplify for DRA7xx only build</title>
<updated>2025-10-14T20:37:09+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2025-10-02T13:54:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=fce4f6188b6d1bbdc98e84db9931fafb40c94f61'/>
<id>urn:sha1:fce4f6188b6d1bbdc98e84db9931fafb40c94f61</id>
<content type='text'>
This recipe is already only compatible with the DRA7xx machine, so
no need to set PLATFORM based on the only possibility. This then
allows us to directly set the compile flags for the same. And now
that the package does not change based on the machine, remove the
PACKAGE_ARCH line.

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-extras: gdbc6x: Simplify for DRA7xx only build</title>
<updated>2025-10-14T20:37:09+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2025-10-02T13:54:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=b3bd4813b29df64436f0409f81b19df85e03a0fe'/>
<id>urn:sha1:b3bd4813b29df64436f0409f81b19df85e03a0fe</id>
<content type='text'>
This recipe is already only compatible with the DRA7xx machine, so
no need to set PLATFORM based on the only possibility. This then
allows us to directly set the compile flags for the same. And now
that the package does not change based on the machine, remove the
PACKAGE_ARCH line.

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-extras: libaet: Remove this recipe</title>
<updated>2025-10-14T20:37:09+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2025-10-02T13:50:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=5397fdaac20fe3641b08a31dd8febebdb506b214'/>
<id>urn:sha1:5397fdaac20fe3641b08a31dd8febebdb506b214</id>
<content type='text'>
This was only ever used as part of the DSP firmware for OpenCL dispatch.
That is all gone now, so remove this leftover dependency.

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-bsp: vpe-tests: Remove this recipe</title>
<updated>2025-10-14T20:37:09+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2025-10-02T13:50:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=9741bc7bf165111c0972ef4426d7c761e82ed74d'/>
<id>urn:sha1:9741bc7bf165111c0972ef4426d7c761e82ed74d</id>
<content type='text'>
vpe-tests is obsolete, it was replaced with "testvpe" as part of
glsdk-example-apps about 10 years ago in meta-arago, so long ago even
its replacement has been obsoleted and removed. Yet, this unbuildable
recipe still lives on here in meta-ti. Send it out to sea.

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>u-boot: Make sure the build dir is unique for each UBOOT_CONFIG</title>
<updated>2025-10-14T12:39:53+00:00</updated>
<author>
<name>Ryan Eatmon</name>
<email>reatmon@ti.com</email>
</author>
<published>2025-10-07T20:52:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=b34f91575f131ef8caf7d1aebc838be398487a96'/>
<id>urn:sha1:b34f91575f131ef8caf7d1aebc838be398487a96</id>
<content type='text'>
Make the same changes as the corresponding oe-core patch. [1]

[1] https://git.openembedded.org/openembedded-core/commit/?id=22e96b32b0be02ec0971c9334d4b1df7c9ef8d84

Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>machine: Add FIT_CONF_DEFAULT_DTB for legacy platforms</title>
<updated>2025-10-10T18:21:05+00:00</updated>
<author>
<name>Ryan Eatmon</name>
<email>reatmon@ti.com</email>
</author>
<published>2025-10-09T18:18:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=e108e5424e1cffd58a0e8d540117d79dce85a8c7'/>
<id>urn:sha1:e108e5424e1cffd58a0e8d540117d79dce85a8c7</id>
<content type='text'>
As of u-boot 2025.10, the fit image requires a value for the default
configuration.  The change [1] introduced the FIT_CONF_DEFAULT_DTB code
to the legacy fitimage class, but failed to set values for the legacy
platforms.  This led to us putting default = "" in the .its file, which
is now an error.

Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
</feed>
