<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-ti.git/meta-ti-bsp/conf/machine/beagleplay.conf, branch master</title>
<subtitle>Mirror of git.yoctoproject.org/meta-ti.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-ti.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-ti.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/'/>
<updated>2024-12-16T14:31:15+00:00</updated>
<entry>
<title>conf/machine: rename beagleplay machine to beagleplay-ti</title>
<updated>2024-12-16T14:31:15+00:00</updated>
<author>
<name>Denys Dmytriyenko</name>
<email>denys@konsulko.com</email>
</author>
<published>2024-12-13T23:31:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=97e5fcc396d30e178082e64cf1162ebfe9da76e6'/>
<id>urn:sha1:97e5fcc396d30e178082e64cf1162ebfe9da76e6</id>
<content type='text'>
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 &lt;denys@konsulko.com&gt;
</content>
</entry>
<entry>
<title>conf: machine: Add support for bsp-ti-6_12 in beagleplay</title>
<updated>2024-10-24T14:46:16+00:00</updated>
<author>
<name>Chirag Shilwant</name>
<email>c-shilwant@ti.com</email>
</author>
<published>2024-10-17T17:27:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=23f799352f6cc6adff1e2922107b42c29b565407'/>
<id>urn:sha1:23f799352f6cc6adff1e2922107b42c29b565407</id>
<content type='text'>
Add bsp-ti-6_12 overrides in A53 &amp; R5 machine configuration
to ensure it picks the appropriate u-boot configs for beagleplay

Signed-off-by: Chirag Shilwant &lt;c-shilwant@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>linux-ti-mainline: Update to version: v6.11</title>
<updated>2024-10-19T19:05:48+00:00</updated>
<author>
<name>LCPD Automation Script</name>
<email>lcpdbld@list.ti.com</email>
</author>
<published>2024-09-17T05:56:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=5c537ecc73f199b575f1ad79924b05324ae8340d'/>
<id>urn:sha1:5c537ecc73f199b575f1ad79924b05324ae8340d</id>
<content type='text'>
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 &lt;lcpdbld@list.ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf: machine: Remove multiconfig compulsion for k3 platforms</title>
<updated>2024-09-13T15:38:39+00:00</updated>
<author>
<name>Chirag Shilwant</name>
<email>c-shilwant@ti.com</email>
</author>
<published>2024-09-12T20:07:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=82e8543cdcec09f1fe95fd2c937121ed3c513c22'/>
<id>urn:sha1:82e8543cdcec09f1fe95fd2c937121ed3c513c22</id>
<content type='text'>
- 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 &amp; 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&amp;id=f814840465358a6b5429ad20165742ac6e6e6a29

Signed-off-by: Chirag Shilwant &lt;c-shilwant@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>linux-ti-mainline: Update to version: v6.10</title>
<updated>2024-08-01T18:14:11+00:00</updated>
<author>
<name>LCPD Automation Script</name>
<email>lcpdbld@list.ti.com</email>
</author>
<published>2024-07-18T14:20:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=4a3918009f44c8e6cf487a920b247ac2c8ee1e8b'/>
<id>urn:sha1:4a3918009f44c8e6cf487a920b247ac2c8ee1e8b</id>
<content type='text'>
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 &lt;lcpdbld@list.ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf/machine: use the default TI BSP for BeaglePlay</title>
<updated>2024-06-15T13:05:34+00:00</updated>
<author>
<name>Denys Dmytriyenko</name>
<email>denys@konsulko.com</email>
</author>
<published>2024-06-14T21:57:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=8090ce9a4b1108fe51b40b3d8997314a59bf89f1'/>
<id>urn:sha1:8090ce9a4b1108fe51b40b3d8997314a59bf89f1</id>
<content type='text'>
BeaglePlay gains official support from latest TI lts-6.6 baseline, so set
it as the default. Other Beagle platforms will still use BB.org as default.

And these defaults can still be changed with TI_PREFERRED_BSP setting in a
distro config or by end user in the local.conf

Signed-off-by: Denys Dmytriyenko &lt;denys@konsulko.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf/machine/beagle*, linux-bb.org: update for multi-BSP support</title>
<updated>2024-06-15T13:05:34+00:00</updated>
<author>
<name>Denys Dmytriyenko</name>
<email>denys@konsulko.com</email>
</author>
<published>2024-06-14T21:57:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=16092e065bb03cfe29952d4ec792a0de3142879a'/>
<id>urn:sha1:16092e065bb03cfe29952d4ec792a0de3142879a</id>
<content type='text'>
Update all Beagle platform configurations to support multiple BSPs.

Signed-off-by: Denys Dmytriyenko &lt;denys@konsulko.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf/machine, ti-bsp: add support for multiple BSP providers</title>
<updated>2024-06-15T13:05:34+00:00</updated>
<author>
<name>Denys Dmytriyenko</name>
<email>denys@konsulko.com</email>
</author>
<published>2024-06-14T21:57:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=fdfa6e2f13f5d58223b82819cbf87081d7b11750'/>
<id>urn:sha1:fdfa6e2f13f5d58223b82819cbf87081d7b11750</id>
<content type='text'>
This adds a facility to define multiple supported BSPs with their own
preferences for individual components, as well as lets machine configs
specify conditional configurations for different BSPs.

Signed-off-by: Denys Dmytriyenko &lt;denys@konsulko.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf/machine, linux-bb.org: re-org DT lists for Beagle platforms</title>
<updated>2024-06-15T13:05:34+00:00</updated>
<author>
<name>Denys Dmytriyenko</name>
<email>denys@konsulko.com</email>
</author>
<published>2024-06-06T19:48:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=12909d33292ba5e51e7383bbca9d1ae4383192b2'/>
<id>urn:sha1:12909d33292ba5e51e7383bbca9d1ae4383192b2</id>
<content type='text'>
In order to be able to switch between different kernel providers, as well
as different versions of kernel LTS (e.g. 6.1 vs. 6.6), let's re-organize
Device Tree lists as follows:

* Move all Beagle-specific DTBs and overlays into corresponding linux-bb.org
recipe for now, to be used when building beagleboard.org baseline
* Update KERNEL_DEVICETREE in the machine configs to only list what already
exists in the upstream/mainline kernel
* Update KERNEL_DEVICETREE_PREFIX to match the list when building TI baseline

With this change it is now very easy to switch the kernel between providers
supported by meta-ti - linux-ti-mainline, linux-ti-staging and linux-bb.org

Please note that 6.6 LTS has moved to "vendored" device tree layout even for
32-bit platforms, while BB.org still uses 6.1 LTS and flat DT layout.

Signed-off-by: Denys Dmytriyenko &lt;denys@konsulko.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-bsp: update BeagleBoard.org BSP to the latest</title>
<updated>2024-06-15T13:05:34+00:00</updated>
<author>
<name>Denys Dmytriyenko</name>
<email>denys@konsulko.com</email>
</author>
<published>2024-05-24T03:46:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=f59716983f5338ef425d8c8e056f2f1c430ef294'/>
<id>urn:sha1:f59716983f5338ef425d8c8e056f2f1c430ef294</id>
<content type='text'>
* Update linux-bb.org to 6.1.80 for both 32 and 64 bit platforms
* Update DTB/DTBO lists to include latest renames and additions
* Re-enable vendored DTB layout by default

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