from:"Denys Dmytriyenko"

Re: [meta-ti] [master][PATCH] conf: machine: k3: use ARMv8-A as base arch

2025-01-16 Thread Denys Dmytriyenko

On Thu, Jan 16, 2025 at 03:19:29PM +0100, Matthias Schiffer wrote:
> On Mon, 2024-12-09 at 10:59 -0500, Denys Dmytriyenko wrote:
> > 
> > On Mon, Dec 09, 2024 at 10:38:56AM +0100, Matthias Schiffer via 
> > lists.yoctoproject.org wrote:
> > > On Thu, 2024-11-14 at 15:08 +0100, Matthias Schiffer wrote:
> > > > All K3 SoCs are Cortex-A53/A72, so arch-armv8a.inc is a more appropriate
> > > > common base than the very generic arch-arm64.inc. arch-armv8a.inc 
> > > > defaults
> > > > to enable the CRC extension (DEFAULTTUNE = "armv8a-crc") and allows for
> > > > easy addition of the ARMv8 crypto extensions by setting the tune to
> > > > "armv8a-crc-crypto".
> > > 
> > > Hi, any comments regarding this patch?
> > 
> > Matthias,
> > 
> > We've discussed this couple of weeks ago and decided to make a slightly 
> > different change that will also enable your use case as well.
> > 
> > Ryan got busy lately with master breakage, so I should probably send the 
> > change in for discussion.
> 
> Hi Denys,
> 
> I haven't seen the mentioned change yet, did you not send it or did I overlook
> it?

Matthias,

Thank you for the reminder - unfortunately it fell through the cracks due to 
the holidays and other engagements and distractions. I'll get to it shortly.

-- 
Denys

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18202): 
https://lists.yoctoproject.org/g/meta-ti/message/18202
Mute This Topic: https://lists.yoctoproject.org/mt/109573384/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][scarthgap/master][PATCH v2] ti-bsp: Disable GC320 support conditionally on BSP version

2025-01-10 Thread Denys Dmytriyenko

On Fri, Jan 10, 2025 at 02:00:26PM -0600, Ryan Eatmon wrote:
> 
> 
> On 1/10/2025 1:30 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
> >
> >
> >On 1/10/2025 12:06 PM, Denys Dmytriyenko wrote:
> >>On Wed, Jan 08, 2025 at 02:51:45PM -0600, Andrew Davis via
> >>lists.yoctoproject.org wrote:
> >>>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 
> >>>---
> >>>
> >>>Changes for v2:
> >>>  - Rebased on latest with new meta-beagle layer
> >>>
> >>>  meta-beagle/conf/machine/include/beagle-bsp.inc |  6 ++
> >>>  meta-ti-bsp/conf/machine/include/ti-bsp.inc | 15 +++
> >>>  2 files changed, 21 insertions(+)
> >>>
> >>>diff --git a/meta-beagle/conf/machine/include/beagle-bsp.inc
> >>>b/meta-beagle/conf/machine/include/beagle-bsp.inc
> >>>index 34889b41..06483ba9 100644
> >>>--- a/meta-beagle/conf/machine/include/beagle-bsp.inc
> >>>+++ b/meta-beagle/conf/machine/include/beagle-bsp.inc
> >>>@@ -23,6 +23,9 @@ BSP_ROGUE_DRIVER_VERSION:bsp-bb_org-6_1 = "23%"
> >>>  BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org-6_1 = "23%"
> >>>  BSP_MESA_PVR_VERSION:bsp-bb_org-6_1 = "22%"
> >>>+# GC320 support requires out-of-tree drivers not yet
> >>>available in bb.org 6.1
> >>>+MACHINE_FEATURES:remove:bsp-bb_org-6_1 = "gc320"
> >>>+
> >>>  # ==
> >>>  # bb_org-6_6
> >>>  # BeagleBoard.org kernel 6.6, Upstream u-boot 2024.07
> >>>@@ -41,3 +44,6 @@ BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org-6_6 =
> >>>"ti-img-rogue-driver"
> >>>  BSP_ROGUE_DRIVER_VERSION:bsp-bb_org-6_6 = "24%"
> >>>  BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org-6_6 = "24%"
> >>>  BSP_MESA_PVR_VERSION:bsp-bb_org-6_6 = "23%"
> >>>+
> >>>+# GC320 support requires out-of-tree drivers not yet
> >>>available in bb.org 6.6
> >>>+MACHINE_FEATURES:remove:bsp-bb_org-6_6 = "gc320"
> >>>diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> >>>b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> >>>index 4bbe7668..6773bb7a 100644
> >>>--- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> >>>+++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> >>>@@ -22,6 +22,9 @@ BSP_BOOTLOADER_VERSION:bsp-mainline = "%"
> >>>  # in mainline, usually present in TI staging or derivative like BB.org
> >>>  MACHINE_FEATURES:remove:bsp-mainline = "gpu"
> >>>+# GC320 support requires out-of-tree drivers not available in mainline
> >>>+MACHINE_FEATURES:remove:bsp-mainline = "gc320"
> >>>+
> >>>  # ==
> >>>  # next
> >>>  # upcoming upstream/mainline kernel, u-boot
> >>>@@ -35,6 +38,9 @@ BSP_BOOTLOADER_VERSION:bsp-next = "%"
> >>>  # in next, usually present in TI staging or derivative like BB.org
> >>>  MACHINE_FEATURES:remove:bsp-next = "gpu"
> >>>+# GC320 support requires out-of-tree drivers not available in next
> >>>+MACHINE_FEATURES:remove:bsp-next = "gc320"
> >>
> >>Andrew, Ryan,
> >>
> >>Something went wrong here ^^^
> >>Instead of removing "gc320" for bsp-next, like in the patch here, it got
> >>committed removing it for bsp-ti-6_12 twice:
> >>
> >>https://git.yoctoproject.org/meta-ti/commit/?h=master-wip&id=fe0b35f5f135b98d1ee0f8fe2488b10fbe9a7bb3
> >>
> >>Was there any manual massaging involved?
> >
> >Yes.  I did.  Let me look at it.
> 
> Fixed on master-wip, scarthgap-wip was correct.

bsp-ti-6_next ?


> >>>+
> >>>  # ==
> >>>  # ti-6_12
> >>>  # TI staging kernel 6.12, u-boot 2024.10
> >>>@@ -48,6 +54,9 @@ BSP_BOOTLOADER_VERSION:bsp-ti-6_12 = "2024.10%"
> >>>  # in 6.12 yet
> >>>  MACHINE_FEATURES:remove:bsp-ti-6_12 = "gpu"
> >>>+# GC320 support requires out-of-tree drivers not yet av

Re: [meta-ti][scarthgap/master][PATCH v2] ti-bsp: Disable GC320 support conditionally on BSP version

2025-01-10 Thread Denys Dmytriyenko

On Wed, Jan 08, 2025 at 02:51:45PM -0600, Andrew Davis via 
lists.yoctoproject.org wrote:
> 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 
> ---
> 
> Changes for v2:
>  - Rebased on latest with new meta-beagle layer
> 
>  meta-beagle/conf/machine/include/beagle-bsp.inc |  6 ++
>  meta-ti-bsp/conf/machine/include/ti-bsp.inc | 15 +++
>  2 files changed, 21 insertions(+)
> 
> diff --git a/meta-beagle/conf/machine/include/beagle-bsp.inc 
> b/meta-beagle/conf/machine/include/beagle-bsp.inc
> index 34889b41..06483ba9 100644
> --- a/meta-beagle/conf/machine/include/beagle-bsp.inc
> +++ b/meta-beagle/conf/machine/include/beagle-bsp.inc
> @@ -23,6 +23,9 @@ BSP_ROGUE_DRIVER_VERSION:bsp-bb_org-6_1 = "23%"
>  BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org-6_1 = "23%"
>  BSP_MESA_PVR_VERSION:bsp-bb_org-6_1 = "22%"
>  
> +# GC320 support requires out-of-tree drivers not yet available in bb.org 6.1
> +MACHINE_FEATURES:remove:bsp-bb_org-6_1 = "gc320"
> +
>  # ==
>  # bb_org-6_6
>  # BeagleBoard.org kernel 6.6, Upstream u-boot 2024.07
> @@ -41,3 +44,6 @@ BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org-6_6 = 
> "ti-img-rogue-driver"
>  BSP_ROGUE_DRIVER_VERSION:bsp-bb_org-6_6 = "24%"
>  BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org-6_6 = "24%"
>  BSP_MESA_PVR_VERSION:bsp-bb_org-6_6 = "23%"
> +
> +# GC320 support requires out-of-tree drivers not yet available in bb.org 6.6
> +MACHINE_FEATURES:remove:bsp-bb_org-6_6 = "gc320"
> diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
> b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> index 4bbe7668..6773bb7a 100644
> --- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> +++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> @@ -22,6 +22,9 @@ BSP_BOOTLOADER_VERSION:bsp-mainline = "%"
>  # in mainline, usually present in TI staging or derivative like BB.org
>  MACHINE_FEATURES:remove:bsp-mainline = "gpu"
>  
> +# GC320 support requires out-of-tree drivers not available in mainline
> +MACHINE_FEATURES:remove:bsp-mainline = "gc320"
> +
>  # ==
>  # next
>  # upcoming upstream/mainline kernel, u-boot
> @@ -35,6 +38,9 @@ BSP_BOOTLOADER_VERSION:bsp-next = "%"
>  # in next, usually present in TI staging or derivative like BB.org
>  MACHINE_FEATURES:remove:bsp-next = "gpu"
>  
> +# GC320 support requires out-of-tree drivers not available in next
> +MACHINE_FEATURES:remove:bsp-next = "gc320"

Andrew, Ryan,

Something went wrong here ^^^
Instead of removing "gc320" for bsp-next, like in the patch here, it got 
committed removing it for bsp-ti-6_12 twice:

https://git.yoctoproject.org/meta-ti/commit/?h=master-wip&id=fe0b35f5f135b98d1ee0f8fe2488b10fbe9a7bb3

Was there any manual massaging involved?


> +
>  # ==
>  # ti-6_12
>  # TI staging kernel 6.12, u-boot 2024.10
> @@ -48,6 +54,9 @@ BSP_BOOTLOADER_VERSION:bsp-ti-6_12 = "2024.10%"
>  # in 6.12 yet
>  MACHINE_FEATURES:remove:bsp-ti-6_12 = "gpu"
>  
> +# GC320 support requires out-of-tree drivers not yet available in 6.12
> +MACHINE_FEATURES:remove:bsp-ti-6_12 = "gc320"
> +
>  # ==
>  # ti-6_6
>  # TI staging kernel 6.6, u-boot 2024.04
> @@ -65,6 +74,9 @@ BSP_ROGUE_DRIVER_VERSION:bsp-ti-6_6 = "24%"
>  BSP_ROGUE_UMLIBS_VERSION:bsp-ti-6_6 = "24%"
>  BSP_MESA_PVR_VERSION:bsp-ti-6_6 = "23%"
>  
> +# GC320 support requires out-of-tree drivers not yet available in 6.6
> +MACHINE_FEATURES:remove:bsp-ti-6_6 = "gc320"
> +
>  # ==
>  # ti-6_1
>  # TI staging kernel 6.1, u-boot 2023.04
> @@ -82,6 +94,9 @@ BSP_ROGUE_DRIVER_VERSION:bsp-ti-6_1 = "23%"
>  BSP_ROGUE_UMLIBS_VERSION:bsp-ti-6_1 = "23%"
>  BSP_MESA_PVR_VERSION:bsp-ti-6_1 = "22%"
>  
> +# GC320 support requires out-of-tree drivers not yet available in 6.1
> +MACHINE_FEATURES:remove:bsp-ti-6_1 = "gc320"
> +
>  # ==
>  # sane fallback defaults
>  # if specific values are not defined or bsp is set incorrectly
> -- 
> 2.39.2

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18178): 
https://lists.yoctoproject.org/g/meta-ti/message/18178
Mute This Topic: https://lists.yoctoproject.org/mt/110504595/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH v2] ti-bsp: Change to 6.12 as the default

2025-01-10 Thread Denys Dmytriyenko

On Wed, Jan 08, 2025 at 01:53:44PM -0600, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> 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.

Sorry for piecemealing my comments one by one, but I just though it might be 
a very good idea to explicitly call out a complete lack of graphics support 
in 6.12 BSP (at least for now), especially since this is also targeted for 
scarthgap. 


> Signed-off-by: Ryan Eatmon 
> ---
> v2: Remove the DEFAULT_PREFERENCE settings on the kernel/u-boot recipes.
> 
>  meta-ti-bsp/conf/machine/include/ti-bsp.inc | 2 +-
>  meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2025.01.bb | 2 --
>  .../recipes-kernel/linux/linux-ti-staging-systest_6.12.bb   | 2 --
>  meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.12.bb   | 2 --
>  4 files changed, 1 insertion(+), 7 deletions(-)
> 
> diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
> b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> index 083177dc..f19a0c9c 100644
> --- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> +++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> @@ -4,7 +4,7 @@
>  # well as a dedicated machine override.
>  
>  # Supported options are: mainline, next, ti-6_12, ti-6_6, ti-6_1
> -TI_PREFERRED_BSP ??= "ti-6_6"
> +TI_PREFERRED_BSP ??= "ti-6_12"
>  
>  # Use bsp-* namespace for overrides
>  MACHINEOVERRIDES =. "bsp-${TI_PREFERRED_BSP}:"
> diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2025.01.bb 
> b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2025.01.bb
> index e71008fa..4a3b347d 100644
> --- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2025.01.bb
> +++ b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2025.01.bb
> @@ -1,7 +1,5 @@
>  require u-boot-ti.inc
>  
> -DEFAULT_PREFERENCE = "-1"
> -
>  include ${@ 'recipes-bsp/u-boot/ti-extras.inc' if d.getVar('TI_EXTRAS') else 
> ''}
>  
>  PR = "r0"
> diff --git 
> a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-systest_6.12.bb 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-systest_6.12.bb
> index 8ce23368..b0dcab52 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-systest_6.12.bb
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-systest_6.12.bb
> @@ -1,7 +1,5 @@
>  require linux-ti-staging_6.12.bb
>  
> -DEFAULT_PREFERENCE = "-1"
> -
>  # Look in the generic major.minor directory for files
>  # This will have priority over generic non-rt path
>  FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}-6.12:"
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.12.bb 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.12.bb
> index 7f61b8ab..2ddced64 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.12.bb
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.12.bb
> @@ -6,8 +6,6 @@ LIC_FILES_CHKSUM = 
> "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
>  inherit ti-secdev
>  inherit kernel
>  
> -DEFAULT_PREFERENCE = "-1"
> -
>  require recipes-kernel/linux/setup-defconfig.inc
>  require recipes-kernel/linux/ti-kernel.inc
>  include ${@ 'recipes-kernel/linux/ti-kernel-devicetree-prefix.inc' if 
> d.getVar('KERNEL_DEVICETREE_PREFIX') else ''}
> -- 
> 2.17.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18177): 
https://lists.yoctoproject.org/g/meta-ti/message/18177
Mute This Topic: https://lists.yoctoproject.org/mt/110503466/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master][PATCH] libdce: Fix compile errors

2025-01-10 Thread Denys Dmytriyenko

On Thu, Jan 09, 2025 at 02:03:10PM -0600, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> 
> 
> On 1/9/2025 1:50 PM, Chirag Shilwant wrote:
> >Hi,
> >On 09/01/25 22:46, Ryan Eatmon via lists.yoctoproject.org wrote:
> >>Added a patch to fix 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,
> >>ZjQcmQRYFpfptBannerStart
> >>This message was sent from outside of Texas Instruments.
> >>Do not click links or open attachments unless you recognize the
> >>source of this email and know the content is safe.
> >>Report Suspicious
> >>
> >>ZjQcmQRYFpfptBannerEnd
> >>Added a patch to fix some compile errors:
> >
> >
> >
> >Any particular reasons for fixing the compilation error via a patch
> >rather than updating the sources itself since it lies under git.ti.com [1]
> 
> Because that repo hasn't been updated in 7 years.  If we want to
> work on getting it updated, then we can remove the patch.  But we
> have a build failure today that we need to resolve.

Probably not critical here, but should Upstream-Status then reflect that with 
Inactive-Upstream [lastcommit: date] ?

https://docs.yoctoproject.org/contributor-guide/recipe-style-guide.html#patch-upstream-status


> >[1]: https://git.ti.com/cgit/omapzoom/libdce/
> >
> >-- 
> >Chirag
> >
> >
> >
> >>
> >>../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 
> >>---
> >>  .../files/0001-linux-Fix-compile-errors.patch | 70 +++
> >>  .../libdce/libdce_3.00.15.00.bb   |  5 +-
> >>  2 files changed, 74 insertions(+), 1 deletion(-)
> >>  create mode 100644 
> >>meta-ti-extras/recipes-multimedia/libdce/files/0001-linux-Fix-compile-errors.patch
> >>
> >>diff --git 
> >>a/meta-ti-extras/recipes-multimedia/libdce/files/0001-linux-Fix-compile-errors.patch
> >> 
> >>b/meta-ti-extras/recipes-multimedia/libdce/files/0001-linux-Fix-compile-errors.patch
> >>new file mode 100644
> >>index ..aaee694d
> >>--- /dev/null
> >>+++ 
> >>b/meta-ti-extras/recipes-multimedia/libdce/files/0001-linux-Fix-compile-errors.patch
> >>@@ -0,0 +1,70 @@
> >>+From 23db5f29715b771b8557703f1eea7f1502796d5d Mon Sep 17 00:00:00 2001
> >>+From: Ryan Eatmon 
> >>+Date: Thu, 9 Jan 2025 10:34:17 -0600
> >>+Subject: [PATCH] linux: Fix compile errors
> >>+
> >>+Fix the following compile errors:
> >>+
> >>+../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/mem

Re: [meta-ti][master/scarthgap][PATCH] ti-bsp: Change to 6.12 as the default

2025-01-08 Thread Denys Dmytriyenko

On Wed, Jan 08, 2025 at 08:41:08AM -0600, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> 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.

Do you also need to drop DEFAULT_PREFERENCE = "-1" in corresponding recipes?


> Signed-off-by: Ryan Eatmon 
> ---
>  meta-ti-bsp/conf/machine/include/ti-bsp.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
> b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> index 083177dc..f19a0c9c 100644
> --- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> +++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> @@ -4,7 +4,7 @@
>  # well as a dedicated machine override.
>  
>  # Supported options are: mainline, next, ti-6_12, ti-6_6, ti-6_1
> -TI_PREFERRED_BSP ??= "ti-6_6"
> +TI_PREFERRED_BSP ??= "ti-6_12"
>  
>  # Use bsp-* namespace for overrides
>  MACHINEOVERRIDES =. "bsp-${TI_PREFERRED_BSP}:"
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18167): 
https://lists.yoctoproject.org/g/meta-ti/message/18167
Mute This Topic: https://lists.yoctoproject.org/mt/110497207/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][scarthgap][PATCH 00/13] Add meta-beagle layer

2024-12-19 Thread Denys Dmytriyenko

On Thu, Dec 19, 2024 at 03:53:49PM -0600, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> Backport of the meta-beagle patches from master.

Are there any changes here from my backport to scarthgap I posted yesterday? 
Or is it just a re-post?


> Denys Dmytriyenko (12):
>   conf/machine: rename beagleplay machine to beagleplay-ti
>   meta-beagle: create a separate layer for Beagle platforms
>   meta-beagle: layer.conf: add lz4c to host tools list
>   conf/machine: move "bb_org" BSP settings to meta-beagle
>   conf/machine: split beagleplay config between meta-ti-bsp and
> meta-beagle
>   conf/machine: move remaining Beagle platforms to meta-beagle
>   u-boot-bb_org, linux-bb_org: move "bb_org" providers to meta-beagle
>   linux-bb.org: update Beagle BSP to 6.1.83
>   conf/machine: add BeagleY-AI platform
>   linux-bb.org, u-boot-bb.org: rename recipes with version
>   beagle-bsp, linux-bb.org, u-boot-bb.org: add support for 6.6 BSP
>   linux-bb.org_6.6: disable FORTIFY_SOURCE for now
> 
> Ryan Eatmon (1):
>   meta-beagle: Add SECURITY file
> 
>  {meta-ti-extras => meta-beagle}/COPYING.MIT   | 24 ++---
>  {meta-ti-extras => meta-beagle}/README| 10 +-
>  {meta-ti-bsp => meta-beagle}/SECURITY |  0
>  meta-beagle/conf/layer.conf   | 17 
>  .../conf/machine/beagle-x15.conf  |  5 +-
>  .../conf/machine/beaglebone-ai64-k3r5.conf| 11 ++-
>  .../conf/machine/beaglebone-ai64.conf | 22 +++--
>  .../conf/machine/beaglebone.conf  |  5 +-
>  meta-beagle/conf/machine/beagleplay-k3r5.conf | 11 +++
>  meta-beagle/conf/machine/beagleplay.conf  | 78 +++
>  meta-beagle/conf/machine/beagley-ai-k3r5.conf | 16 
>  meta-beagle/conf/machine/beagley-ai.conf  | 25 +
>  .../conf/machine/include/beagle-bsp.inc   | 43 +
>  .../u-boot/u-boot-bb.org_2023.04.bb   |  7 +-
>  .../u-boot/u-boot-bb.org_2024.10.bb   | 12 +++
>  .../linux/linux-bb.org-6.1}/defconfig |  0
>  .../linux/linux-bb.org-6.6}/defconfig |  0
>  .../linux/linux-bb.org-6.6/no-fortify.cfg |  1 +
>  .../recipes-kernel/linux/linux-bb.org_6.1.bb  | 19 ++--
>  .../recipes-kernel/linux/linux-bb.org_6.6.bb  | 71 ++
>  ...play-k3r5.conf => beagleplay-ti-k3r5.conf} |  1 -
>  meta-ti-bsp/conf/machine/beagleplay-ti.conf   | 49 ++
>  meta-ti-bsp/conf/machine/beagleplay.conf  | 96 ---
>  meta-ti-bsp/conf/machine/include/ti-bsp.inc   | 21 +---
>  ...void-64-bit-division-in-ioc_timer_fn.patch | 56 ---
>  ...-gcc13-keep-large-values-in-a-new-en.patch | 54 ---
>  26 files changed, 382 insertions(+), 272 deletions(-)
>  copy {meta-ti-extras => meta-beagle}/COPYING.MIT (86%)
>  copy {meta-ti-extras => meta-beagle}/README (82%)
>  copy {meta-ti-bsp => meta-beagle}/SECURITY (100%)
>  create mode 100644 meta-beagle/conf/layer.conf
>  rename {meta-ti-bsp => meta-beagle}/conf/machine/beagle-x15.conf (89%)
>  rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64-k3r5.conf 
> (66%)
>  rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64.conf (65%)
>  rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone.conf (92%)
>  create mode 100644 meta-beagle/conf/machine/beagleplay-k3r5.conf
>  create mode 100644 meta-beagle/conf/machine/beagleplay.conf
>  create mode 100644 meta-beagle/conf/machine/beagley-ai-k3r5.conf
>  create mode 100644 meta-beagle/conf/machine/beagley-ai.conf
>  create mode 100644 meta-beagle/conf/machine/include/beagle-bsp.inc
>  rename meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb => 
> meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2023.04.bb (61%)
>  create mode 100644 meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.10.bb
>  copy {meta-ti-bsp/recipes-kernel/linux/linux-bb.org => 
> meta-beagle/recipes-kernel/linux/linux-bb.org-6.1}/defconfig (100%)
>  rename {meta-ti-bsp/recipes-kernel/linux/linux-bb.org => 
> meta-beagle/recipes-kernel/linux/linux-bb.org-6.6}/defconfig (100%)
>  create mode 100644 
> meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg
>  rename meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb => 
> meta-beagle/recipes-kernel/linux/linux-bb.org_6.1.bb (76%)
>  create mode 100644 meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb
>  rename meta-ti-bsp/conf/machine/{beagleplay-k3r5.conf => 
> beagleplay-ti-k3r5.conf} (88%)
>  create mode 100644 meta-ti-bsp/conf/machine/beagleplay-ti.conf
>  delete mode 100644 meta-ti-bsp/conf/machine/beagleplay.conf
>  delete mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
>  delete mode 100644 
> met

Re: [meta-ti][scarthgap/master][PATCH] ti-bsp: Disable GC320 support conditionally on BSP version

2024-12-18 Thread Denys Dmytriyenko

Andrew,

Thanks for the patches. Ryan and I were discussing them yesterday.

Couple points/questions:

1. There's meta-beagle restructuring going on in master right now - the 
changes are in master-next and should be merged to master shortly. I also 
just posted a series to backport these changes to scarthgap. That will 
affect your change below to ti-bsp.inc and will need to be re-spinned.

2. A more generic question... GC320 is a unique peripheral of legacy AM57/J6 
platforms and the driver for it hasn't been updated since 5.10 times. It 
has been disabled globally in the Distro layer for a couple years now. While 
I do understand your change to move this disablenent from the Distro to 
BSP, are there any plans to revive GC320 support and not simply remove it 
altogether?


On Tue, Dec 17, 2024 at 02:59:45PM -0600, Andrew Davis via 
lists.yoctoproject.org wrote:
> 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 
> ---
>  meta-ti-bsp/conf/machine/include/ti-bsp.inc | 18 ++
>  1 file changed, 18 insertions(+)
> 
> diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
> b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> index 814c6ca8..bdc8bef7 100644
> --- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> +++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> @@ -22,6 +22,9 @@ BSP_BOOTLOADER_VERSION:bsp-mainline = "%"
>  # in mainline, usually present in TI staging or derivative like BB.org
>  MACHINE_FEATURES:remove:bsp-mainline = "gpu"
>  
> +# GC320 support requires out-of-tree drivers not available in mainline
> +MACHINE_FEATURES:remove:bsp-mainline = "gc320"
> +
>  # ==
>  # next
>  # upcoming upstream/mainline kernel, u-boot
> @@ -35,6 +38,9 @@ BSP_BOOTLOADER_VERSION:bsp-next = "%"
>  # in next, usually present in TI staging or derivative like BB.org
>  MACHINE_FEATURES:remove:bsp-next = "gpu"
>  
> +# GC320 support requires out-of-tree drivers not available in next
> +MACHINE_FEATURES:remove:bsp-next = "gc320"
> +
>  # ==
>  # ti-6_12
>  # TI staging kernel 6.12, u-boot 2024.10
> @@ -48,6 +54,9 @@ BSP_BOOTLOADER_VERSION:bsp-ti-6_12 = "2024.10%"
>  # in 6.12 yet
>  MACHINE_FEATURES:remove:bsp-ti-6_12 = "gpu"
>  
> +# GC320 support requires out-of-tree drivers not yet available in 6.12
> +MACHINE_FEATURES:remove:bsp-ti-6_12 = "gc320"
> +
>  # ==
>  # ti-6_6
>  # TI staging kernel 6.6, u-boot 2024.04
> @@ -65,6 +74,9 @@ BSP_ROGUE_DRIVER_VERSION:bsp-ti-6_6 = "24%"
>  BSP_ROGUE_UMLIBS_VERSION:bsp-ti-6_6 = "24%"
>  BSP_MESA_PVR_VERSION:bsp-ti-6_6 = "23%"
>  
> +# GC320 support requires out-of-tree drivers not yet available in 6.6
> +MACHINE_FEATURES:remove:bsp-ti-6_6 = "gc320"
> +
>  # ==
>  # ti-6_1
>  # TI staging kernel 6.1, u-boot 2023.04
> @@ -82,6 +94,9 @@ BSP_ROGUE_DRIVER_VERSION:bsp-ti-6_1 = "23%"
>  BSP_ROGUE_UMLIBS_VERSION:bsp-ti-6_1 = "23%"
>  BSP_MESA_PVR_VERSION:bsp-ti-6_1 = "22%"
>  
> +# GC320 support requires out-of-tree drivers not yet available in 6.1
> +MACHINE_FEATURES:remove:bsp-ti-6_1 = "gc320"
> +
>  # ==
>  # bb_org
>  # BeagleBoard.org kernel 6.1, u-boot 2023.04
> @@ -101,6 +116,9 @@ BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
>  BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
>  BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
>  
> +# GC320 support requires out-of-tree drivers not yet available in bb.org
> +MACHINE_FEATURES:remove:bsp-bb_org = "gc320"
> +
>  # ==
>  # sane fallback defaults
>  # if specific values are not defined or bsp is set incorrectly
> -- 
> 2.39.2

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18142): 
https://lists.yoctoproject.org/g/meta-ti/message/18142
Mute This Topic: https://lists.yoctoproject.org/mt/110170195/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 13/13] meta-beagle: Add SECURITY file

2024-12-18 Thread Denys Dmytriyenko

From: Ryan Eatmon 

Add missing SECURITY file required by yocto-check-layer.

Signed-off-by: Ryan Eatmon 
Signed-off-by: Denys Dmytriyenko 
---
 meta-beagle/SECURITY | 20 
 1 file changed, 20 insertions(+)
 create mode 100644 meta-beagle/SECURITY

diff --git a/meta-beagle/SECURITY b/meta-beagle/SECURITY
new file mode 100644
index ..367adc34
--- /dev/null
+++ b/meta-beagle/SECURITY
@@ -0,0 +1,20 @@
+How to Report a Potential Vulnerability?
+
+
+If you would like to report a public issue (for example, one with a released
+CVE number), please report it to the mailing list:
+
+  https://lists.yoctoproject.org/g/meta-ti
+
+If you are dealing with a not-yet released or urgent issue, please send a
+message to one of the maintainers listed in the README.  Include as many
+details as possible:
+  - the layer or software module affected
+  - the recipe and its version
+  - any example code, if available
+
+Branches maintained with security fixes
+---
+
+See https://wiki.yoctoproject.org/wiki/Releases for the list of current
+releases.  We only accept patches for the LTS releases and the master branch.
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18140): 
https://lists.yoctoproject.org/g/meta-ti/message/18140
Mute This Topic: https://lists.yoctoproject.org/mt/110187689/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 03/13] meta-beagle: layer.conf: add lz4c to host tools list

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
Note: this change is not required for scarthgap for now, but it doesn't hurt
and will ensure meta-beagle won't get broken if/when the corresponding change
in OE-Core gets backported.

 meta-beagle/conf/layer.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta-beagle/conf/layer.conf b/meta-beagle/conf/layer.conf
index 0dac4946..d980df8e 100644
--- a/meta-beagle/conf/layer.conf
+++ b/meta-beagle/conf/layer.conf
@@ -13,3 +13,5 @@ LAYERSERIES_COMPAT_meta-beagle = "scarthgap"
 LAYERDEPENDS_meta-beagle = " \
 meta-ti-bsp \
 "
+
+HOSTTOOLS_NONFATAL += "lz4c"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18133): 
https://lists.yoctoproject.org/g/meta-ti/message/18133
Mute This Topic: https://lists.yoctoproject.org/mt/110187681/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 11/13] beagle-bsp, linux-bb.org, u-boot-bb.org: add support for 6.6 BSP

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 meta-beagle/conf/machine/beagle-x15.conf  |  2 +-
 .../conf/machine/beaglebone-ai64-k3r5.conf|  8 ++-
 meta-beagle/conf/machine/beaglebone-ai64.conf | 19 --
 meta-beagle/conf/machine/beaglebone.conf  |  2 +-
 meta-beagle/conf/machine/beagleplay-k3r5.conf |  5 +-
 meta-beagle/conf/machine/beagleplay.conf  | 37 +-
 meta-beagle/conf/machine/beagley-ai-k3r5.conf |  4 +-
 meta-beagle/conf/machine/beagley-ai.conf  |  6 +-
 .../conf/machine/include/beagle-bsp.inc   | 47 +
 .../u-boot/u-boot-bb.org_2024.10.bb   | 12 
 .../linux/linux-bb.org-6.6/defconfig  |  1 +
 .../recipes-kernel/linux/linux-bb.org_6.6.bb  | 68 +++
 12 files changed, 180 insertions(+), 31 deletions(-)
 create mode 100644 meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.10.bb
 create mode 100644 meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/defconfig
 create mode 100644 meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb

diff --git a/meta-beagle/conf/machine/beagle-x15.conf 
b/meta-beagle/conf/machine/beagle-x15.conf
index e9ab5d40..8ad028f4 100644
--- a/meta-beagle/conf/machine/beagle-x15.conf
+++ b/meta-beagle/conf/machine/beagle-x15.conf
@@ -7,7 +7,7 @@ require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PREFIX:bsp-ti-6_1 = ""
-DT_VENDOR_PREFIX:bsp-bb_org = ""
+DT_VENDOR_PREFIX:bsp-bb_org-6_1 = ""
 
 KERNEL_DEVICETREE_PREFIX = " \
 ${DT_VENDOR_PREFIX}am57xx-beagle-x15 \
diff --git a/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf 
b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
index 95d3abc0..4574f82b 100644
--- a/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
@@ -15,8 +15,10 @@ UBOOT_BINARY = "tiboot3.${UBOOT_SUFFIX}"
 UBOOT_IMAGE = "tiboot3-${MAINMACHINE}-${PV}-${PR}.${UBOOT_SUFFIX}"
 UBOOT_SYMLINK = "tiboot3-${MAINMACHINE}.${UBOOT_SUFFIX}"
 
-UBOOT_MACHINE = "j721e_evm_r5_defconfig"
-UBOOT_MACHINE:bsp-ti-6_6 = "j721e_beagleboneai64_r5_defconfig"
+UBOOT_MACHINE = "j721e_beagleboneai64_r5_defconfig"
 
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "j721e_beagleboneai64_r5.config"
+UBOOT_MACHINE:bsp-ti-6_1 = "j721e_evm_r5_defconfig"
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "j721e_beagleboneai64_r5.config"
+
+UBOOT_MACHINE:bsp-bb_org-6_1 = "j721e_evm_r5_defconfig"
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org-6_1 = "j721e_beagleboneai64_r5.config"
diff --git a/meta-beagle/conf/machine/beaglebone-ai64.conf 
b/meta-beagle/conf/machine/beaglebone-ai64.conf
index faffd0bb..a521c8cf 100644
--- a/meta-beagle/conf/machine/beaglebone-ai64.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64.conf
@@ -5,18 +5,25 @@
 require conf/machine/include/j721e.inc
 require conf/machine/include/beagle-bsp.inc
 
-IMAGE_SR1_1_HS_FS_FILES:bsp-bb_org = ""
-IMAGE_SR2_HS_SE_FILES:bsp-bb_org = ""
+IMAGE_SR1_1_HS_FS_FILES = ""
+IMAGE_SR1_1_HS_SE_FILES = ""
+IMAGE_SR2_HS_FS_FILES = ""
+IMAGE_SR2_HS_SE_FILES = ""
 
-UBOOT_MACHINE = "j721e_evm_a72_config"
-UBOOT_MACHINE:bsp-ti-6_6 = "j721e_beagleboneai64_a72_defconfig"
+UBOOT_MACHINE = "j721e_beagleboneai64_a72_defconfig"
 
+UBOOT_MACHINE:bsp-ti-6_1 = "j721e_evm_a72_config"
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "j721e_beagleboneai64_a72.config"
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "j721e_beagleboneai64_a72.config"
+
+UBOOT_MACHINE:bsp-bb_org-6_1 = "j721e_evm_a72_config"
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org-6_1 = "j721e_beagleboneai64_a72.config"
 
 SPL_BINARY:bsp-ti-6_6 = "tispl.bin_unsigned"
 SPL_BINARYNAME:bsp-ti-6_6 = "tispl.bin"
 
+SPL_BINARY:bsp-bb_org-6_6 = "tispl.bin_unsigned"
+SPL_BINARYNAME:bsp-bb_org-6_6 = "tispl.bin"
+
 KERNEL_DEVICETREE_PREFIX = " \
 ti/k3-j721e \
 "
@@ -29,7 +36,7 @@ ti/k3-j721e-evm-quad-port-eth-exp.dtbo \
 ti/k3-j721e-sk.dtb \
 "
 
-KERNEL_DEVICETREE:append:bsp-bb_org = " \
+KERNEL_DEVICETREE:append:bsp-bb_org-6_1 = " \
 ti/k3-j721e-beagleboneai64-dsi-rpi-7inch-panel.dtbo \
 ti/k3-j721e-common-proc-board-infotainment.dtbo \
 ti/k3-j721e-evm-csi2-ov5640.dtbo \
diff --git a/meta-beagle/conf/machine/beaglebone.conf 
b/meta-beagle/conf/machine/beaglebone.conf
index 6048383b..456da618 100644
--- a/meta-beagle/conf/machine/beaglebone.conf
+++ b/meta-beagle/conf/machine/beaglebone.conf
@@ -7,7 +7,7 @@ require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PR

[meta-ti] [scarthgap][PATCH 07/13] u-boot-bb_org, linux-bb_org: move "bb_org" providers to meta-beagle

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 .../recipes-bsp/u-boot/u-boot-bb.org_git.bb | 2 +-
 .../0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch | 0
 ...1-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch | 0
 .../recipes-kernel/linux/linux-bb.org/defconfig | 0
 .../recipes-kernel/linux/linux-bb.org_git.bb| 0
 5 files changed, 1 insertion(+), 1 deletion(-)
 rename {meta-ti-bsp => meta-beagle}/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
(92%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 (100%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 (100%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/defconfig (100%)
 rename {meta-ti-bsp => meta-beagle}/recipes-kernel/linux/linux-bb.org_git.bb 
(100%)

diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
similarity index 92%
rename from meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
rename to meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
index 13286564..0b23effc 100644
--- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
+++ b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
@@ -1,4 +1,4 @@
-require u-boot-ti.inc
+require recipes-bsp/u-boot/u-boot-ti.inc
 
 SUMMARY = "BeagleBoard.org U-Boot"
 
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
similarity index 100%
rename from 
meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
rename to 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
similarity index 100%
rename from 
meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
rename to 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/defconfig 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
similarity index 100%
rename from meta-ti-bsp/recipes-kernel/linux/linux-bb.org/defconfig
rename to meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb 
b/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
similarity index 100%
rename from meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb
rename to meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18135): 
https://lists.yoctoproject.org/g/meta-ti/message/18135
Mute This Topic: https://lists.yoctoproject.org/mt/110187683/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 08/13] linux-bb.org: update Beagle BSP to 6.1.83

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Update Beagle BSP to the latest 6.1.83 kernel version.

Signed-off-by: Denys Dmytriyenko 
---
 .../recipes-kernel/linux/linux-bb.org_git.bb | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb 
b/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
index ef79bfb7..986eda68 100644
--- a/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
+++ b/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
@@ -52,14 +52,14 @@ PB-MIKROBUS-1.dtbo \
 
 S = "${WORKDIR}/git"
 
-# 6.1.80 version for 32-bit
-SRCREV:armv7a = "4ca9ea30768d58c8d4d56d03dd1eaf8c8feb7ef9"
-PV:armv7a = "6.1.80+git"
-BRANCH:armv7a = "v6.1.80-ti-r34"
+# 6.1.83 version for 32-bit
+SRCREV:armv7a = "be9b910b08dfd674e47a2643f35080b005ac3792"
+PV:armv7a = "6.1.83+git"
+BRANCH:armv7a = "v6.1.83-ti-r35"
 
-# 6.1.80 version for 64-bit
-SRCREV:aarch64 = "977c75e082620f15c06c72bcced30f787c14b390"
-PV:aarch64 = "6.1.80+git"
-BRANCH:aarch64 = "v6.1.80-ti-arm64-r49"
+# 6.1.83 version for 64-bit
+SRCREV:aarch64 = "135558243d5a98ed39812b797d2ba6295ef3b86a"
+PV:aarch64 = "6.1.83+git"
+BRANCH:aarch64 = "v6.1.83-ti-arm64-r64"
 
 KERNEL_GIT_URI = "git://github.com/beagleboard/linux.git"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18139): 
https://lists.yoctoproject.org/g/meta-ti/message/18139
Mute This Topic: https://lists.yoctoproject.org/mt/110187688/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 12/13] linux-bb.org_6.6: disable FORTIFY_SOURCE for now

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 .../recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg   | 1 +
 meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb   | 3 +++
 2 files changed, 4 insertions(+)
 create mode 100644 
meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg

diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg 
b/meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg
new file mode 100644
index ..808f9519
--- /dev/null
+++ b/meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg
@@ -0,0 +1 @@
+CONFIG_FORTIFY_SOURCE=n
diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb 
b/meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb
index bf8f8a24..056142d9 100644
--- a/meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb
+++ b/meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb
@@ -66,3 +66,6 @@ PV:aarch64 = "6.6.58+git"
 BRANCH:aarch64 = "v6.6.58-ti-arm64-r16"
 
 KERNEL_GIT_URI = "git://github.com/beagleboard/linux.git"
+
+SRC_URI += "file://no-fortify.cfg"
+KERNEL_CONFIG_FRAGMENTS += "${WORKDIR}/no-fortify.cfg"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18134): 
https://lists.yoctoproject.org/g/meta-ti/message/18134
Mute This Topic: https://lists.yoctoproject.org/mt/110187682/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 06/13] conf/machine: move remaining Beagle platforms to meta-beagle

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Include beagle-bsp.inc to define "bb_org" BSP settings and select that
as a default.

Signed-off-by: Denys Dmytriyenko 
---
 {meta-ti-bsp => meta-beagle}/conf/machine/beagle-x15.conf  | 3 +--
 .../conf/machine/beaglebone-ai64-k3r5.conf | 3 +--
 {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64.conf | 3 +--
 {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone.conf  | 3 +--
 4 files changed, 4 insertions(+), 8 deletions(-)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beagle-x15.conf (94%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64-k3r5.conf 
(94%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64.conf (96%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone.conf (95%)

diff --git a/meta-ti-bsp/conf/machine/beagle-x15.conf 
b/meta-beagle/conf/machine/beagle-x15.conf
similarity index 94%
rename from meta-ti-bsp/conf/machine/beagle-x15.conf
rename to meta-beagle/conf/machine/beagle-x15.conf
index 6f8c435b..e9ab5d40 100644
--- a/meta-ti-bsp/conf/machine/beagle-x15.conf
+++ b/meta-beagle/conf/machine/beagle-x15.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBoard X15
 #@DESCRIPTION: Machine configuration for the BeagleBoard X15
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/am57xx.inc
+require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PREFIX:bsp-ti-6_1 = ""
diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf 
b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
similarity index 94%
rename from meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
rename to meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
index d415a212..95d3abc0 100644
--- a/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone AI-64 (R5F)
 #@DESCRIPTION: Machine configuration for the BeagleBone AI-64 (R5F core)
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/k3r5.inc
+require conf/machine/include/beagle-bsp.inc
 
 SYSFW_SOC = "j721e"
 SYSFW_CONFIG = "evm"
diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf 
b/meta-beagle/conf/machine/beaglebone-ai64.conf
similarity index 96%
rename from meta-ti-bsp/conf/machine/beaglebone-ai64.conf
rename to meta-beagle/conf/machine/beaglebone-ai64.conf
index 56e1ed4e..faffd0bb 100644
--- a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone AI-64 (A72)
 #@DESCRIPTION: Machine configuration for the BeagleBone AI-64 board (A72 core)
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/j721e.inc
+require conf/machine/include/beagle-bsp.inc
 
 IMAGE_SR1_1_HS_FS_FILES:bsp-bb_org = ""
 IMAGE_SR2_HS_SE_FILES:bsp-bb_org = ""
diff --git a/meta-ti-bsp/conf/machine/beaglebone.conf 
b/meta-beagle/conf/machine/beaglebone.conf
similarity index 95%
rename from meta-ti-bsp/conf/machine/beaglebone.conf
rename to meta-beagle/conf/machine/beaglebone.conf
index 0db4d304..6048383b 100644
--- a/meta-ti-bsp/conf/machine/beaglebone.conf
+++ b/meta-beagle/conf/machine/beaglebone.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone machine
 #@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/ti33x.inc
+require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PREFIX:bsp-ti-6_1 = ""
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18138): 
https://lists.yoctoproject.org/g/meta-ti/message/18138
Mute This Topic: https://lists.yoctoproject.org/mt/110187686/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 05/13] conf/machine: split beagleplay config between meta-ti-bsp and meta-beagle

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 meta-beagle/conf/machine/beagleplay-k3r5.conf |  8 +++
 meta-beagle/conf/machine/beagleplay.conf  | 45 
 .../conf/machine/beagleplay-ti-k3r5.conf  |  1 -
 meta-ti-bsp/conf/machine/beagleplay-ti.conf   | 51 +--
 4 files changed, 55 insertions(+), 50 deletions(-)
 create mode 100644 meta-beagle/conf/machine/beagleplay-k3r5.conf
 create mode 100644 meta-beagle/conf/machine/beagleplay.conf

diff --git a/meta-beagle/conf/machine/beagleplay-k3r5.conf 
b/meta-beagle/conf/machine/beagleplay-k3r5.conf
new file mode 100644
index ..1423aa10
--- /dev/null
+++ b/meta-beagle/conf/machine/beagleplay-k3r5.conf
@@ -0,0 +1,8 @@
+#@TYPE: Machine
+#@NAME: BeaglePlay (R5F)
+#@DESCRIPTION: Machine configuration for the BeaglePlay (R5F core)
+
+require conf/machine/beagleplay-ti-k3r5.conf
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_r5.config"
diff --git a/meta-beagle/conf/machine/beagleplay.conf 
b/meta-beagle/conf/machine/beagleplay.conf
new file mode 100644
index ..1977b4c1
--- /dev/null
+++ b/meta-beagle/conf/machine/beagleplay.conf
@@ -0,0 +1,45 @@
+#@TYPE: Machine
+#@NAME: BeaglePlay (A53)
+#@DESCRIPTION: Machine configuration for the BeaglePlay board (A53 core)
+
+require conf/machine/beagleplay-ti.conf
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_a53.config"
+
+KERNEL_DEVICETREE:append:bsp-bb_org = " \
+ti/k3-am625-beagleplay-csi2-ov5640.dtbo \
+ti/k3-am625-beagleplay-csi2-tevi-ov5640.dtbo \
+ti/k3-am625-beagleplay-lincolntech-lcd185-panel.dtbo \
+ti/k3-am625-beaglemod.dtb \
+ti/k3-am625-beaglemod-audio.dtbo \
+ti/k3-am625-beaglemod-can0.dtbo \
+ti/k3-am625-beaglemod-can1.dtbo \
+ti/k3-am625-beaglemod-csi0-ov5640.dtbo \
+ti/k3-am625-beaglemod-eeprom.dtbo \
+ti/k3-am625-beaglemod-eth.dtbo \
+ti/k3-am625-beaglemod-hdmi.dtbo \
+ti/k3-am625-beaglemod-io-expand.dtbo \
+ti/k3-am625-beaglemod-lt-lcd185.dtbo \
+ti/k3-am625-beaglemod-ospi-flash.dtbo \
+ti/k3-am625-beaglemod-rs485-1.dtbo \
+ti/k3-am625-beaglemod-rs485-2.dtbo \
+ti/k3-am625-beaglemod-rtc.dtbo \
+ti/k3-am625-beaglemod-wl1835.dtbo \
+ti/k3-am625-sk-dmtimer-pwm.dtbo \
+ti/k3-am625-sk-ecap-capture.dtbo \
+ti/k3-am625-sk-lincolntech-lcd185-panel.dtbo \
+ti/k3-am625-sk-mcspi-loopback.dtbo \
+ti/k3-am625-sk-microtips-mf101hie-panel.dtbo \
+ti/k3-am625-sk-microtips-mf103hie-lcd2.dtbo \
+ti/k3-am625-sk-pwm.dtbo \
+ti/k3-am625-sk-rpi-hdr-ehrpwm.dtbo \
+ti/k3-am62x-sk-csi2-imx219.dtbo \
+ti/k3-am62x-sk-csi2-ov5640.dtbo \
+ti/k3-am62x-sk-csi2-tevi-ov5640.dtbo \
+ti/k3-am62x-sk-csi2-v3link-fusion.dtbo \
+ti/k3-am62x-sk-eqep.dtbo \
+ti/k3-am62x-sk-hdmi-disable-fastboot.dtbo \
+ti/k3-am62x-sk-lpm-wkup-sources.dtbo \
+ti/k3-am62x-sk-mcan.dtbo \
+"
diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
index 3844ccfa..c27e0abc 100644
--- a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
+++ b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
@@ -12,6 +12,5 @@ UBOOT_MACHINE = "am62x_evm_r5_defconfig"
 UBOOT_MACHINE:bsp-ti-6_6 = "am62x_beagleplay_r5_defconfig"
 UBOOT_MACHINE:bsp-ti-6_12 = "am62x_beagleplay_r5_defconfig"
 
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_r5.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "am625_beagleplay_r5.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-mainline = "beagleplay_r5.config"
diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
index 3ae10171..68d6dced 100644
--- a/meta-ti-bsp/conf/machine/beagleplay-ti.conf
+++ b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
@@ -24,14 +24,14 @@ UBOOT_MACHINE:bsp-ti-6_6 = "am62x_beagleplay_a53_defconfig"
 UBOOT_MACHINE:bsp-ti-6_12 = "am62x_beagleplay_a53_defconfig"
 
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "am625_beagleplay_a53.config"
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_a53.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-mainline = "beagleplay_a53.config"
 
 SPL_BINARY:bsp-ti-6_6 = "tispl.bin_unsigned"
 SPL_BINARYNAME:bsp-ti-6_6 = "tispl.bin"
 
 KERNEL_DEVICETREE_PREFIX = " \
-ti/k3-am625 \
+ti/k3-am625-beagle \
+ti/k3-am625-sk \
 ti/k3-am62x-sk \
 "
 
@@ -39,58 +39,11 @@ KERNEL_DEVICETREE = " \
 ti/k3-am625-beagleplay-csi2-ov5640.dtbo \
 ti/k3-am625-beagleplay-csi2-tevi-ov5640.dtbo \
 ti/k3-am625-beagleplay.dtb \
-ti/k3-am625-phyboard-lyra-1-4-ghz-opp.dt

[meta-ti] [scarthgap][PATCH 02/13] meta-beagle: create a separate layer for Beagle platforms

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 meta-beagle/COPYING.MIT | 17 +
 meta-beagle/README  | 31 +++
 meta-beagle/conf/layer.conf | 15 +++
 3 files changed, 63 insertions(+)
 create mode 100644 meta-beagle/COPYING.MIT
 create mode 100644 meta-beagle/README
 create mode 100644 meta-beagle/conf/layer.conf

diff --git a/meta-beagle/COPYING.MIT b/meta-beagle/COPYING.MIT
new file mode 100644
index ..fb950dc6
--- /dev/null
+++ b/meta-beagle/COPYING.MIT
@@ -0,0 +1,17 @@
+Permission is hereby granted, free of charge, to any person obtaining a copy 
+of this software and associated documentation files (the "Software"), to deal 
+in the Software without restriction, including without limitation the rights 
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 
+copies of the Software, and to permit persons to whom the Software is 
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in 
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 
+THE SOFTWARE.
diff --git a/meta-beagle/README b/meta-beagle/README
new file mode 100644
index ..a17e6433
--- /dev/null
+++ b/meta-beagle/README
@@ -0,0 +1,31 @@
+OpenEmbedded/Yocto layer that extends meta-ti-bsp with BeagleBoard.org 
platforms.
+
+It is hosted on http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/ with the
+source repository at git://git.yoctoproject.org/meta-ti
+
+
+This layer depends on:
+
+URI: git://git.openembedded.org/openembedded-core
+layers: meta
+branch: master
+
+URI: git://git.yoctoproject.org/meta-arm
+layers: meta-arm
+branch: master
+
+URI: git://git.yoctoproject.org/meta-ti
+branch: master
+revision: HEAD
+layers: meta-ti-bsp
+
+
+Send pull requests, patches, comments or questions to:
+meta-ti@lists.yoctoproject.org
+
+Please note - meta-ti mailing list requires subscription for posting:
+https://lists.yoctoproject.org/g/meta-ti
+
+Maintainers:
+Denys Dmytriyenko 
+Ryan Eatmon 
diff --git a/meta-beagle/conf/layer.conf b/meta-beagle/conf/layer.conf
new file mode 100644
index ..0dac4946
--- /dev/null
+++ b/meta-beagle/conf/layer.conf
@@ -0,0 +1,15 @@
+# We have a conf and classes directory, append to BBPATH
+BBPATH .= ":${LAYERDIR}"
+
+# We have a recipes directory, add to BBFILES
+BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "meta-beagle"
+BBFILE_PATTERN_meta-beagle := "^${LAYERDIR}/"
+BBFILE_PRIORITY_meta-beagle = "6"
+
+LAYERSERIES_COMPAT_meta-beagle = "scarthgap"
+
+LAYERDEPENDS_meta-beagle = " \
+meta-ti-bsp \
+"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18132): 
https://lists.yoctoproject.org/g/meta-ti/message/18132
Mute This Topic: https://lists.yoctoproject.org/mt/110187680/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 10/13] linux-bb.org, u-boot-bb.org: rename recipes with version

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 ...bb.org_git.bb => u-boot-bb.org_2023.04.bb} |  0
 .../defconfig |  0
 ...void-64-bit-division-in-ioc_timer_fn.patch | 56 ---
 ...-gcc13-keep-large-values-in-a-new-en.patch | 54 --
 ...inux-bb.org_git.bb => linux-bb.org_6.1.bb} |  3 +
 5 files changed, 3 insertions(+), 110 deletions(-)
 rename meta-beagle/recipes-bsp/u-boot/{u-boot-bb.org_git.bb => 
u-boot-bb.org_2023.04.bb} (100%)
 rename meta-beagle/recipes-kernel/linux/{linux-bb.org => 
linux-bb.org-6.1}/defconfig (100%)
 delete mode 100644 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 delete mode 100644 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 rename meta-beagle/recipes-kernel/linux/{linux-bb.org_git.bb => 
linux-bb.org_6.1.bb} (93%)

diff --git a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2023.04.bb
similarity index 100%
rename from meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
rename to meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2023.04.bb
diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig 
b/meta-beagle/recipes-kernel/linux/linux-bb.org-6.1/defconfig
similarity index 100%
rename from meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
rename to meta-beagle/recipes-kernel/linux/linux-bb.org-6.1/defconfig
diff --git 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
deleted file mode 100644
index a7806c22..
--- 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
+++ /dev/null
@@ -1,56 +0,0 @@
-From 5f2779dfa7b8cc7dfd4a1b6586d86e0d193266f3 Mon Sep 17 00:00:00 2001
-From: Arnd Bergmann 
-Date: Wed, 18 Jan 2023 09:07:01 +0100
-Subject: [PATCH] blk-iocost: avoid 64-bit division in ioc_timer_fn
-
-The behavior of 'enum' types has changed in gcc-13, so now the
-UNBUSY_THR_PCT constant is interpreted as a 64-bit number because
-it is defined as part of the same enum definition as some other
-constants that do not fit within a 32-bit integer. This in turn
-leads to some inefficient code on 32-bit architectures as well
-as a link error:
-
-arm-linux-gnueabi/bin/arm-linux-gnueabi-ld: block/blk-iocost.o: in function 
`ioc_timer_fn':
-blk-iocost.c:(.text+0x68e8): undefined reference to `__aeabi_uldivmod'
-arm-linux-gnueabi-ld: blk-iocost.c:(.text+0x6908): undefined reference to 
`__aeabi_uldivmod'
-
-Split the enum definition to keep the 64-bit timing constants in
-a separate enum type from those constants that can clearly fit
-within a smaller type.
-
-Signed-off-by: Arnd Bergmann 
-Acked-by: Tejun Heo 
-Link: https://lore.kernel.org/r/20230118080706.3303186-1-a...@kernel.org
-Signed-off-by: Jens Axboe 

- block/blk-iocost.c | 8 +---
- 1 file changed, 5 insertions(+), 3 deletions(-)
-
-diff --git a/block/blk-iocost.c b/block/blk-iocost.c
-index 6955605629e4..b691b6bb498f 100644
 a/block/blk-iocost.c
-+++ b/block/blk-iocost.c
-@@ -258,6 +258,11 @@ enum {
-   VRATE_MIN   = VTIME_PER_USEC * VRATE_MIN_PPM / MILLION,
-   VRATE_CLAMP_ADJ_PCT = 4,
-
-+  /* switch iff the conditions are met for longer than this */
-+  AUTOP_CYCLE_NSEC= 10LLU * NSEC_PER_SEC,
-+};
-+
-+enum {
-   /* if IOs end up waiting for requests, issue less */
-   RQ_WAIT_BUSY_PCT= 5,
-
-@@ -296,9 +301,6 @@ enum {
-   /* don't let cmds which take a very long time pin lagging for too long 
*/
-   MAX_LAGGING_PERIODS = 10,
-
--  /* switch iff the conditions are met for longer than this */
--  AUTOP_CYCLE_NSEC= 10LLU * NSEC_PER_SEC,
--
-   /*
-* Count IO size in 4k pages.  The 12bit shift helps keeping
-* size-proportional components of cost calculation in closer
---
-2.40.1
diff --git 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
deleted file mode 100644
index f5d0f476..
--- 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
+++ /dev/null
@@ -1,54 +0,0 @@
-From ff1cc97b1f4c10db224f276d9615b22835b8c424 Mon Sep 17 00:00:00 2001
-From: "Jiri Slaby (SUSE)" 
-Date: Tue, 13 Dec 2022 13:08:26 +0100
-Subject: [PATCH] block/blk-iocost (gcc13

[meta-ti] [scarthgap][PATCH 04/13] conf/machine: move "bb_org" BSP settings to meta-beagle

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Define "bb_org" default BSP settings in meta-beagle layer that all Beagle
platforms will use.

Signed-off-by: Denys Dmytriyenko 
---
 .../conf/machine/include/beagle-bsp.inc   | 24 +++
 meta-ti-bsp/conf/machine/include/ti-bsp.inc   | 21 +---
 2 files changed, 25 insertions(+), 20 deletions(-)
 create mode 100644 meta-beagle/conf/machine/include/beagle-bsp.inc

diff --git a/meta-beagle/conf/machine/include/beagle-bsp.inc 
b/meta-beagle/conf/machine/include/beagle-bsp.inc
new file mode 100644
index ..77d0b483
--- /dev/null
+++ b/meta-beagle/conf/machine/include/beagle-bsp.inc
@@ -0,0 +1,24 @@
+# Use meta-ti-bsp "multi-BSP" facility to create a custom "bb_org" BSP profile
+# with default preferences for Beagle platforms
+
+# Default is bb_org, but can override with any of the existing options
+TI_PREFERRED_BSP ?= "bb_org"
+
+# ==
+# bb_org
+# BeagleBoard.org kernel 6.1, u-boot 2023.04
+# based on TI staging trees with extra Beagle-specific features
+# but may not be up-to-date with TI version
+# ==
+BSP_KERNEL_PROVIDER:bsp-bb_org = "linux-bb.org"
+BSP_KERNEL_VERSION:bsp-bb_org = "%"
+BSP_BOOTLOADER_PROVIDER:bsp-bb_org = "u-boot-bb.org"
+BSP_BOOTLOADER_VERSION:bsp-bb_org = "%"
+
+BSP_SGX_DRIVER_PROVIDER:bsp-bb_org = "ti-sgx-ddk-km"
+BSP_SGX_DRIVER_VERSION:bsp-bb_org = "1.17%"
+BSP_SGX_UMLIBS_VERSION:bsp-bb_org = "1.17%"
+BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org = "ti-img-rogue-driver"
+BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
+BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
+BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
index 814c6ca8..4bbe7668 100644
--- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
+++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
@@ -3,7 +3,7 @@
 # preferences for kernel, bootloader and graphics components, as
 # well as a dedicated machine override.
 
-# Supported options are: mainline, next, ti-6_6, ti-6_1, bb_org
+# Supported options are: mainline, next, ti-6_12, ti-6_6, ti-6_1
 TI_PREFERRED_BSP ??= "ti-6_6"
 
 # Use bsp-* namespace for overrides
@@ -82,25 +82,6 @@ BSP_ROGUE_DRIVER_VERSION:bsp-ti-6_1 = "23%"
 BSP_ROGUE_UMLIBS_VERSION:bsp-ti-6_1 = "23%"
 BSP_MESA_PVR_VERSION:bsp-ti-6_1 = "22%"
 
-# ==
-# bb_org
-# BeagleBoard.org kernel 6.1, u-boot 2023.04
-# based on TI staging trees with extra Beagle-specific features
-# but may not be up-to-date with TI version
-# ==
-BSP_KERNEL_PROVIDER:bsp-bb_org = "linux-bb.org"
-BSP_KERNEL_VERSION:bsp-bb_org = "%"
-BSP_BOOTLOADER_PROVIDER:bsp-bb_org = "u-boot-bb.org"
-BSP_BOOTLOADER_VERSION:bsp-bb_org = "%"
-
-BSP_SGX_DRIVER_PROVIDER:bsp-bb_org = "ti-sgx-ddk-km"
-BSP_SGX_DRIVER_VERSION:bsp-bb_org = "1.17%"
-BSP_SGX_UMLIBS_VERSION:bsp-bb_org = "1.17%"
-BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org = "ti-img-rogue-driver"
-BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
-BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
-BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
-
 # ==
 # sane fallback defaults
 # if specific values are not defined or bsp is set incorrectly
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18131): 
https://lists.yoctoproject.org/g/meta-ti/message/18131
Mute This Topic: https://lists.yoctoproject.org/mt/110187679/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 09/13] conf/machine: add BeagleY-AI platform

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Add machine configuration for BeagleY-AI platform.

Signed-off-by: Denys Dmytriyenko 
---
 meta-beagle/conf/machine/beagley-ai-k3r5.conf | 14 +++
 meta-beagle/conf/machine/beagley-ai.conf  | 23 +++
 .../recipes-bsp/u-boot/u-boot-bb.org_git.bb   |  5 
 3 files changed, 42 insertions(+)
 create mode 100644 meta-beagle/conf/machine/beagley-ai-k3r5.conf
 create mode 100644 meta-beagle/conf/machine/beagley-ai.conf

diff --git a/meta-beagle/conf/machine/beagley-ai-k3r5.conf 
b/meta-beagle/conf/machine/beagley-ai-k3r5.conf
new file mode 100644
index ..87462e72
--- /dev/null
+++ b/meta-beagle/conf/machine/beagley-ai-k3r5.conf
@@ -0,0 +1,14 @@
+#@TYPE: Machine
+#@NAME: BeagleY AI (R5F)
+#@DESCRIPTION: Machine configuration for the BeagleY AI (R5F core)
+
+require conf/machine/include/k3r5.inc
+require conf/machine/include/beagle-bsp.inc
+
+SYSFW_SOC = "j722s"
+SYSFW_CONFIG = "evm"
+SYSFW_SUFFIX = "hs-fs"
+
+UBOOT_MACHINE = "j722s_evm_r5_defconfig"
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am67a_beagley_ai_r5.config"
diff --git a/meta-beagle/conf/machine/beagley-ai.conf 
b/meta-beagle/conf/machine/beagley-ai.conf
new file mode 100644
index ..8dcc9b14
--- /dev/null
+++ b/meta-beagle/conf/machine/beagley-ai.conf
@@ -0,0 +1,23 @@
+#@TYPE: Machine
+#@NAME: BeagleY AI (A53)
+#@DESCRIPTION: Machine configuration for the BeagleY AI board (A53 core)
+
+require conf/machine/include/j722s.inc
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_MACHINE = "j722s_evm_a53_config"
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am67a_beagley_ai_a53.config"
+
+KERNEL_DEVICETREE_PREFIX = " \
+ti/k3-j722s \
+"
+
+KERNEL_DEVICETREE = ""
+
+KERNEL_DEVICETREE:append:bsp-bb_org = " \
+ti/k3-j722s-evm.dtb \
+ti/k3-am67a-beagley-ai.dtb \
+"
+
+MACHINE_GUI_CLASS = "bigscreen"
diff --git a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
index 0b23effc..8e14c495 100644
--- a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
+++ b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
@@ -15,3 +15,8 @@ BRANCH:beagleplay = "v2023.04-ti-09.01.00.008-BeaglePlay"
 BRANCH:beagleplay-k3r5 = "v2023.04-ti-09.01.00.008-BeaglePlay"
 SRCREV:beagleplay = "43791d945f4e5c25bcc19b9c778e8f9d194dc16e"
 SRCREV:beagleplay-k3r5 = "43791d945f4e5c25bcc19b9c778e8f9d194dc16e"
+
+BRANCH:beagley-ai = "v2023.04-ti-09.02.00.009-BeagleY-AI-Production"
+BRANCH:beagley-ai-k3r5 = "v2023.04-ti-09.02.00.009-BeagleY-AI-Production"
+SRCREV:beagley-ai = "93735daa6fe024304934d5a5e93ab05a06abf1a8"
+SRCREV:beagley-ai-k3r5 = "93735daa6fe024304934d5a5e93ab05a06abf1a8"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18136): 
https://lists.yoctoproject.org/g/meta-ti/message/18136
Mute This Topic: https://lists.yoctoproject.org/mt/110187684/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 01/13] conf/machine: rename beagleplay machine to beagleplay-ti

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 .../machine/{beagleplay-k3r5.conf => beagleplay-ti-k3r5.conf} | 0
 meta-ti-bsp/conf/machine/{beagleplay.conf => beagleplay-ti.conf}  | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename meta-ti-bsp/conf/machine/{beagleplay-k3r5.conf => 
beagleplay-ti-k3r5.conf} (100%)
 rename meta-ti-bsp/conf/machine/{beagleplay.conf => beagleplay-ti.conf} (100%)

diff --git a/meta-ti-bsp/conf/machine/beagleplay-k3r5.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beagleplay-k3r5.conf
rename to meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
diff --git a/meta-ti-bsp/conf/machine/beagleplay.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beagleplay.conf
rename to meta-ti-bsp/conf/machine/beagleplay-ti.conf
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18130): 
https://lists.yoctoproject.org/g/meta-ti/message/18130
Mute This Topic: https://lists.yoctoproject.org/mt/110187678/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 2/2] ti-ipc: mark as incompatible with non-Linux builds

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 meta-ti-bsp/recipes-ti/ipc/ti-ipc-common.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-ti-bsp/recipes-ti/ipc/ti-ipc-common.inc 
b/meta-ti-bsp/recipes-ti/ipc/ti-ipc-common.inc
index ec1e71be..da7e4733 100644
--- a/meta-ti-bsp/recipes-ti/ipc/ti-ipc-common.inc
+++ b/meta-ti-bsp/recipes-ti/ipc/ti-ipc-common.inc
@@ -3,7 +3,7 @@ INC_PR = "r0"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 COMPATIBLE_HOST ?= "null"
-COMPATIBLE_HOST:ti-soc = "(.*)"
+COMPATIBLE_HOST:ti-soc = ".*-linux"
 
 PLATFORM = "UNKNOWN"
 PLATFORM:dra7xx = "DRA7XX"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18128): 
https://lists.yoctoproject.org/g/meta-ti/message/18128
Mute This Topic: https://lists.yoctoproject.org/mt/110187480/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [scarthgap][PATCH 1/2] ti-ipc: fix accidental reference to UNPACKDIR from master

2024-12-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb 
b/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb
index c05de508..90472e48 100644
--- a/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb
+++ b/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb
@@ -18,7 +18,7 @@ SRC_URI += "file://tiipclad-daemon.sh \
 file://0001-MmRpc-Stop-looking-for-rpmsg_rpc.h-in-the-kernel.patch 
\
"
 
-CFLAGS += "-I${WORKDIR} -fdebug-prefix-map=${UNPACKDIR}=${TARGET_DBGSRC_DIR}"
+CFLAGS += "-I${WORKDIR} -fdebug-prefix-map=${WORKDIR}=${TARGET_DBGSRC_DIR}"
 
 DAEMON = "UNKNOWN"
 DAEMON:dra7xx = "lad_dra7xx"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18127): 
https://lists.yoctoproject.org/g/meta-ti/message/18127
Mute This Topic: https://lists.yoctoproject.org/mt/110187479/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [master][PATCH 02/12] meta-beagle: create a separate layer for Beagle platforms

2024-12-14 Thread Denys Dmytriyenko

On Sat, Dec 14, 2024 at 10:21:25PM +0530, Chirag Shilwant wrote:
> Hi,
> >diff --git a/meta-beagle/conf/layer.conf b/meta-beagle/conf/layer.conf
> >new file mode 100644
> >index ..df6a77ed
> >--- /dev/null
> >+++ b/meta-beagle/conf/layer.conf
> >@@ -0,0 +1,15 @@
> >+# We have a conf and classes directory, append to BBPATH
> >+BBPATH .= ":${LAYERDIR}"
> >+
> >+# We have a recipes directory, add to BBFILES
> >+BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
> >+
> >+BBFILE_COLLECTIONS += "meta-beagle"
> >+BBFILE_PATTERN_meta-beagle := "^${LAYERDIR}/"
> >+BBFILE_PRIORITY_meta-beagle = "6"
> >+
> >+LAYERSERIES_COMPAT_meta-beagle = "scarthgap styhead walnascar"
> 
> Post [1], LAYERSERIES_COMPAT_meta-beagle shouldn't have scarthgap
> in meta-ti:master since this sublayer has a hard dependency on
> meta-ti-bsp via LAYERDEPENDS & meta-ti-bsp has dropped scarthgap
> from LAYERSERIES_COMPAT in master

v2 posted.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18121): 
https://lists.yoctoproject.org/g/meta-ti/message/18121
Mute This Topic: https://lists.yoctoproject.org/mt/110107251/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH v2 02/12] meta-beagle: create a separate layer for Beagle platforms

2024-12-14 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
v2 - drop scarthgap compatibility

 meta-beagle/COPYING.MIT | 17 +
 meta-beagle/README  | 31 +++
 meta-beagle/conf/layer.conf | 15 +++
 3 files changed, 63 insertions(+)
 create mode 100644 meta-beagle/COPYING.MIT
 create mode 100644 meta-beagle/README
 create mode 100644 meta-beagle/conf/layer.conf

diff --git a/meta-beagle/COPYING.MIT b/meta-beagle/COPYING.MIT
new file mode 100644
index ..fb950dc6
--- /dev/null
+++ b/meta-beagle/COPYING.MIT
@@ -0,0 +1,17 @@
+Permission is hereby granted, free of charge, to any person obtaining a copy 
+of this software and associated documentation files (the "Software"), to deal 
+in the Software without restriction, including without limitation the rights 
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 
+copies of the Software, and to permit persons to whom the Software is 
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in 
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 
+THE SOFTWARE.
diff --git a/meta-beagle/README b/meta-beagle/README
new file mode 100644
index ..a17e6433
--- /dev/null
+++ b/meta-beagle/README
@@ -0,0 +1,31 @@
+OpenEmbedded/Yocto layer that extends meta-ti-bsp with BeagleBoard.org 
platforms.
+
+It is hosted on http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/ with the
+source repository at git://git.yoctoproject.org/meta-ti
+
+
+This layer depends on:
+
+URI: git://git.openembedded.org/openembedded-core
+layers: meta
+branch: master
+
+URI: git://git.yoctoproject.org/meta-arm
+layers: meta-arm
+branch: master
+
+URI: git://git.yoctoproject.org/meta-ti
+branch: master
+revision: HEAD
+layers: meta-ti-bsp
+
+
+Send pull requests, patches, comments or questions to:
+meta-ti@lists.yoctoproject.org
+
+Please note - meta-ti mailing list requires subscription for posting:
+https://lists.yoctoproject.org/g/meta-ti
+
+Maintainers:
+Denys Dmytriyenko 
+Ryan Eatmon 
diff --git a/meta-beagle/conf/layer.conf b/meta-beagle/conf/layer.conf
new file mode 100644
index ..df6a77ed
--- /dev/null
+++ b/meta-beagle/conf/layer.conf
@@ -0,0 +1,15 @@
+# We have a conf and classes directory, append to BBPATH
+BBPATH .= ":${LAYERDIR}"
+
+# We have a recipes directory, add to BBFILES
+BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "meta-beagle"
+BBFILE_PATTERN_meta-beagle := "^${LAYERDIR}/"
+BBFILE_PRIORITY_meta-beagle = "6"
+
+LAYERSERIES_COMPAT_meta-beagle = "styhead walnascar"
+
+LAYERDEPENDS_meta-beagle = " \
+meta-ti-bsp \
+"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18120): 
https://lists.yoctoproject.org/g/meta-ti/message/18120
Mute This Topic: https://lists.yoctoproject.org/mt/110118864/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH 03/12] meta-beagle: layer.conf: add lz4c to host tools list

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
New patch since RFC v2

 meta-beagle/conf/layer.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta-beagle/conf/layer.conf b/meta-beagle/conf/layer.conf
index df6a77ed..cb448b21 100644
--- a/meta-beagle/conf/layer.conf
+++ b/meta-beagle/conf/layer.conf
@@ -13,3 +13,5 @@ LAYERSERIES_COMPAT_meta-beagle = "scarthgap styhead walnascar"
 LAYERDEPENDS_meta-beagle = " \
 meta-ti-bsp \
 "
+
+HOSTTOOLS_NONFATAL += "lz4c"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18107): 
https://lists.yoctoproject.org/g/meta-ti/message/18107
Mute This Topic: https://lists.yoctoproject.org/mt/110107248/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH 01/12] conf/machine: rename beagleplay machine to beagleplay-ti

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
No changes since RFC v2

 .../machine/{beagleplay-k3r5.conf => beagleplay-ti-k3r5.conf} | 0
 meta-ti-bsp/conf/machine/{beagleplay.conf => beagleplay-ti.conf}  | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename meta-ti-bsp/conf/machine/{beagleplay-k3r5.conf => 
beagleplay-ti-k3r5.conf} (100%)
 rename meta-ti-bsp/conf/machine/{beagleplay.conf => beagleplay-ti.conf} (100%)

diff --git a/meta-ti-bsp/conf/machine/beagleplay-k3r5.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beagleplay-k3r5.conf
rename to meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
diff --git a/meta-ti-bsp/conf/machine/beagleplay.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beagleplay.conf
rename to meta-ti-bsp/conf/machine/beagleplay-ti.conf
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18109): 
https://lists.yoctoproject.org/g/meta-ti/message/18109
Mute This Topic: https://lists.yoctoproject.org/mt/110107250/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH 06/12] conf/machine: move remaining Beagle platforms to meta-beagle

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Include beagle-bsp.inc to define "bb_org" BSP settings and select that
as a default.

Signed-off-by: Denys Dmytriyenko 
---
No changes since RFC v2

 {meta-ti-bsp => meta-beagle}/conf/machine/beagle-x15.conf  | 3 +--
 .../conf/machine/beaglebone-ai64-k3r5.conf | 3 +--
 {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64.conf | 3 +--
 {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone.conf  | 3 +--
 4 files changed, 4 insertions(+), 8 deletions(-)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beagle-x15.conf (94%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64-k3r5.conf 
(94%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64.conf (96%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone.conf (95%)

diff --git a/meta-ti-bsp/conf/machine/beagle-x15.conf 
b/meta-beagle/conf/machine/beagle-x15.conf
similarity index 94%
rename from meta-ti-bsp/conf/machine/beagle-x15.conf
rename to meta-beagle/conf/machine/beagle-x15.conf
index 6f8c435b..e9ab5d40 100644
--- a/meta-ti-bsp/conf/machine/beagle-x15.conf
+++ b/meta-beagle/conf/machine/beagle-x15.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBoard X15
 #@DESCRIPTION: Machine configuration for the BeagleBoard X15
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/am57xx.inc
+require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PREFIX:bsp-ti-6_1 = ""
diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf 
b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
similarity index 94%
rename from meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
rename to meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
index d415a212..95d3abc0 100644
--- a/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone AI-64 (R5F)
 #@DESCRIPTION: Machine configuration for the BeagleBone AI-64 (R5F core)
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/k3r5.inc
+require conf/machine/include/beagle-bsp.inc
 
 SYSFW_SOC = "j721e"
 SYSFW_CONFIG = "evm"
diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf 
b/meta-beagle/conf/machine/beaglebone-ai64.conf
similarity index 96%
rename from meta-ti-bsp/conf/machine/beaglebone-ai64.conf
rename to meta-beagle/conf/machine/beaglebone-ai64.conf
index 56e1ed4e..faffd0bb 100644
--- a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone AI-64 (A72)
 #@DESCRIPTION: Machine configuration for the BeagleBone AI-64 board (A72 core)
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/j721e.inc
+require conf/machine/include/beagle-bsp.inc
 
 IMAGE_SR1_1_HS_FS_FILES:bsp-bb_org = ""
 IMAGE_SR2_HS_SE_FILES:bsp-bb_org = ""
diff --git a/meta-ti-bsp/conf/machine/beaglebone.conf 
b/meta-beagle/conf/machine/beaglebone.conf
similarity index 95%
rename from meta-ti-bsp/conf/machine/beaglebone.conf
rename to meta-beagle/conf/machine/beaglebone.conf
index 0db4d304..6048383b 100644
--- a/meta-ti-bsp/conf/machine/beaglebone.conf
+++ b/meta-beagle/conf/machine/beaglebone.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone machine
 #@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/ti33x.inc
+require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PREFIX:bsp-ti-6_1 = ""
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18113): 
https://lists.yoctoproject.org/g/meta-ti/message/18113
Mute This Topic: https://lists.yoctoproject.org/mt/110107254/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH 09/12] conf/machine: add BeagleY-AI platform

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Add machine configuration for BeagleY-AI platform.

Signed-off-by: Denys Dmytriyenko 
---
No changes since RFC v2

 meta-beagle/conf/machine/beagley-ai-k3r5.conf | 14 +++
 meta-beagle/conf/machine/beagley-ai.conf  | 23 +++
 .../recipes-bsp/u-boot/u-boot-bb.org_git.bb   |  5 
 3 files changed, 42 insertions(+)
 create mode 100644 meta-beagle/conf/machine/beagley-ai-k3r5.conf
 create mode 100644 meta-beagle/conf/machine/beagley-ai.conf

diff --git a/meta-beagle/conf/machine/beagley-ai-k3r5.conf 
b/meta-beagle/conf/machine/beagley-ai-k3r5.conf
new file mode 100644
index ..87462e72
--- /dev/null
+++ b/meta-beagle/conf/machine/beagley-ai-k3r5.conf
@@ -0,0 +1,14 @@
+#@TYPE: Machine
+#@NAME: BeagleY AI (R5F)
+#@DESCRIPTION: Machine configuration for the BeagleY AI (R5F core)
+
+require conf/machine/include/k3r5.inc
+require conf/machine/include/beagle-bsp.inc
+
+SYSFW_SOC = "j722s"
+SYSFW_CONFIG = "evm"
+SYSFW_SUFFIX = "hs-fs"
+
+UBOOT_MACHINE = "j722s_evm_r5_defconfig"
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am67a_beagley_ai_r5.config"
diff --git a/meta-beagle/conf/machine/beagley-ai.conf 
b/meta-beagle/conf/machine/beagley-ai.conf
new file mode 100644
index ..8dcc9b14
--- /dev/null
+++ b/meta-beagle/conf/machine/beagley-ai.conf
@@ -0,0 +1,23 @@
+#@TYPE: Machine
+#@NAME: BeagleY AI (A53)
+#@DESCRIPTION: Machine configuration for the BeagleY AI board (A53 core)
+
+require conf/machine/include/j722s.inc
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_MACHINE = "j722s_evm_a53_config"
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am67a_beagley_ai_a53.config"
+
+KERNEL_DEVICETREE_PREFIX = " \
+ti/k3-j722s \
+"
+
+KERNEL_DEVICETREE = ""
+
+KERNEL_DEVICETREE:append:bsp-bb_org = " \
+ti/k3-j722s-evm.dtb \
+ti/k3-am67a-beagley-ai.dtb \
+"
+
+MACHINE_GUI_CLASS = "bigscreen"
diff --git a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
index 1d895f9c..fb7b0c18 100644
--- a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
+++ b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
@@ -17,3 +17,8 @@ BRANCH:beagleplay = "v2023.04-ti-09.01.00.008-BeaglePlay"
 BRANCH:beagleplay-k3r5 = "v2023.04-ti-09.01.00.008-BeaglePlay"
 SRCREV:beagleplay = "43791d945f4e5c25bcc19b9c778e8f9d194dc16e"
 SRCREV:beagleplay-k3r5 = "43791d945f4e5c25bcc19b9c778e8f9d194dc16e"
+
+BRANCH:beagley-ai = "v2023.04-ti-09.02.00.009-BeagleY-AI-Production"
+BRANCH:beagley-ai-k3r5 = "v2023.04-ti-09.02.00.009-BeagleY-AI-Production"
+SRCREV:beagley-ai = "93735daa6fe024304934d5a5e93ab05a06abf1a8"
+SRCREV:beagley-ai-k3r5 = "93735daa6fe024304934d5a5e93ab05a06abf1a8"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18114): 
https://lists.yoctoproject.org/g/meta-ti/message/18114
Mute This Topic: https://lists.yoctoproject.org/mt/110107255/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH 11/12] beagle-bsp, linux-bb.org, u-boot-bb.org: add support for 6.6 BSP

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
Changes since RFC v2:
* bump kernel to 6.6.58 for 64-bit platforms
* add 6.6.32 for 32-bit platforms
* replace upstream 2024.07 u-boot with bb.org 2024.10
* make 6.6 the default for most platforms, except BeagleY-AI
* correct some leftovers of the old :bsp-bb_org override
* refresh device tree lists
* revise u-boot defconfig and config fragment selection
* apply required SWIG patch from meta-ti-bsp to u-boot recipe
* use unsigned SPL binaries

 meta-beagle/conf/machine/beagle-x15.conf  |  2 +-
 .../conf/machine/beaglebone-ai64-k3r5.conf|  8 ++-
 meta-beagle/conf/machine/beaglebone-ai64.conf | 19 --
 meta-beagle/conf/machine/beaglebone.conf  |  2 +-
 meta-beagle/conf/machine/beagleplay-k3r5.conf |  5 +-
 meta-beagle/conf/machine/beagleplay.conf  | 37 +-
 meta-beagle/conf/machine/beagley-ai-k3r5.conf |  4 +-
 meta-beagle/conf/machine/beagley-ai.conf  |  6 +-
 .../conf/machine/include/beagle-bsp.inc   | 47 +
 .../u-boot/u-boot-bb.org_2024.10.bb   | 14 
 .../linux/linux-bb.org-6.6/defconfig  |  1 +
 .../recipes-kernel/linux/linux-bb.org_6.6.bb  | 68 +++
 12 files changed, 182 insertions(+), 31 deletions(-)
 create mode 100644 meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.10.bb
 create mode 100644 meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/defconfig
 create mode 100644 meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb

diff --git a/meta-beagle/conf/machine/beagle-x15.conf 
b/meta-beagle/conf/machine/beagle-x15.conf
index e9ab5d40..8ad028f4 100644
--- a/meta-beagle/conf/machine/beagle-x15.conf
+++ b/meta-beagle/conf/machine/beagle-x15.conf
@@ -7,7 +7,7 @@ require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PREFIX:bsp-ti-6_1 = ""
-DT_VENDOR_PREFIX:bsp-bb_org = ""
+DT_VENDOR_PREFIX:bsp-bb_org-6_1 = ""
 
 KERNEL_DEVICETREE_PREFIX = " \
 ${DT_VENDOR_PREFIX}am57xx-beagle-x15 \
diff --git a/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf 
b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
index 95d3abc0..4574f82b 100644
--- a/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
@@ -15,8 +15,10 @@ UBOOT_BINARY = "tiboot3.${UBOOT_SUFFIX}"
 UBOOT_IMAGE = "tiboot3-${MAINMACHINE}-${PV}-${PR}.${UBOOT_SUFFIX}"
 UBOOT_SYMLINK = "tiboot3-${MAINMACHINE}.${UBOOT_SUFFIX}"
 
-UBOOT_MACHINE = "j721e_evm_r5_defconfig"
-UBOOT_MACHINE:bsp-ti-6_6 = "j721e_beagleboneai64_r5_defconfig"
+UBOOT_MACHINE = "j721e_beagleboneai64_r5_defconfig"
 
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "j721e_beagleboneai64_r5.config"
+UBOOT_MACHINE:bsp-ti-6_1 = "j721e_evm_r5_defconfig"
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "j721e_beagleboneai64_r5.config"
+
+UBOOT_MACHINE:bsp-bb_org-6_1 = "j721e_evm_r5_defconfig"
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org-6_1 = "j721e_beagleboneai64_r5.config"
diff --git a/meta-beagle/conf/machine/beaglebone-ai64.conf 
b/meta-beagle/conf/machine/beaglebone-ai64.conf
index faffd0bb..a521c8cf 100644
--- a/meta-beagle/conf/machine/beaglebone-ai64.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64.conf
@@ -5,18 +5,25 @@
 require conf/machine/include/j721e.inc
 require conf/machine/include/beagle-bsp.inc
 
-IMAGE_SR1_1_HS_FS_FILES:bsp-bb_org = ""
-IMAGE_SR2_HS_SE_FILES:bsp-bb_org = ""
+IMAGE_SR1_1_HS_FS_FILES = ""
+IMAGE_SR1_1_HS_SE_FILES = ""
+IMAGE_SR2_HS_FS_FILES = ""
+IMAGE_SR2_HS_SE_FILES = ""
 
-UBOOT_MACHINE = "j721e_evm_a72_config"
-UBOOT_MACHINE:bsp-ti-6_6 = "j721e_beagleboneai64_a72_defconfig"
+UBOOT_MACHINE = "j721e_beagleboneai64_a72_defconfig"
 
+UBOOT_MACHINE:bsp-ti-6_1 = "j721e_evm_a72_config"
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "j721e_beagleboneai64_a72.config"
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "j721e_beagleboneai64_a72.config"
+
+UBOOT_MACHINE:bsp-bb_org-6_1 = "j721e_evm_a72_config"
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org-6_1 = "j721e_beagleboneai64_a72.config"
 
 SPL_BINARY:bsp-ti-6_6 = "tispl.bin_unsigned"
 SPL_BINARYNAME:bsp-ti-6_6 = "tispl.bin"
 
+SPL_BINARY:bsp-bb_org-6_6 = "tispl.bin_unsigned"
+SPL_BINARYNAME:bsp-bb_org-6_6 = "tispl.bin"
+
 KERNEL_DEVICETREE_PREFIX = " \
 ti/k3-j721e \
 "
@@ -29,7 +36,7 @@ ti/k3-j721e-evm-quad-port-eth-exp.dtbo \
 ti/k3-j721e-sk.dtb \
 "
 
-KERNEL_DEVICETREE:append:bsp-bb_org = " \
+KERNEL_DEVICETREE:append:bsp-bb_org-6_1 = " \
 ti/k3-j721e-beagleboneai64-dsi-rp

[meta-ti] [master][PATCH 12/12] linux-bb.org_6.6: disable FORTIFY_SOURCE for now

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
New patch since RFC v2

 .../recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg   | 1 +
 meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb   | 3 +++
 2 files changed, 4 insertions(+)
 create mode 100644 
meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg

diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg 
b/meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg
new file mode 100644
index ..808f9519
--- /dev/null
+++ b/meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/no-fortify.cfg
@@ -0,0 +1 @@
+CONFIG_FORTIFY_SOURCE=n
diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb 
b/meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb
index bf8f8a24..c50802e4 100644
--- a/meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb
+++ b/meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb
@@ -66,3 +66,6 @@ PV:aarch64 = "6.6.58+git"
 BRANCH:aarch64 = "v6.6.58-ti-arm64-r16"
 
 KERNEL_GIT_URI = "git://github.com/beagleboard/linux.git"
+
+SRC_URI += "file://no-fortify.cfg"
+KERNEL_CONFIG_FRAGMENTS += "${UNPACKDIR}/no-fortify.cfg"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18116): 
https://lists.yoctoproject.org/g/meta-ti/message/18116
Mute This Topic: https://lists.yoctoproject.org/mt/110107257/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH 02/12] meta-beagle: create a separate layer for Beagle platforms

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
No changes since RFC v2

 meta-beagle/COPYING.MIT | 17 +
 meta-beagle/README  | 31 +++
 meta-beagle/conf/layer.conf | 15 +++
 3 files changed, 63 insertions(+)
 create mode 100644 meta-beagle/COPYING.MIT
 create mode 100644 meta-beagle/README
 create mode 100644 meta-beagle/conf/layer.conf

diff --git a/meta-beagle/COPYING.MIT b/meta-beagle/COPYING.MIT
new file mode 100644
index ..fb950dc6
--- /dev/null
+++ b/meta-beagle/COPYING.MIT
@@ -0,0 +1,17 @@
+Permission is hereby granted, free of charge, to any person obtaining a copy 
+of this software and associated documentation files (the "Software"), to deal 
+in the Software without restriction, including without limitation the rights 
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 
+copies of the Software, and to permit persons to whom the Software is 
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in 
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 
+THE SOFTWARE.
diff --git a/meta-beagle/README b/meta-beagle/README
new file mode 100644
index ..a17e6433
--- /dev/null
+++ b/meta-beagle/README
@@ -0,0 +1,31 @@
+OpenEmbedded/Yocto layer that extends meta-ti-bsp with BeagleBoard.org 
platforms.
+
+It is hosted on http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/ with the
+source repository at git://git.yoctoproject.org/meta-ti
+
+
+This layer depends on:
+
+URI: git://git.openembedded.org/openembedded-core
+layers: meta
+branch: master
+
+URI: git://git.yoctoproject.org/meta-arm
+layers: meta-arm
+branch: master
+
+URI: git://git.yoctoproject.org/meta-ti
+branch: master
+revision: HEAD
+layers: meta-ti-bsp
+
+
+Send pull requests, patches, comments or questions to:
+meta-ti@lists.yoctoproject.org
+
+Please note - meta-ti mailing list requires subscription for posting:
+https://lists.yoctoproject.org/g/meta-ti
+
+Maintainers:
+Denys Dmytriyenko 
+Ryan Eatmon 
diff --git a/meta-beagle/conf/layer.conf b/meta-beagle/conf/layer.conf
new file mode 100644
index ..df6a77ed
--- /dev/null
+++ b/meta-beagle/conf/layer.conf
@@ -0,0 +1,15 @@
+# We have a conf and classes directory, append to BBPATH
+BBPATH .= ":${LAYERDIR}"
+
+# We have a recipes directory, add to BBFILES
+BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "meta-beagle"
+BBFILE_PATTERN_meta-beagle := "^${LAYERDIR}/"
+BBFILE_PRIORITY_meta-beagle = "6"
+
+LAYERSERIES_COMPAT_meta-beagle = "scarthgap styhead walnascar"
+
+LAYERDEPENDS_meta-beagle = " \
+meta-ti-bsp \
+"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18110): 
https://lists.yoctoproject.org/g/meta-ti/message/18110
Mute This Topic: https://lists.yoctoproject.org/mt/110107251/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH 07/12] u-boot-bb_org, linux-bb_org: move "bb_org" providers to meta-beagle

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
Changes since RFC v2:
* apply required SWIG patch from meta-ti-bsp to u-boot recipe

 .../recipes-bsp/u-boot/u-boot-bb.org_git.bb   | 4 +++-
 ...001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch | 0
 ...block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch | 0
 .../recipes-kernel/linux/linux-bb.org/defconfig   | 0
 .../recipes-kernel/linux/linux-bb.org_git.bb  | 0
 5 files changed, 3 insertions(+), 1 deletion(-)
 rename {meta-ti-bsp => meta-beagle}/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
(80%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 (100%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 (100%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/defconfig (100%)
 rename {meta-ti-bsp => meta-beagle}/recipes-kernel/linux/linux-bb.org_git.bb 
(100%)

diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
similarity index 80%
rename from meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
rename to meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
index 13286564..1d895f9c 100644
--- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
+++ b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
@@ -1,4 +1,4 @@
-require u-boot-ti.inc
+require recipes-bsp/u-boot/u-boot-ti.inc
 
 SUMMARY = "BeagleBoard.org U-Boot"
 
@@ -6,6 +6,8 @@ COMPATIBLE_MACHINE = "beagle.*"
 
 PV = "2023.04"
 
+SRC_URI += 
"file://0001-scripts-dtc-pylibfdt-libfdt.i_shipped-Use-SWIG_Appen.patch"
+
 UBOOT_GIT_URI = "git://github.com/beagleboard/u-boot.git"
 UBOOT_GIT_PROTOCOL = "https"
 BRANCH = "v2023.04-ti-09.01.00.008"
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
similarity index 100%
rename from 
meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
rename to 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
similarity index 100%
rename from 
meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
rename to 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/defconfig 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
similarity index 100%
rename from meta-ti-bsp/recipes-kernel/linux/linux-bb.org/defconfig
rename to meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb 
b/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
similarity index 100%
rename from meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb
rename to meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18118): 
https://lists.yoctoproject.org/g/meta-ti/message/18118
Mute This Topic: https://lists.yoctoproject.org/mt/110107259/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH 08/12] linux-bb.org: update Beagle BSP to 6.1.83

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Update Beagle BSP to the latest 6.1.83 kernel version.

Signed-off-by: Denys Dmytriyenko 
---
No changes since RFC v2

 .../recipes-kernel/linux/linux-bb.org_git.bb | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb 
b/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
index ef79bfb7..986eda68 100644
--- a/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
+++ b/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
@@ -52,14 +52,14 @@ PB-MIKROBUS-1.dtbo \
 
 S = "${WORKDIR}/git"
 
-# 6.1.80 version for 32-bit
-SRCREV:armv7a = "4ca9ea30768d58c8d4d56d03dd1eaf8c8feb7ef9"
-PV:armv7a = "6.1.80+git"
-BRANCH:armv7a = "v6.1.80-ti-r34"
+# 6.1.83 version for 32-bit
+SRCREV:armv7a = "be9b910b08dfd674e47a2643f35080b005ac3792"
+PV:armv7a = "6.1.83+git"
+BRANCH:armv7a = "v6.1.83-ti-r35"
 
-# 6.1.80 version for 64-bit
-SRCREV:aarch64 = "977c75e082620f15c06c72bcced30f787c14b390"
-PV:aarch64 = "6.1.80+git"
-BRANCH:aarch64 = "v6.1.80-ti-arm64-r49"
+# 6.1.83 version for 64-bit
+SRCREV:aarch64 = "135558243d5a98ed39812b797d2ba6295ef3b86a"
+PV:aarch64 = "6.1.83+git"
+BRANCH:aarch64 = "v6.1.83-ti-arm64-r64"
 
 KERNEL_GIT_URI = "git://github.com/beagleboard/linux.git"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18111): 
https://lists.yoctoproject.org/g/meta-ti/message/18111
Mute This Topic: https://lists.yoctoproject.org/mt/110107252/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH 10/12] linux-bb.org, u-boot-bb.org: rename recipes with version

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
No changes since RFC v2

 ...bb.org_git.bb => u-boot-bb.org_2023.04.bb} |  0
 .../defconfig |  0
 ...void-64-bit-division-in-ioc_timer_fn.patch | 56 ---
 ...-gcc13-keep-large-values-in-a-new-en.patch | 54 --
 ...inux-bb.org_git.bb => linux-bb.org_6.1.bb} |  3 +
 5 files changed, 3 insertions(+), 110 deletions(-)
 rename meta-beagle/recipes-bsp/u-boot/{u-boot-bb.org_git.bb => 
u-boot-bb.org_2023.04.bb} (100%)
 rename meta-beagle/recipes-kernel/linux/{linux-bb.org => 
linux-bb.org-6.1}/defconfig (100%)
 delete mode 100644 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 delete mode 100644 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 rename meta-beagle/recipes-kernel/linux/{linux-bb.org_git.bb => 
linux-bb.org_6.1.bb} (93%)

diff --git a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2023.04.bb
similarity index 100%
rename from meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
rename to meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2023.04.bb
diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig 
b/meta-beagle/recipes-kernel/linux/linux-bb.org-6.1/defconfig
similarity index 100%
rename from meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
rename to meta-beagle/recipes-kernel/linux/linux-bb.org-6.1/defconfig
diff --git 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
deleted file mode 100644
index a7806c22..
--- 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
+++ /dev/null
@@ -1,56 +0,0 @@
-From 5f2779dfa7b8cc7dfd4a1b6586d86e0d193266f3 Mon Sep 17 00:00:00 2001
-From: Arnd Bergmann 
-Date: Wed, 18 Jan 2023 09:07:01 +0100
-Subject: [PATCH] blk-iocost: avoid 64-bit division in ioc_timer_fn
-
-The behavior of 'enum' types has changed in gcc-13, so now the
-UNBUSY_THR_PCT constant is interpreted as a 64-bit number because
-it is defined as part of the same enum definition as some other
-constants that do not fit within a 32-bit integer. This in turn
-leads to some inefficient code on 32-bit architectures as well
-as a link error:
-
-arm-linux-gnueabi/bin/arm-linux-gnueabi-ld: block/blk-iocost.o: in function 
`ioc_timer_fn':
-blk-iocost.c:(.text+0x68e8): undefined reference to `__aeabi_uldivmod'
-arm-linux-gnueabi-ld: blk-iocost.c:(.text+0x6908): undefined reference to 
`__aeabi_uldivmod'
-
-Split the enum definition to keep the 64-bit timing constants in
-a separate enum type from those constants that can clearly fit
-within a smaller type.
-
-Signed-off-by: Arnd Bergmann 
-Acked-by: Tejun Heo 
-Link: https://lore.kernel.org/r/20230118080706.3303186-1-a...@kernel.org
-Signed-off-by: Jens Axboe 

- block/blk-iocost.c | 8 +---
- 1 file changed, 5 insertions(+), 3 deletions(-)
-
-diff --git a/block/blk-iocost.c b/block/blk-iocost.c
-index 6955605629e4..b691b6bb498f 100644
 a/block/blk-iocost.c
-+++ b/block/blk-iocost.c
-@@ -258,6 +258,11 @@ enum {
-   VRATE_MIN   = VTIME_PER_USEC * VRATE_MIN_PPM / MILLION,
-   VRATE_CLAMP_ADJ_PCT = 4,
-
-+  /* switch iff the conditions are met for longer than this */
-+  AUTOP_CYCLE_NSEC= 10LLU * NSEC_PER_SEC,
-+};
-+
-+enum {
-   /* if IOs end up waiting for requests, issue less */
-   RQ_WAIT_BUSY_PCT= 5,
-
-@@ -296,9 +301,6 @@ enum {
-   /* don't let cmds which take a very long time pin lagging for too long 
*/
-   MAX_LAGGING_PERIODS = 10,
-
--  /* switch iff the conditions are met for longer than this */
--  AUTOP_CYCLE_NSEC= 10LLU * NSEC_PER_SEC,
--
-   /*
-* Count IO size in 4k pages.  The 12bit shift helps keeping
-* size-proportional components of cost calculation in closer
---
-2.40.1
diff --git 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
deleted file mode 100644
index f5d0f476..
--- 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
+++ /dev/null
@@ -1,54 +0,0 @@
-From ff1cc97b1f4c10db224f276d9615b22835b8c424 Mon Sep 17 00:00:00 2001
-From: "Jiri Slaby (SUSE)" 
-Date: Tue, 13 Dec 2022 13:08:26 +0100
-Subject:

[meta-ti] [master][PATCH 05/12] conf/machine: split beagleplay config between meta-ti-bsp and meta-beagle

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
No changes since RFC v2

 meta-beagle/conf/machine/beagleplay-k3r5.conf |  8 +++
 meta-beagle/conf/machine/beagleplay.conf  | 45 
 .../conf/machine/beagleplay-ti-k3r5.conf  |  1 -
 meta-ti-bsp/conf/machine/beagleplay-ti.conf   | 51 +--
 4 files changed, 55 insertions(+), 50 deletions(-)
 create mode 100644 meta-beagle/conf/machine/beagleplay-k3r5.conf
 create mode 100644 meta-beagle/conf/machine/beagleplay.conf

diff --git a/meta-beagle/conf/machine/beagleplay-k3r5.conf 
b/meta-beagle/conf/machine/beagleplay-k3r5.conf
new file mode 100644
index ..1423aa10
--- /dev/null
+++ b/meta-beagle/conf/machine/beagleplay-k3r5.conf
@@ -0,0 +1,8 @@
+#@TYPE: Machine
+#@NAME: BeaglePlay (R5F)
+#@DESCRIPTION: Machine configuration for the BeaglePlay (R5F core)
+
+require conf/machine/beagleplay-ti-k3r5.conf
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_r5.config"
diff --git a/meta-beagle/conf/machine/beagleplay.conf 
b/meta-beagle/conf/machine/beagleplay.conf
new file mode 100644
index ..1977b4c1
--- /dev/null
+++ b/meta-beagle/conf/machine/beagleplay.conf
@@ -0,0 +1,45 @@
+#@TYPE: Machine
+#@NAME: BeaglePlay (A53)
+#@DESCRIPTION: Machine configuration for the BeaglePlay board (A53 core)
+
+require conf/machine/beagleplay-ti.conf
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_a53.config"
+
+KERNEL_DEVICETREE:append:bsp-bb_org = " \
+ti/k3-am625-beagleplay-csi2-ov5640.dtbo \
+ti/k3-am625-beagleplay-csi2-tevi-ov5640.dtbo \
+ti/k3-am625-beagleplay-lincolntech-lcd185-panel.dtbo \
+ti/k3-am625-beaglemod.dtb \
+ti/k3-am625-beaglemod-audio.dtbo \
+ti/k3-am625-beaglemod-can0.dtbo \
+ti/k3-am625-beaglemod-can1.dtbo \
+ti/k3-am625-beaglemod-csi0-ov5640.dtbo \
+ti/k3-am625-beaglemod-eeprom.dtbo \
+ti/k3-am625-beaglemod-eth.dtbo \
+ti/k3-am625-beaglemod-hdmi.dtbo \
+ti/k3-am625-beaglemod-io-expand.dtbo \
+ti/k3-am625-beaglemod-lt-lcd185.dtbo \
+ti/k3-am625-beaglemod-ospi-flash.dtbo \
+ti/k3-am625-beaglemod-rs485-1.dtbo \
+ti/k3-am625-beaglemod-rs485-2.dtbo \
+ti/k3-am625-beaglemod-rtc.dtbo \
+ti/k3-am625-beaglemod-wl1835.dtbo \
+ti/k3-am625-sk-dmtimer-pwm.dtbo \
+ti/k3-am625-sk-ecap-capture.dtbo \
+ti/k3-am625-sk-lincolntech-lcd185-panel.dtbo \
+ti/k3-am625-sk-mcspi-loopback.dtbo \
+ti/k3-am625-sk-microtips-mf101hie-panel.dtbo \
+ti/k3-am625-sk-microtips-mf103hie-lcd2.dtbo \
+ti/k3-am625-sk-pwm.dtbo \
+ti/k3-am625-sk-rpi-hdr-ehrpwm.dtbo \
+ti/k3-am62x-sk-csi2-imx219.dtbo \
+ti/k3-am62x-sk-csi2-ov5640.dtbo \
+ti/k3-am62x-sk-csi2-tevi-ov5640.dtbo \
+ti/k3-am62x-sk-csi2-v3link-fusion.dtbo \
+ti/k3-am62x-sk-eqep.dtbo \
+ti/k3-am62x-sk-hdmi-disable-fastboot.dtbo \
+ti/k3-am62x-sk-lpm-wkup-sources.dtbo \
+ti/k3-am62x-sk-mcan.dtbo \
+"
diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
index 3844ccfa..c27e0abc 100644
--- a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
+++ b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
@@ -12,6 +12,5 @@ UBOOT_MACHINE = "am62x_evm_r5_defconfig"
 UBOOT_MACHINE:bsp-ti-6_6 = "am62x_beagleplay_r5_defconfig"
 UBOOT_MACHINE:bsp-ti-6_12 = "am62x_beagleplay_r5_defconfig"
 
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_r5.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "am625_beagleplay_r5.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-mainline = "beagleplay_r5.config"
diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
index 3ae10171..68d6dced 100644
--- a/meta-ti-bsp/conf/machine/beagleplay-ti.conf
+++ b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
@@ -24,14 +24,14 @@ UBOOT_MACHINE:bsp-ti-6_6 = "am62x_beagleplay_a53_defconfig"
 UBOOT_MACHINE:bsp-ti-6_12 = "am62x_beagleplay_a53_defconfig"
 
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "am625_beagleplay_a53.config"
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_a53.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-mainline = "beagleplay_a53.config"
 
 SPL_BINARY:bsp-ti-6_6 = "tispl.bin_unsigned"
 SPL_BINARYNAME:bsp-ti-6_6 = "tispl.bin"
 
 KERNEL_DEVICETREE_PREFIX = " \
-ti/k3-am625 \
+ti/k3-am625-beagle \
+ti/k3-am625-sk \
 ti/k3-am62x-sk \
 "
 
@@ -39,58 +39,11 @@ KERNEL_DEVICETREE = " \
 ti/k3-am625-beagleplay-csi2-ov5640.dtbo \
 ti/k3-am625-beagleplay-csi2-tevi-ov5640.dtbo \
 ti/k3-am625-beagleplay.dtb \
-ti/k3-am625-phyboar

[meta-ti] [master][PATCH 04/12] conf/machine: move "bb_org" BSP settings to meta-beagle

2024-12-13 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Define "bb_org" default BSP settings in meta-beagle layer that all Beagle
platforms will use.

Signed-off-by: Denys Dmytriyenko 
---
No changes since RFC v2

 .../conf/machine/include/beagle-bsp.inc   | 24 +++
 meta-ti-bsp/conf/machine/include/ti-bsp.inc   | 21 +---
 2 files changed, 25 insertions(+), 20 deletions(-)
 create mode 100644 meta-beagle/conf/machine/include/beagle-bsp.inc

diff --git a/meta-beagle/conf/machine/include/beagle-bsp.inc 
b/meta-beagle/conf/machine/include/beagle-bsp.inc
new file mode 100644
index ..77d0b483
--- /dev/null
+++ b/meta-beagle/conf/machine/include/beagle-bsp.inc
@@ -0,0 +1,24 @@
+# Use meta-ti-bsp "multi-BSP" facility to create a custom "bb_org" BSP profile
+# with default preferences for Beagle platforms
+
+# Default is bb_org, but can override with any of the existing options
+TI_PREFERRED_BSP ?= "bb_org"
+
+# ==
+# bb_org
+# BeagleBoard.org kernel 6.1, u-boot 2023.04
+# based on TI staging trees with extra Beagle-specific features
+# but may not be up-to-date with TI version
+# ==
+BSP_KERNEL_PROVIDER:bsp-bb_org = "linux-bb.org"
+BSP_KERNEL_VERSION:bsp-bb_org = "%"
+BSP_BOOTLOADER_PROVIDER:bsp-bb_org = "u-boot-bb.org"
+BSP_BOOTLOADER_VERSION:bsp-bb_org = "%"
+
+BSP_SGX_DRIVER_PROVIDER:bsp-bb_org = "ti-sgx-ddk-km"
+BSP_SGX_DRIVER_VERSION:bsp-bb_org = "1.17%"
+BSP_SGX_UMLIBS_VERSION:bsp-bb_org = "1.17%"
+BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org = "ti-img-rogue-driver"
+BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
+BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
+BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
index 814c6ca8..4bbe7668 100644
--- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
+++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
@@ -3,7 +3,7 @@
 # preferences for kernel, bootloader and graphics components, as
 # well as a dedicated machine override.
 
-# Supported options are: mainline, next, ti-6_6, ti-6_1, bb_org
+# Supported options are: mainline, next, ti-6_12, ti-6_6, ti-6_1
 TI_PREFERRED_BSP ??= "ti-6_6"
 
 # Use bsp-* namespace for overrides
@@ -82,25 +82,6 @@ BSP_ROGUE_DRIVER_VERSION:bsp-ti-6_1 = "23%"
 BSP_ROGUE_UMLIBS_VERSION:bsp-ti-6_1 = "23%"
 BSP_MESA_PVR_VERSION:bsp-ti-6_1 = "22%"
 
-# ==
-# bb_org
-# BeagleBoard.org kernel 6.1, u-boot 2023.04
-# based on TI staging trees with extra Beagle-specific features
-# but may not be up-to-date with TI version
-# ==
-BSP_KERNEL_PROVIDER:bsp-bb_org = "linux-bb.org"
-BSP_KERNEL_VERSION:bsp-bb_org = "%"
-BSP_BOOTLOADER_PROVIDER:bsp-bb_org = "u-boot-bb.org"
-BSP_BOOTLOADER_VERSION:bsp-bb_org = "%"
-
-BSP_SGX_DRIVER_PROVIDER:bsp-bb_org = "ti-sgx-ddk-km"
-BSP_SGX_DRIVER_VERSION:bsp-bb_org = "1.17%"
-BSP_SGX_UMLIBS_VERSION:bsp-bb_org = "1.17%"
-BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org = "ti-img-rogue-driver"
-BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
-BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
-BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
-
 # ==
 # sane fallback defaults
 # if specific values are not defined or bsp is set incorrectly
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18108): 
https://lists.yoctoproject.org/g/meta-ti/message/18108
Mute This Topic: https://lists.yoctoproject.org/mt/110107249/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [master][PATCH] conf: machine: k3: use ARMv8-A as base arch

2024-12-09 Thread Denys Dmytriyenko

On Mon, Dec 09, 2024 at 10:38:56AM +0100, Matthias Schiffer via 
lists.yoctoproject.org wrote:
> On Thu, 2024-11-14 at 15:08 +0100, Matthias Schiffer wrote:
> > All K3 SoCs are Cortex-A53/A72, so arch-armv8a.inc is a more appropriate
> > common base than the very generic arch-arm64.inc. arch-armv8a.inc defaults
> > to enable the CRC extension (DEFAULTTUNE = "armv8a-crc") and allows for
> > easy addition of the ARMv8 crypto extensions by setting the tune to
> > "armv8a-crc-crypto".
> 
> Hi, any comments regarding this patch?

Matthias,

We've discussed this couple of weeks ago and decided to make a slightly 
different change that will also enable your use case as well.

Ryan got busy lately with master breakage, so I should probably send the 
change in for discussion.

-- 
Denys


> > Signed-off-by: Matthias Schiffer 
> > ---
> >  meta-ti-bsp/conf/machine/include/k3.inc | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/meta-ti-bsp/conf/machine/include/k3.inc 
> > b/meta-ti-bsp/conf/machine/include/k3.inc
> > index a296f64f..140564f7 100644
> > --- a/meta-ti-bsp/conf/machine/include/k3.inc
> > +++ b/meta-ti-bsp/conf/machine/include/k3.inc
> > @@ -3,7 +3,7 @@
> >  require conf/machine/include/ti-soc.inc
> >  SOC_FAMILY:append = ":k3"
> >  
> > -require conf/machine/include/arm/arch-arm64.inc
> > +require conf/machine/include/arm/arch-armv8a.inc
> >  
> >  require conf/machine/include/ti-bsp.inc
> >  

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18100): 
https://lists.yoctoproject.org/g/meta-ti/message/18100
Mute This Topic: https://lists.yoctoproject.org/mt/109573384/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master][PATCH] conf: layer.conf: Drop scarthgap from LAYERSERIES_COMPAT

2024-12-04 Thread Denys Dmytriyenko

On Wed, Dec 04, 2024 at 08:35:06PM +0530, Chirag Shilwant wrote:
> After scarthgap release, oe-core switched to use UNPACKDIR instead
> of WORKDIR [1]. Post this change, meta-ti updated all references of
> WORKDIR to UNPACKDIR in master branch.
> 
> Since, UNPACKDIR changes aren't backported to oe-core:scarthgap, we need to
> drop it from LAYERSERIES_COMPAT in meta-ti.
> 
> [1]: 
> https://git.openembedded.org/openembedded-core/commit/?id=e022d62ba917790af2121da57646271ef17c03fa

Yeah, this makes sense


> Signed-off-by: Chirag Shilwant 

Acked-by: Denys Dmytriyenko 


> ---
>  meta-ti-bsp/conf/layer.conf| 2 +-
>  meta-ti-extras/conf/layer.conf | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-ti-bsp/conf/layer.conf b/meta-ti-bsp/conf/layer.conf
> index 0d67c729..6d2b0a9a 100644
> --- a/meta-ti-bsp/conf/layer.conf
> +++ b/meta-ti-bsp/conf/layer.conf
> @@ -9,7 +9,7 @@ BBFILE_COLLECTIONS += "meta-ti-bsp"
>  BBFILE_PATTERN_meta-ti-bsp := "^${LAYERDIR}/"
>  BBFILE_PRIORITY_meta-ti-bsp = "6"
>  
> -LAYERSERIES_COMPAT_meta-ti-bsp = "scarthgap styhead walnascar"
> +LAYERSERIES_COMPAT_meta-ti-bsp = "styhead walnascar"
>  
>  LICENSE_PATH += "${LAYERDIR}/licenses"
>  
> diff --git a/meta-ti-extras/conf/layer.conf b/meta-ti-extras/conf/layer.conf
> index 5c493daa..bd139673 100644
> --- a/meta-ti-extras/conf/layer.conf
> +++ b/meta-ti-extras/conf/layer.conf
> @@ -9,7 +9,7 @@ BBFILE_COLLECTIONS += "meta-ti-extras"
>  BBFILE_PATTERN_meta-ti-extras := "^${LAYERDIR}/"
>  BBFILE_PRIORITY_meta-ti-extras = "6"
>  
> -LAYERSERIES_COMPAT_meta-ti-extras = "scarthgap styhead walnascar"
> +LAYERSERIES_COMPAT_meta-ti-extras = "styhead walnascar"
>  
>  LICENSE_PATH += "${LAYERDIR}/licenses"
>  
> -- 
> 2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18078): 
https://lists.yoctoproject.org/g/meta-ti/message/18078
Mute This Topic: https://lists.yoctoproject.org/mt/109921025/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master/scarthgap][PATCH] ti-ipc: mark as incompatible with non-Linux builds

2024-11-21 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 meta-ti-bsp/recipes-ti/ipc/ti-ipc-common.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-ti-bsp/recipes-ti/ipc/ti-ipc-common.inc 
b/meta-ti-bsp/recipes-ti/ipc/ti-ipc-common.inc
index ec1e71be..da7e4733 100644
--- a/meta-ti-bsp/recipes-ti/ipc/ti-ipc-common.inc
+++ b/meta-ti-bsp/recipes-ti/ipc/ti-ipc-common.inc
@@ -3,7 +3,7 @@ INC_PR = "r0"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 COMPATIBLE_HOST ?= "null"
-COMPATIBLE_HOST:ti-soc = "(.*)"
+COMPATIBLE_HOST:ti-soc = ".*-linux"
 
 PLATFORM = "UNKNOWN"
 PLATFORM:dra7xx = "DRA7XX"
-- 
2.35.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18075): 
https://lists.yoctoproject.org/g/meta-ti/message/18075
Mute This Topic: https://lists.yoctoproject.org/mt/109706723/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap/kirkstone][PATCH] SECURITY: Add file

2024-11-15 Thread Denys Dmytriyenko

On Fri, Nov 15, 2024 at 02:15:09PM -0600, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> Add a SECURITY file with hints for security researchers and other
> parties who might report potential security vulnerabilities.
> 
> Signed-off-by: Ryan Eatmon 

Acked-by: Denys Dmytriyenko 


> ---
>  meta-ti-bsp/SECURITY| 21 +
>  meta-ti-extras/SECURITY | 21 +
>  2 files changed, 42 insertions(+)
>  create mode 100644 meta-ti-bsp/SECURITY
>  create mode 100644 meta-ti-extras/SECURITY
> 
> diff --git a/meta-ti-bsp/SECURITY b/meta-ti-bsp/SECURITY
> new file mode 100644
> index ..784bb209
> --- /dev/null
> +++ b/meta-ti-bsp/SECURITY
> @@ -0,0 +1,21 @@
> +How to Report a Potential Vulnerability?
> +
> +
> +If you would like to report a public issue (for example, one with a released
> +CVE number), please report it to the mailing list:
> +
> +  https://lists.yoctoproject.org/g/meta-ti
> +
> +If you are dealing with a not-yet released or urgent issue, please send a
> +message to one of the maintainers listed in the README.  Include as many
> +details as possible:
> +  - the layer or software module affected
> +  - the recipe and its version
> +  - any example code, if available
> +
> +Branches maintained with security fixes
> +---
> +
> +See https://wiki.yoctoproject.org/wiki/Releases for the list of current
> +releases.  We only accept patches for the LTS releases and the master branch.
> +
> diff --git a/meta-ti-extras/SECURITY b/meta-ti-extras/SECURITY
> new file mode 100644
> index ..784bb209
> --- /dev/null
> +++ b/meta-ti-extras/SECURITY
> @@ -0,0 +1,21 @@
> +How to Report a Potential Vulnerability?
> +
> +
> +If you would like to report a public issue (for example, one with a released
> +CVE number), please report it to the mailing list:
> +
> +  https://lists.yoctoproject.org/g/meta-ti
> +
> +If you are dealing with a not-yet released or urgent issue, please send a
> +message to one of the maintainers listed in the README.  Include as many
> +details as possible:
> +  - the layer or software module affected
> +  - the recipe and its version
> +  - any example code, if available
> +
> +Branches maintained with security fixes
> +---
> +
> +See https://wiki.yoctoproject.org/wiki/Releases for the list of current
> +releases.  We only accept patches for the LTS releases and the master branch.
> +
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18071): 
https://lists.yoctoproject.org/g/meta-ti/message/18071
Mute This Topic: https://lists.yoctoproject.org/mt/109600127/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH v1] meta-ti: Linux configs: Bring selinux related configs

2024-11-14 Thread Denys Dmytriyenko

There are several issues with the patch itself, but that is secondary.

The primary issue is that this adds a new layer dependency to meta-ti-bsp 
(which is also not explicitly configured in layer.conf) - that is a very 
undesirable thing for a BSP layer.

This should be done in a Distro or Product layer (I'm not even shure 
meta-arago-distro should have this by default, to be honest).


On Thu, Nov 14, 2024 at 11:18:08AM +0530, Aashvij Shenai via 
lists.yoctoproject.org wrote:
> Kernel configs that are important for SELinux to be included in the
> Linux kernel are present in the meta-selinux layer.
> 
> Ideally, we wouldn't want to be calling a file from another
> layer since it would become messy. However, bringing those configs
> into meta-ti layer would hit maintainbility issues.
> 
> The root cause of this problem lies in the recipe name. While
> meta-selinux names their bbapend as linux_yocto_%.bbappend, TI has their
> recipe named as linux-ti-staging_%.bb
> 
> Signed-off-by: Aashvij Shenai 
> ---
>  .../linux/linux-ti-staging_%.bbappend | 15 +++
>  1 file changed, 15 insertions(+)
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_%.bbappend
> 
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_%.bbappend 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_%.bbappend
> new file mode 100644
> index ..460df5de
> --- /dev/null
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_%.bbappend
> @@ -0,0 +1,15 @@
> +# The meta-selinux layer includes an selinux.cfg file containing
> +# configs necessary for the Linux kernel to enable SELinux
> +
> +# In order to reduce maintainability issues, the file will 
> +# be retained in meta-selinux layer
> +
> +FILESEXTRAPATHS:prepend := "${@bb.utils.contains('DISTRO_FEATURES', 
> 'selinux', '${TOPDIR}/../sources/meta-selinux/recipes-kernel/linux/files:', 
> '', d)}"
> +
> +SRC_URI += "${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 
> 'file://selinux.cfg', '', d)}"
> +
> +do_configure:append() {
> +if echo "${DISTRO_FEATURES}" | grep -q "selinux"; then
> +cat ${WORKDIR}/selinux.cfg >> ${B}/.config
> +fi
> +}
> \ No newline at end of file
> -- 
> 2.34.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18067): 
https://lists.yoctoproject.org/g/meta-ti/message/18067
Mute This Topic: https://lists.yoctoproject.org/mt/109569106/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH v2 05/10] conf/machine: move remaining Beagle platforms to meta-beagle

2024-11-08 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Include beagle-bsp.inc to define "bb_org" BSP settings and select that
as a default.

Signed-off-by: Denys Dmytriyenko 
---
 {meta-ti-bsp => meta-beagle}/conf/machine/beagle-x15.conf  | 3 +--
 .../conf/machine/beaglebone-ai64-k3r5.conf | 3 +--
 {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64.conf | 3 +--
 {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone.conf  | 3 +--
 4 files changed, 4 insertions(+), 8 deletions(-)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beagle-x15.conf (94%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64-k3r5.conf 
(94%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64.conf (96%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone.conf (95%)

diff --git a/meta-ti-bsp/conf/machine/beagle-x15.conf 
b/meta-beagle/conf/machine/beagle-x15.conf
similarity index 94%
rename from meta-ti-bsp/conf/machine/beagle-x15.conf
rename to meta-beagle/conf/machine/beagle-x15.conf
index 6f8c435b..e9ab5d40 100644
--- a/meta-ti-bsp/conf/machine/beagle-x15.conf
+++ b/meta-beagle/conf/machine/beagle-x15.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBoard X15
 #@DESCRIPTION: Machine configuration for the BeagleBoard X15
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/am57xx.inc
+require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PREFIX:bsp-ti-6_1 = ""
diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf 
b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
similarity index 94%
rename from meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
rename to meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
index d415a212..95d3abc0 100644
--- a/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone AI-64 (R5F)
 #@DESCRIPTION: Machine configuration for the BeagleBone AI-64 (R5F core)
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/k3r5.inc
+require conf/machine/include/beagle-bsp.inc
 
 SYSFW_SOC = "j721e"
 SYSFW_CONFIG = "evm"
diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf 
b/meta-beagle/conf/machine/beaglebone-ai64.conf
similarity index 96%
rename from meta-ti-bsp/conf/machine/beaglebone-ai64.conf
rename to meta-beagle/conf/machine/beaglebone-ai64.conf
index 56e1ed4e..faffd0bb 100644
--- a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone AI-64 (A72)
 #@DESCRIPTION: Machine configuration for the BeagleBone AI-64 board (A72 core)
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/j721e.inc
+require conf/machine/include/beagle-bsp.inc
 
 IMAGE_SR1_1_HS_FS_FILES:bsp-bb_org = ""
 IMAGE_SR2_HS_SE_FILES:bsp-bb_org = ""
diff --git a/meta-ti-bsp/conf/machine/beaglebone.conf 
b/meta-beagle/conf/machine/beaglebone.conf
similarity index 95%
rename from meta-ti-bsp/conf/machine/beaglebone.conf
rename to meta-beagle/conf/machine/beaglebone.conf
index 0db4d304..6048383b 100644
--- a/meta-ti-bsp/conf/machine/beaglebone.conf
+++ b/meta-beagle/conf/machine/beaglebone.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone machine
 #@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/ti33x.inc
+require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PREFIX:bsp-ti-6_1 = ""
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18057): 
https://lists.yoctoproject.org/g/meta-ti/message/18057
Mute This Topic: https://lists.yoctoproject.org/mt/109465465/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [master][RFC PATCH v2 10/10] beagle-bsp, linux-bb.org, u-boot-bb.org: add support for 6.6 BSP

2024-11-08 Thread Denys Dmytriyenko

On Fri, Nov 08, 2024 at 10:50:58AM -0500, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko 
> 
> Some Beagle platforms are switching to 6.6 based Linux kernel and upstream
> U-boot 2024.07. Add corresponding recipes and extend beagle-bsp with required
> settings.
> 
> Note that U-boot recipe added is not BeagleBoard.org or TI specific, but
> version 2024.07 or later is required. Sufficiently newer version from OE-Core
> can also be used, as master now has 2024.10, but scarthgap has an older
> 2024.01 version.
> 
> Signed-off-by: Denys Dmytriyenko 
> ---
>  .../conf/machine/include/beagle-bsp.inc   | 47 +--
>  .../u-boot/u-boot-bb.org_2024.07.bb   | 12 +
>  .../linux/linux-bb.org-6.6/defconfig  |  1 +
>  .../recipes-kernel/linux/linux-bb.org_6.6.bb  | 27 +++
>  4 files changed, 73 insertions(+), 14 deletions(-)
>  create mode 100644 meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.07.bb
>  create mode 100644 
> meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/defconfig
>  create mode 100644 meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb
> 
> diff --git a/meta-beagle/conf/machine/include/beagle-bsp.inc 
> b/meta-beagle/conf/machine/include/beagle-bsp.inc
> index 77d0b483..51de2b73 100644
> --- a/meta-beagle/conf/machine/include/beagle-bsp.inc
> +++ b/meta-beagle/conf/machine/include/beagle-bsp.inc
> @@ -1,24 +1,43 @@
>  # Use meta-ti-bsp "multi-BSP" facility to create a custom "bb_org" BSP 
> profile
>  # with default preferences for Beagle platforms
>  
> -# Default is bb_org, but can override with any of the existing options
> -TI_PREFERRED_BSP ?= "bb_org"
> +# Default is bb_org-6_1, but can override with any of the existing options
> +TI_PREFERRED_BSP ?= "bb_org-6_1"
>  
>  # ==
> -# bb_org
> +# bb_org-6_1
>  # BeagleBoard.org kernel 6.1, u-boot 2023.04
>  # based on TI staging trees with extra Beagle-specific features
>  # but may not be up-to-date with TI version
>  # ==
> -BSP_KERNEL_PROVIDER:bsp-bb_org = "linux-bb.org"
> -BSP_KERNEL_VERSION:bsp-bb_org = "%"
> -BSP_BOOTLOADER_PROVIDER:bsp-bb_org = "u-boot-bb.org"
> -BSP_BOOTLOADER_VERSION:bsp-bb_org = "%"
> +BSP_KERNEL_PROVIDER:bsp-bb_org-6_1 = "linux-bb.org"
> +BSP_KERNEL_VERSION:bsp-bb_org-6_1 = "6.1.%"
> +BSP_BOOTLOADER_PROVIDER:bsp-bb_org-6_1 = "u-boot-bb.org"
> +BSP_BOOTLOADER_VERSION:bsp-bb_org-6_1 = "2023.%"
>  
> -BSP_SGX_DRIVER_PROVIDER:bsp-bb_org = "ti-sgx-ddk-km"
> -BSP_SGX_DRIVER_VERSION:bsp-bb_org = "1.17%"
> -BSP_SGX_UMLIBS_VERSION:bsp-bb_org = "1.17%"
> -BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org = "ti-img-rogue-driver"
> -BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
> -BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
> -BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
> +BSP_SGX_DRIVER_PROVIDER:bsp-bb_or-6_1g = "ti-sgx-ddk-km"

Oops, I'll fix this now ^^


> +BSP_SGX_DRIVER_VERSION:bsp-bb_org-6_1 = "1.17%"
> +BSP_SGX_UMLIBS_VERSION:bsp-bb_org-6_1 = "1.17%"
> +BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org-6_1 = "ti-img-rogue-driver"
> +BSP_ROGUE_DRIVER_VERSION:bsp-bb_org-6_1 = "23%"
> +BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org-6_1 = "23%"
> +BSP_MESA_PVR_VERSION:bsp-bb_org-6_1 = "22%"
> +
> +# ==
> +# bb_org-6_6
> +# BeagleBoard.org kernel 6.6, Upstream u-boot 2024.07
> +# based on TI staging trees with extra Beagle-specific features
> +# but may not be up-to-date with TI version
> +# ==
> +BSP_KERNEL_PROVIDER:bsp-bb_org-6_6 = "linux-bb.org"
> +BSP_KERNEL_VERSION:bsp-bb_org-6_6 = "6.6.%"
> +BSP_BOOTLOADER_PROVIDER:bsp-bb_org-6_6 = "u-boot-bb.org"
> +BSP_BOOTLOADER_VERSION:bsp-bb_org-6_6 = "2024.%"
> +
> +BSP_SGX_DRIVER_PROVIDER:bsp-bb_org-6_6 = "ti-sgx-ddk-km"
> +BSP_SGX_DRIVER_VERSION:bsp-bb_org-6_6 = "1.17%"
> +BSP_SGX_UMLIBS_VERSION:bsp-bb_org-6_6 = "1.17%"
> +BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org-6_6 = "ti-img-rogue-driver"
> +BSP_ROGUE_DRIVER_VERSION:bsp-bb_org-6_6 = "24%"
> +BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org-6_6 = "24%"
> +BSP_MESA_PVR_VERSION:bsp-bb_org-6_6 = "23%"
> diff --git a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.07.bb 
> b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.07.bb
> new file mode 100644
> index ..ca1b051b
> --- /dev/null
> +++ b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.07.bb
> @@ -0,0 +1,12 @@
> +require recipes-bsp/u-boot/u-boot-ti.inc
> +
> +SUMMARY = "Upstream U-Boot

[meta-ti] [master][RFC PATCH v2 02/10] meta-beagle: create a separate layer for Beagle platforms

2024-11-08 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
v2 - fix typo and add README/COPYING.MIT

 meta-beagle/COPYING.MIT | 17 +
 meta-beagle/README  | 31 +++
 meta-beagle/conf/layer.conf | 15 +++
 3 files changed, 63 insertions(+)
 create mode 100644 meta-beagle/COPYING.MIT
 create mode 100644 meta-beagle/README
 create mode 100644 meta-beagle/conf/layer.conf

diff --git a/meta-beagle/COPYING.MIT b/meta-beagle/COPYING.MIT
new file mode 100644
index ..fb950dc6
--- /dev/null
+++ b/meta-beagle/COPYING.MIT
@@ -0,0 +1,17 @@
+Permission is hereby granted, free of charge, to any person obtaining a copy 
+of this software and associated documentation files (the "Software"), to deal 
+in the Software without restriction, including without limitation the rights 
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 
+copies of the Software, and to permit persons to whom the Software is 
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in 
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 
+THE SOFTWARE.
diff --git a/meta-beagle/README b/meta-beagle/README
new file mode 100644
index ..a17e6433
--- /dev/null
+++ b/meta-beagle/README
@@ -0,0 +1,31 @@
+OpenEmbedded/Yocto layer that extends meta-ti-bsp with BeagleBoard.org 
platforms.
+
+It is hosted on http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/ with the
+source repository at git://git.yoctoproject.org/meta-ti
+
+
+This layer depends on:
+
+URI: git://git.openembedded.org/openembedded-core
+layers: meta
+branch: master
+
+URI: git://git.yoctoproject.org/meta-arm
+layers: meta-arm
+branch: master
+
+URI: git://git.yoctoproject.org/meta-ti
+branch: master
+revision: HEAD
+layers: meta-ti-bsp
+
+
+Send pull requests, patches, comments or questions to:
+meta-ti@lists.yoctoproject.org
+
+Please note - meta-ti mailing list requires subscription for posting:
+https://lists.yoctoproject.org/g/meta-ti
+
+Maintainers:
+Denys Dmytriyenko 
+Ryan Eatmon 
diff --git a/meta-beagle/conf/layer.conf b/meta-beagle/conf/layer.conf
new file mode 100644
index ..df6a77ed
--- /dev/null
+++ b/meta-beagle/conf/layer.conf
@@ -0,0 +1,15 @@
+# We have a conf and classes directory, append to BBPATH
+BBPATH .= ":${LAYERDIR}"
+
+# We have a recipes directory, add to BBFILES
+BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "meta-beagle"
+BBFILE_PATTERN_meta-beagle := "^${LAYERDIR}/"
+BBFILE_PRIORITY_meta-beagle = "6"
+
+LAYERSERIES_COMPAT_meta-beagle = "scarthgap styhead walnascar"
+
+LAYERDEPENDS_meta-beagle = " \
+meta-ti-bsp \
+"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18054): 
https://lists.yoctoproject.org/g/meta-ti/message/18054
Mute This Topic: https://lists.yoctoproject.org/mt/109465462/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH v2 03/10] conf/machine: move "bb_org" BSP settings to meta-beagle

2024-11-08 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Define "bb_org" default BSP settings in meta-beagle layer that all Beagle
platforms will use.

Signed-off-by: Denys Dmytriyenko 
---
 .../conf/machine/include/beagle-bsp.inc   | 24 +++
 meta-ti-bsp/conf/machine/include/ti-bsp.inc   | 21 +---
 2 files changed, 25 insertions(+), 20 deletions(-)
 create mode 100644 meta-beagle/conf/machine/include/beagle-bsp.inc

diff --git a/meta-beagle/conf/machine/include/beagle-bsp.inc 
b/meta-beagle/conf/machine/include/beagle-bsp.inc
new file mode 100644
index ..77d0b483
--- /dev/null
+++ b/meta-beagle/conf/machine/include/beagle-bsp.inc
@@ -0,0 +1,24 @@
+# Use meta-ti-bsp "multi-BSP" facility to create a custom "bb_org" BSP profile
+# with default preferences for Beagle platforms
+
+# Default is bb_org, but can override with any of the existing options
+TI_PREFERRED_BSP ?= "bb_org"
+
+# ==
+# bb_org
+# BeagleBoard.org kernel 6.1, u-boot 2023.04
+# based on TI staging trees with extra Beagle-specific features
+# but may not be up-to-date with TI version
+# ==
+BSP_KERNEL_PROVIDER:bsp-bb_org = "linux-bb.org"
+BSP_KERNEL_VERSION:bsp-bb_org = "%"
+BSP_BOOTLOADER_PROVIDER:bsp-bb_org = "u-boot-bb.org"
+BSP_BOOTLOADER_VERSION:bsp-bb_org = "%"
+
+BSP_SGX_DRIVER_PROVIDER:bsp-bb_org = "ti-sgx-ddk-km"
+BSP_SGX_DRIVER_VERSION:bsp-bb_org = "1.17%"
+BSP_SGX_UMLIBS_VERSION:bsp-bb_org = "1.17%"
+BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org = "ti-img-rogue-driver"
+BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
+BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
+BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
index d27bbe3c..fcb7e2bc 100644
--- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
+++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
@@ -3,7 +3,7 @@
 # preferences for kernel, bootloader and graphics components, as
 # well as a dedicated machine override.
 
-# Supported options are: mainline, next, ti-6_6, ti-6_1, bb_org
+# Supported options are: mainline, next, ti-6_12, ti-6_6, ti-6_1
 TI_PREFERRED_BSP ??= "ti-6_6"
 
 # Use bsp-* namespace for overrides
@@ -80,25 +80,6 @@ BSP_ROGUE_DRIVER_VERSION:bsp-ti-6_1 = "23%"
 BSP_ROGUE_UMLIBS_VERSION:bsp-ti-6_1 = "23%"
 BSP_MESA_PVR_VERSION:bsp-ti-6_1 = "22%"
 
-# ==
-# bb_org
-# BeagleBoard.org kernel 6.1, u-boot 2023.04
-# based on TI staging trees with extra Beagle-specific features
-# but may not be up-to-date with TI version
-# ==
-BSP_KERNEL_PROVIDER:bsp-bb_org = "linux-bb.org"
-BSP_KERNEL_VERSION:bsp-bb_org = "%"
-BSP_BOOTLOADER_PROVIDER:bsp-bb_org = "u-boot-bb.org"
-BSP_BOOTLOADER_VERSION:bsp-bb_org = "%"
-
-BSP_SGX_DRIVER_PROVIDER:bsp-bb_org = "ti-sgx-ddk-km"
-BSP_SGX_DRIVER_VERSION:bsp-bb_org = "1.17%"
-BSP_SGX_UMLIBS_VERSION:bsp-bb_org = "1.17%"
-BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org = "ti-img-rogue-driver"
-BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
-BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
-BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
-
 # ==
 # sane fallback defaults
 # if specific values are not defined or bsp is set incorrectly
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18055): 
https://lists.yoctoproject.org/g/meta-ti/message/18055
Mute This Topic: https://lists.yoctoproject.org/mt/109465463/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH v2 08/10] conf/machine: add BeagleY-AI platform

2024-11-08 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Add machine configuration for BeagleY-AI platform.

Signed-off-by: Denys Dmytriyenko 
---
 meta-beagle/conf/machine/beagley-ai-k3r5.conf | 14 +++
 meta-beagle/conf/machine/beagley-ai.conf  | 23 +++
 .../recipes-bsp/u-boot/u-boot-bb.org_git.bb   |  5 
 3 files changed, 42 insertions(+)
 create mode 100644 meta-beagle/conf/machine/beagley-ai-k3r5.conf
 create mode 100644 meta-beagle/conf/machine/beagley-ai.conf

diff --git a/meta-beagle/conf/machine/beagley-ai-k3r5.conf 
b/meta-beagle/conf/machine/beagley-ai-k3r5.conf
new file mode 100644
index ..87462e72
--- /dev/null
+++ b/meta-beagle/conf/machine/beagley-ai-k3r5.conf
@@ -0,0 +1,14 @@
+#@TYPE: Machine
+#@NAME: BeagleY AI (R5F)
+#@DESCRIPTION: Machine configuration for the BeagleY AI (R5F core)
+
+require conf/machine/include/k3r5.inc
+require conf/machine/include/beagle-bsp.inc
+
+SYSFW_SOC = "j722s"
+SYSFW_CONFIG = "evm"
+SYSFW_SUFFIX = "hs-fs"
+
+UBOOT_MACHINE = "j722s_evm_r5_defconfig"
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am67a_beagley_ai_r5.config"
diff --git a/meta-beagle/conf/machine/beagley-ai.conf 
b/meta-beagle/conf/machine/beagley-ai.conf
new file mode 100644
index ..8dcc9b14
--- /dev/null
+++ b/meta-beagle/conf/machine/beagley-ai.conf
@@ -0,0 +1,23 @@
+#@TYPE: Machine
+#@NAME: BeagleY AI (A53)
+#@DESCRIPTION: Machine configuration for the BeagleY AI board (A53 core)
+
+require conf/machine/include/j722s.inc
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_MACHINE = "j722s_evm_a53_config"
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am67a_beagley_ai_a53.config"
+
+KERNEL_DEVICETREE_PREFIX = " \
+ti/k3-j722s \
+"
+
+KERNEL_DEVICETREE = ""
+
+KERNEL_DEVICETREE:append:bsp-bb_org = " \
+ti/k3-j722s-evm.dtb \
+ti/k3-am67a-beagley-ai.dtb \
+"
+
+MACHINE_GUI_CLASS = "bigscreen"
diff --git a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
index 0b23effc..8e14c495 100644
--- a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
+++ b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
@@ -15,3 +15,8 @@ BRANCH:beagleplay = "v2023.04-ti-09.01.00.008-BeaglePlay"
 BRANCH:beagleplay-k3r5 = "v2023.04-ti-09.01.00.008-BeaglePlay"
 SRCREV:beagleplay = "43791d945f4e5c25bcc19b9c778e8f9d194dc16e"
 SRCREV:beagleplay-k3r5 = "43791d945f4e5c25bcc19b9c778e8f9d194dc16e"
+
+BRANCH:beagley-ai = "v2023.04-ti-09.02.00.009-BeagleY-AI-Production"
+BRANCH:beagley-ai-k3r5 = "v2023.04-ti-09.02.00.009-BeagleY-AI-Production"
+SRCREV:beagley-ai = "93735daa6fe024304934d5a5e93ab05a06abf1a8"
+SRCREV:beagley-ai-k3r5 = "93735daa6fe024304934d5a5e93ab05a06abf1a8"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18062): 
https://lists.yoctoproject.org/g/meta-ti/message/18062
Mute This Topic: https://lists.yoctoproject.org/mt/109465471/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH v2 10/10] beagle-bsp, linux-bb.org, u-boot-bb.org: add support for 6.6 BSP

2024-11-08 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Some Beagle platforms are switching to 6.6 based Linux kernel and upstream
U-boot 2024.07. Add corresponding recipes and extend beagle-bsp with required
settings.

Note that U-boot recipe added is not BeagleBoard.org or TI specific, but
version 2024.07 or later is required. Sufficiently newer version from OE-Core
can also be used, as master now has 2024.10, but scarthgap has an older
2024.01 version.

Signed-off-by: Denys Dmytriyenko 
---
 .../conf/machine/include/beagle-bsp.inc   | 47 +--
 .../u-boot/u-boot-bb.org_2024.07.bb   | 12 +
 .../linux/linux-bb.org-6.6/defconfig  |  1 +
 .../recipes-kernel/linux/linux-bb.org_6.6.bb  | 27 +++
 4 files changed, 73 insertions(+), 14 deletions(-)
 create mode 100644 meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.07.bb
 create mode 100644 meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/defconfig
 create mode 100644 meta-beagle/recipes-kernel/linux/linux-bb.org_6.6.bb

diff --git a/meta-beagle/conf/machine/include/beagle-bsp.inc 
b/meta-beagle/conf/machine/include/beagle-bsp.inc
index 77d0b483..51de2b73 100644
--- a/meta-beagle/conf/machine/include/beagle-bsp.inc
+++ b/meta-beagle/conf/machine/include/beagle-bsp.inc
@@ -1,24 +1,43 @@
 # Use meta-ti-bsp "multi-BSP" facility to create a custom "bb_org" BSP profile
 # with default preferences for Beagle platforms
 
-# Default is bb_org, but can override with any of the existing options
-TI_PREFERRED_BSP ?= "bb_org"
+# Default is bb_org-6_1, but can override with any of the existing options
+TI_PREFERRED_BSP ?= "bb_org-6_1"
 
 # ==
-# bb_org
+# bb_org-6_1
 # BeagleBoard.org kernel 6.1, u-boot 2023.04
 # based on TI staging trees with extra Beagle-specific features
 # but may not be up-to-date with TI version
 # ==
-BSP_KERNEL_PROVIDER:bsp-bb_org = "linux-bb.org"
-BSP_KERNEL_VERSION:bsp-bb_org = "%"
-BSP_BOOTLOADER_PROVIDER:bsp-bb_org = "u-boot-bb.org"
-BSP_BOOTLOADER_VERSION:bsp-bb_org = "%"
+BSP_KERNEL_PROVIDER:bsp-bb_org-6_1 = "linux-bb.org"
+BSP_KERNEL_VERSION:bsp-bb_org-6_1 = "6.1.%"
+BSP_BOOTLOADER_PROVIDER:bsp-bb_org-6_1 = "u-boot-bb.org"
+BSP_BOOTLOADER_VERSION:bsp-bb_org-6_1 = "2023.%"
 
-BSP_SGX_DRIVER_PROVIDER:bsp-bb_org = "ti-sgx-ddk-km"
-BSP_SGX_DRIVER_VERSION:bsp-bb_org = "1.17%"
-BSP_SGX_UMLIBS_VERSION:bsp-bb_org = "1.17%"
-BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org = "ti-img-rogue-driver"
-BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
-BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
-BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
+BSP_SGX_DRIVER_PROVIDER:bsp-bb_or-6_1g = "ti-sgx-ddk-km"
+BSP_SGX_DRIVER_VERSION:bsp-bb_org-6_1 = "1.17%"
+BSP_SGX_UMLIBS_VERSION:bsp-bb_org-6_1 = "1.17%"
+BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org-6_1 = "ti-img-rogue-driver"
+BSP_ROGUE_DRIVER_VERSION:bsp-bb_org-6_1 = "23%"
+BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org-6_1 = "23%"
+BSP_MESA_PVR_VERSION:bsp-bb_org-6_1 = "22%"
+
+# ==
+# bb_org-6_6
+# BeagleBoard.org kernel 6.6, Upstream u-boot 2024.07
+# based on TI staging trees with extra Beagle-specific features
+# but may not be up-to-date with TI version
+# ==
+BSP_KERNEL_PROVIDER:bsp-bb_org-6_6 = "linux-bb.org"
+BSP_KERNEL_VERSION:bsp-bb_org-6_6 = "6.6.%"
+BSP_BOOTLOADER_PROVIDER:bsp-bb_org-6_6 = "u-boot-bb.org"
+BSP_BOOTLOADER_VERSION:bsp-bb_org-6_6 = "2024.%"
+
+BSP_SGX_DRIVER_PROVIDER:bsp-bb_org-6_6 = "ti-sgx-ddk-km"
+BSP_SGX_DRIVER_VERSION:bsp-bb_org-6_6 = "1.17%"
+BSP_SGX_UMLIBS_VERSION:bsp-bb_org-6_6 = "1.17%"
+BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org-6_6 = "ti-img-rogue-driver"
+BSP_ROGUE_DRIVER_VERSION:bsp-bb_org-6_6 = "24%"
+BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org-6_6 = "24%"
+BSP_MESA_PVR_VERSION:bsp-bb_org-6_6 = "23%"
diff --git a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.07.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.07.bb
new file mode 100644
index ..ca1b051b
--- /dev/null
+++ b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2024.07.bb
@@ -0,0 +1,12 @@
+require recipes-bsp/u-boot/u-boot-ti.inc
+
+SUMMARY = "Upstream U-Boot for BeagleBoard.org devices"
+
+COMPATIBLE_MACHINE = "beagle.*"
+
+PV = "2024.07"
+
+UBOOT_GIT_URI = "git://github.com/u-boot/u-boot.git"
+UBOOT_GIT_PROTOCOL = "https"
+BRANCH = "master"
+SRCREV = "3f772959501c99fbe5aa0b22a36efe3478d1ae1c"
diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/defconfig 
b/meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/defconfig
new file mode 100644
index ..a5de2e24
--- /dev/null
+++ b/meta-beagle/recipes-kernel/linux/linux-bb.org-6.6/defconfig
@@ -0

[meta-ti] [master][RFC PATCH v2 06/10] u-boot-bb_org, linux-bb_org: move "bb_org" providers to meta-beagle

2024-11-08 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 .../recipes-bsp/u-boot/u-boot-bb.org_git.bb | 2 +-
 .../0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch | 0
 ...1-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch | 0
 .../recipes-kernel/linux/linux-bb.org/defconfig | 0
 .../recipes-kernel/linux/linux-bb.org_git.bb| 0
 5 files changed, 1 insertion(+), 1 deletion(-)
 rename {meta-ti-bsp => meta-beagle}/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
(92%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 (100%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 (100%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/defconfig (100%)
 rename {meta-ti-bsp => meta-beagle}/recipes-kernel/linux/linux-bb.org_git.bb 
(100%)

diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
similarity index 92%
rename from meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
rename to meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
index 13286564..0b23effc 100644
--- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
+++ b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
@@ -1,4 +1,4 @@
-require u-boot-ti.inc
+require recipes-bsp/u-boot/u-boot-ti.inc
 
 SUMMARY = "BeagleBoard.org U-Boot"
 
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
similarity index 100%
rename from 
meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
rename to 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
similarity index 100%
rename from 
meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
rename to 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/defconfig 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
similarity index 100%
rename from meta-ti-bsp/recipes-kernel/linux/linux-bb.org/defconfig
rename to meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb 
b/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
similarity index 100%
rename from meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb
rename to meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18059): 
https://lists.yoctoproject.org/g/meta-ti/message/18059
Mute This Topic: https://lists.yoctoproject.org/mt/109465468/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH v2 07/10] linux-bb.org: update Beagle BSP to 6.1.83

2024-11-08 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Update Beagle BSP to the latest 6.1.83 kernel version.

Signed-off-by: Denys Dmytriyenko 
---
 .../recipes-kernel/linux/linux-bb.org_git.bb | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb 
b/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
index ef79bfb7..986eda68 100644
--- a/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
+++ b/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
@@ -52,14 +52,14 @@ PB-MIKROBUS-1.dtbo \
 
 S = "${WORKDIR}/git"
 
-# 6.1.80 version for 32-bit
-SRCREV:armv7a = "4ca9ea30768d58c8d4d56d03dd1eaf8c8feb7ef9"
-PV:armv7a = "6.1.80+git"
-BRANCH:armv7a = "v6.1.80-ti-r34"
+# 6.1.83 version for 32-bit
+SRCREV:armv7a = "be9b910b08dfd674e47a2643f35080b005ac3792"
+PV:armv7a = "6.1.83+git"
+BRANCH:armv7a = "v6.1.83-ti-r35"
 
-# 6.1.80 version for 64-bit
-SRCREV:aarch64 = "977c75e082620f15c06c72bcced30f787c14b390"
-PV:aarch64 = "6.1.80+git"
-BRANCH:aarch64 = "v6.1.80-ti-arm64-r49"
+# 6.1.83 version for 64-bit
+SRCREV:aarch64 = "135558243d5a98ed39812b797d2ba6295ef3b86a"
+PV:aarch64 = "6.1.83+git"
+BRANCH:aarch64 = "v6.1.83-ti-arm64-r64"
 
 KERNEL_GIT_URI = "git://github.com/beagleboard/linux.git"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18058): 
https://lists.yoctoproject.org/g/meta-ti/message/18058
Mute This Topic: https://lists.yoctoproject.org/mt/109465467/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH v2 01/10] conf/machine: rename beagleplay machine to beagleplay-ti

2024-11-08 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 .../machine/{beagleplay-k3r5.conf => beagleplay-ti-k3r5.conf} | 0
 meta-ti-bsp/conf/machine/{beagleplay.conf => beagleplay-ti.conf}  | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename meta-ti-bsp/conf/machine/{beagleplay-k3r5.conf => 
beagleplay-ti-k3r5.conf} (100%)
 rename meta-ti-bsp/conf/machine/{beagleplay.conf => beagleplay-ti.conf} (100%)

diff --git a/meta-ti-bsp/conf/machine/beagleplay-k3r5.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beagleplay-k3r5.conf
rename to meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
diff --git a/meta-ti-bsp/conf/machine/beagleplay.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beagleplay.conf
rename to meta-ti-bsp/conf/machine/beagleplay-ti.conf
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18053): 
https://lists.yoctoproject.org/g/meta-ti/message/18053
Mute This Topic: https://lists.yoctoproject.org/mt/109465461/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH v2 09/10] linux-bb.org, u-boot-bb.org: rename recipes with version

2024-11-08 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 ...bb.org_git.bb => u-boot-bb.org_2023.04.bb} |  0
 .../defconfig |  0
 ...void-64-bit-division-in-ioc_timer_fn.patch | 56 ---
 ...-gcc13-keep-large-values-in-a-new-en.patch | 54 --
 ...inux-bb.org_git.bb => linux-bb.org_6.1.bb} |  3 +
 5 files changed, 3 insertions(+), 110 deletions(-)
 rename meta-beagle/recipes-bsp/u-boot/{u-boot-bb.org_git.bb => 
u-boot-bb.org_2023.04.bb} (100%)
 rename meta-beagle/recipes-kernel/linux/{linux-bb.org => 
linux-bb.org-6.1}/defconfig (100%)
 delete mode 100644 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 delete mode 100644 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 rename meta-beagle/recipes-kernel/linux/{linux-bb.org_git.bb => 
linux-bb.org_6.1.bb} (93%)

diff --git a/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2023.04.bb
similarity index 100%
rename from meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
rename to meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_2023.04.bb
diff --git a/meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig 
b/meta-beagle/recipes-kernel/linux/linux-bb.org-6.1/defconfig
similarity index 100%
rename from meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
rename to meta-beagle/recipes-kernel/linux/linux-bb.org-6.1/defconfig
diff --git 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
deleted file mode 100644
index a7806c22..
--- 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
+++ /dev/null
@@ -1,56 +0,0 @@
-From 5f2779dfa7b8cc7dfd4a1b6586d86e0d193266f3 Mon Sep 17 00:00:00 2001
-From: Arnd Bergmann 
-Date: Wed, 18 Jan 2023 09:07:01 +0100
-Subject: [PATCH] blk-iocost: avoid 64-bit division in ioc_timer_fn
-
-The behavior of 'enum' types has changed in gcc-13, so now the
-UNBUSY_THR_PCT constant is interpreted as a 64-bit number because
-it is defined as part of the same enum definition as some other
-constants that do not fit within a 32-bit integer. This in turn
-leads to some inefficient code on 32-bit architectures as well
-as a link error:
-
-arm-linux-gnueabi/bin/arm-linux-gnueabi-ld: block/blk-iocost.o: in function 
`ioc_timer_fn':
-blk-iocost.c:(.text+0x68e8): undefined reference to `__aeabi_uldivmod'
-arm-linux-gnueabi-ld: blk-iocost.c:(.text+0x6908): undefined reference to 
`__aeabi_uldivmod'
-
-Split the enum definition to keep the 64-bit timing constants in
-a separate enum type from those constants that can clearly fit
-within a smaller type.
-
-Signed-off-by: Arnd Bergmann 
-Acked-by: Tejun Heo 
-Link: https://lore.kernel.org/r/20230118080706.3303186-1-a...@kernel.org
-Signed-off-by: Jens Axboe 

- block/blk-iocost.c | 8 +---
- 1 file changed, 5 insertions(+), 3 deletions(-)
-
-diff --git a/block/blk-iocost.c b/block/blk-iocost.c
-index 6955605629e4..b691b6bb498f 100644
 a/block/blk-iocost.c
-+++ b/block/blk-iocost.c
-@@ -258,6 +258,11 @@ enum {
-   VRATE_MIN   = VTIME_PER_USEC * VRATE_MIN_PPM / MILLION,
-   VRATE_CLAMP_ADJ_PCT = 4,
-
-+  /* switch iff the conditions are met for longer than this */
-+  AUTOP_CYCLE_NSEC= 10LLU * NSEC_PER_SEC,
-+};
-+
-+enum {
-   /* if IOs end up waiting for requests, issue less */
-   RQ_WAIT_BUSY_PCT= 5,
-
-@@ -296,9 +301,6 @@ enum {
-   /* don't let cmds which take a very long time pin lagging for too long 
*/
-   MAX_LAGGING_PERIODS = 10,
-
--  /* switch iff the conditions are met for longer than this */
--  AUTOP_CYCLE_NSEC= 10LLU * NSEC_PER_SEC,
--
-   /*
-* Count IO size in 4k pages.  The 12bit shift helps keeping
-* size-proportional components of cost calculation in closer
---
-2.40.1
diff --git 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
deleted file mode 100644
index f5d0f476..
--- 
a/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
+++ /dev/null
@@ -1,54 +0,0 @@
-From ff1cc97b1f4c10db224f276d9615b22835b8c424 Mon Sep 17 00:00:00 2001
-From: "Jiri Slaby (SUSE)" 
-Date: Tue, 13 Dec 2022 13:08:26 +0100
-Subject: [PATCH] block/blk-iocost (gcc13

[meta-ti] [master][RFC PATCH v2 04/10] conf/machine: split beagleplay config between meta-ti-bsp and meta-beagle

2024-11-08 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 meta-beagle/conf/machine/beagleplay-k3r5.conf |  8 +++
 meta-beagle/conf/machine/beagleplay.conf  | 45 
 .../conf/machine/beagleplay-ti-k3r5.conf  |  1 -
 meta-ti-bsp/conf/machine/beagleplay-ti.conf   | 51 +--
 4 files changed, 55 insertions(+), 50 deletions(-)
 create mode 100644 meta-beagle/conf/machine/beagleplay-k3r5.conf
 create mode 100644 meta-beagle/conf/machine/beagleplay.conf

diff --git a/meta-beagle/conf/machine/beagleplay-k3r5.conf 
b/meta-beagle/conf/machine/beagleplay-k3r5.conf
new file mode 100644
index ..1423aa10
--- /dev/null
+++ b/meta-beagle/conf/machine/beagleplay-k3r5.conf
@@ -0,0 +1,8 @@
+#@TYPE: Machine
+#@NAME: BeaglePlay (R5F)
+#@DESCRIPTION: Machine configuration for the BeaglePlay (R5F core)
+
+require conf/machine/beagleplay-ti-k3r5.conf
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_r5.config"
diff --git a/meta-beagle/conf/machine/beagleplay.conf 
b/meta-beagle/conf/machine/beagleplay.conf
new file mode 100644
index ..1977b4c1
--- /dev/null
+++ b/meta-beagle/conf/machine/beagleplay.conf
@@ -0,0 +1,45 @@
+#@TYPE: Machine
+#@NAME: BeaglePlay (A53)
+#@DESCRIPTION: Machine configuration for the BeaglePlay board (A53 core)
+
+require conf/machine/beagleplay-ti.conf
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_a53.config"
+
+KERNEL_DEVICETREE:append:bsp-bb_org = " \
+ti/k3-am625-beagleplay-csi2-ov5640.dtbo \
+ti/k3-am625-beagleplay-csi2-tevi-ov5640.dtbo \
+ti/k3-am625-beagleplay-lincolntech-lcd185-panel.dtbo \
+ti/k3-am625-beaglemod.dtb \
+ti/k3-am625-beaglemod-audio.dtbo \
+ti/k3-am625-beaglemod-can0.dtbo \
+ti/k3-am625-beaglemod-can1.dtbo \
+ti/k3-am625-beaglemod-csi0-ov5640.dtbo \
+ti/k3-am625-beaglemod-eeprom.dtbo \
+ti/k3-am625-beaglemod-eth.dtbo \
+ti/k3-am625-beaglemod-hdmi.dtbo \
+ti/k3-am625-beaglemod-io-expand.dtbo \
+ti/k3-am625-beaglemod-lt-lcd185.dtbo \
+ti/k3-am625-beaglemod-ospi-flash.dtbo \
+ti/k3-am625-beaglemod-rs485-1.dtbo \
+ti/k3-am625-beaglemod-rs485-2.dtbo \
+ti/k3-am625-beaglemod-rtc.dtbo \
+ti/k3-am625-beaglemod-wl1835.dtbo \
+ti/k3-am625-sk-dmtimer-pwm.dtbo \
+ti/k3-am625-sk-ecap-capture.dtbo \
+ti/k3-am625-sk-lincolntech-lcd185-panel.dtbo \
+ti/k3-am625-sk-mcspi-loopback.dtbo \
+ti/k3-am625-sk-microtips-mf101hie-panel.dtbo \
+ti/k3-am625-sk-microtips-mf103hie-lcd2.dtbo \
+ti/k3-am625-sk-pwm.dtbo \
+ti/k3-am625-sk-rpi-hdr-ehrpwm.dtbo \
+ti/k3-am62x-sk-csi2-imx219.dtbo \
+ti/k3-am62x-sk-csi2-ov5640.dtbo \
+ti/k3-am62x-sk-csi2-tevi-ov5640.dtbo \
+ti/k3-am62x-sk-csi2-v3link-fusion.dtbo \
+ti/k3-am62x-sk-eqep.dtbo \
+ti/k3-am62x-sk-hdmi-disable-fastboot.dtbo \
+ti/k3-am62x-sk-lpm-wkup-sources.dtbo \
+ti/k3-am62x-sk-mcan.dtbo \
+"
diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
index 3844ccfa..c27e0abc 100644
--- a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
+++ b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
@@ -12,6 +12,5 @@ UBOOT_MACHINE = "am62x_evm_r5_defconfig"
 UBOOT_MACHINE:bsp-ti-6_6 = "am62x_beagleplay_r5_defconfig"
 UBOOT_MACHINE:bsp-ti-6_12 = "am62x_beagleplay_r5_defconfig"
 
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_r5.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "am625_beagleplay_r5.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-mainline = "beagleplay_r5.config"
diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
index 3ae10171..68d6dced 100644
--- a/meta-ti-bsp/conf/machine/beagleplay-ti.conf
+++ b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
@@ -24,14 +24,14 @@ UBOOT_MACHINE:bsp-ti-6_6 = "am62x_beagleplay_a53_defconfig"
 UBOOT_MACHINE:bsp-ti-6_12 = "am62x_beagleplay_a53_defconfig"
 
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "am625_beagleplay_a53.config"
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_a53.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-mainline = "beagleplay_a53.config"
 
 SPL_BINARY:bsp-ti-6_6 = "tispl.bin_unsigned"
 SPL_BINARYNAME:bsp-ti-6_6 = "tispl.bin"
 
 KERNEL_DEVICETREE_PREFIX = " \
-ti/k3-am625 \
+ti/k3-am625-beagle \
+ti/k3-am625-sk \
 ti/k3-am62x-sk \
 "
 
@@ -39,58 +39,11 @@ KERNEL_DEVICETREE = " \
 ti/k3-am625-beagleplay-csi2-ov5640.dtbo \
 ti/k3-am625-beagleplay-csi2-tevi-ov5640.dtbo \
 ti/k3-am625-beagleplay.dtb \
-ti/k3-am625-phyboard-lyra-1-4-ghz-opp.dt

Re: [meta-ti] [master][RFC PATCH 2/6] meta-beagle: create a separate layer for Beagle platforms

2024-11-05 Thread Denys Dmytriyenko

On Tue, Nov 05, 2024 at 02:24:40PM -0600, Ryan Eatmon wrote:
> 
> 
> On 11/5/2024 1:10 PM, Denys Dmytriyenko wrote:
> >From: Denys Dmytriyenko 
> >
> >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 
> >---
> >  meta-beagle/conf/layer.conf | 15 +++
> >  1 file changed, 15 insertions(+)
> >  create mode 100644 meta-beagle/conf/layer.conf
> >
> >diff --git a/meta-beagle/conf/layer.conf b/meta-beagle/conf/layer.conf
> >new file mode 100644
> >index ..ca920f29
> >--- /dev/null
> >+++ b/meta-beagle/conf/layer.conf
> >@@ -0,0 +1,15 @@
> >+# We have a conf and classes directory, append to BBPATH
> >+BBPATH .= ":${LAYERDIR}"
> >+
> >+# We have a recipes directory, add to BBFILES
> >+BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
> >+
> >+BBFILE_COLLECTIONS += "meta-beagle"
> >+BBFILE_PATTERN_meta-beagle := "^${LAYERDIR}/"
> >+BBFILE_PRIORITY_meta-beagle = "6"
> >+
> >+LAYERSERIES_COMPAT_meta-beagle = "scarthgap styhead walnascar"
> >+
> >+LAYERDEPENDS_meta-bealge = " \
> 
> misspelling^

Indeed, thanks!


> >+meta-ti-bsp \
> >+"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18048): 
https://lists.yoctoproject.org/g/meta-ti/message/18048
Mute This Topic: https://lists.yoctoproject.org/mt/109412224/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH 4/6] conf/machine: split beagleplay config between meta-ti-bsp and meta-beagle

2024-11-05 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 meta-beagle/conf/machine/beagleplay-k3r5.conf |  8 +++
 meta-beagle/conf/machine/beagleplay.conf  | 45 
 .../conf/machine/beagleplay-ti-k3r5.conf  |  1 -
 meta-ti-bsp/conf/machine/beagleplay-ti.conf   | 51 +--
 4 files changed, 55 insertions(+), 50 deletions(-)
 create mode 100644 meta-beagle/conf/machine/beagleplay-k3r5.conf
 create mode 100644 meta-beagle/conf/machine/beagleplay.conf

diff --git a/meta-beagle/conf/machine/beagleplay-k3r5.conf 
b/meta-beagle/conf/machine/beagleplay-k3r5.conf
new file mode 100644
index ..1423aa10
--- /dev/null
+++ b/meta-beagle/conf/machine/beagleplay-k3r5.conf
@@ -0,0 +1,8 @@
+#@TYPE: Machine
+#@NAME: BeaglePlay (R5F)
+#@DESCRIPTION: Machine configuration for the BeaglePlay (R5F core)
+
+require conf/machine/beagleplay-ti-k3r5.conf
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_r5.config"
diff --git a/meta-beagle/conf/machine/beagleplay.conf 
b/meta-beagle/conf/machine/beagleplay.conf
new file mode 100644
index ..1977b4c1
--- /dev/null
+++ b/meta-beagle/conf/machine/beagleplay.conf
@@ -0,0 +1,45 @@
+#@TYPE: Machine
+#@NAME: BeaglePlay (A53)
+#@DESCRIPTION: Machine configuration for the BeaglePlay board (A53 core)
+
+require conf/machine/beagleplay-ti.conf
+require conf/machine/include/beagle-bsp.inc
+
+UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_a53.config"
+
+KERNEL_DEVICETREE:append:bsp-bb_org = " \
+ti/k3-am625-beagleplay-csi2-ov5640.dtbo \
+ti/k3-am625-beagleplay-csi2-tevi-ov5640.dtbo \
+ti/k3-am625-beagleplay-lincolntech-lcd185-panel.dtbo \
+ti/k3-am625-beaglemod.dtb \
+ti/k3-am625-beaglemod-audio.dtbo \
+ti/k3-am625-beaglemod-can0.dtbo \
+ti/k3-am625-beaglemod-can1.dtbo \
+ti/k3-am625-beaglemod-csi0-ov5640.dtbo \
+ti/k3-am625-beaglemod-eeprom.dtbo \
+ti/k3-am625-beaglemod-eth.dtbo \
+ti/k3-am625-beaglemod-hdmi.dtbo \
+ti/k3-am625-beaglemod-io-expand.dtbo \
+ti/k3-am625-beaglemod-lt-lcd185.dtbo \
+ti/k3-am625-beaglemod-ospi-flash.dtbo \
+ti/k3-am625-beaglemod-rs485-1.dtbo \
+ti/k3-am625-beaglemod-rs485-2.dtbo \
+ti/k3-am625-beaglemod-rtc.dtbo \
+ti/k3-am625-beaglemod-wl1835.dtbo \
+ti/k3-am625-sk-dmtimer-pwm.dtbo \
+ti/k3-am625-sk-ecap-capture.dtbo \
+ti/k3-am625-sk-lincolntech-lcd185-panel.dtbo \
+ti/k3-am625-sk-mcspi-loopback.dtbo \
+ti/k3-am625-sk-microtips-mf101hie-panel.dtbo \
+ti/k3-am625-sk-microtips-mf103hie-lcd2.dtbo \
+ti/k3-am625-sk-pwm.dtbo \
+ti/k3-am625-sk-rpi-hdr-ehrpwm.dtbo \
+ti/k3-am62x-sk-csi2-imx219.dtbo \
+ti/k3-am62x-sk-csi2-ov5640.dtbo \
+ti/k3-am62x-sk-csi2-tevi-ov5640.dtbo \
+ti/k3-am62x-sk-csi2-v3link-fusion.dtbo \
+ti/k3-am62x-sk-eqep.dtbo \
+ti/k3-am62x-sk-hdmi-disable-fastboot.dtbo \
+ti/k3-am62x-sk-lpm-wkup-sources.dtbo \
+ti/k3-am62x-sk-mcan.dtbo \
+"
diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
index 3844ccfa..c27e0abc 100644
--- a/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
+++ b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
@@ -12,6 +12,5 @@ UBOOT_MACHINE = "am62x_evm_r5_defconfig"
 UBOOT_MACHINE:bsp-ti-6_6 = "am62x_beagleplay_r5_defconfig"
 UBOOT_MACHINE:bsp-ti-6_12 = "am62x_beagleplay_r5_defconfig"
 
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_r5.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "am625_beagleplay_r5.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-mainline = "beagleplay_r5.config"
diff --git a/meta-ti-bsp/conf/machine/beagleplay-ti.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
index 3ae10171..68d6dced 100644
--- a/meta-ti-bsp/conf/machine/beagleplay-ti.conf
+++ b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
@@ -24,14 +24,14 @@ UBOOT_MACHINE:bsp-ti-6_6 = "am62x_beagleplay_a53_defconfig"
 UBOOT_MACHINE:bsp-ti-6_12 = "am62x_beagleplay_a53_defconfig"
 
 UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 = "am625_beagleplay_a53.config"
-UBOOT_CONFIG_FRAGMENTS:bsp-bb_org = "am625_beagleplay_a53.config"
 UBOOT_CONFIG_FRAGMENTS:bsp-mainline = "beagleplay_a53.config"
 
 SPL_BINARY:bsp-ti-6_6 = "tispl.bin_unsigned"
 SPL_BINARYNAME:bsp-ti-6_6 = "tispl.bin"
 
 KERNEL_DEVICETREE_PREFIX = " \
-ti/k3-am625 \
+ti/k3-am625-beagle \
+ti/k3-am625-sk \
 ti/k3-am62x-sk \
 "
 
@@ -39,58 +39,11 @@ KERNEL_DEVICETREE = " \
 ti/k3-am625-beagleplay-csi2-ov5640.dtbo \
 ti/k3-am625-beagleplay-csi2-tevi-ov5640.dtbo \
 ti/k3-am625-beagleplay.dtb \
-ti/k3-am625-phyboard-lyra-1-4-ghz-opp.dt

[meta-ti] [master][RFC PATCH 5/6] conf/machine: move remaining Beagle platforms to meta-beagle

2024-11-05 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Include beagle-bsp.inc to define "bb_org" BSP settings and select that
as a default.

Signed-off-by: Denys Dmytriyenko 
---
 {meta-ti-bsp => meta-beagle}/conf/machine/beagle-x15.conf  | 3 +--
 .../conf/machine/beaglebone-ai64-k3r5.conf | 3 +--
 {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64.conf | 3 +--
 {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone.conf  | 3 +--
 4 files changed, 4 insertions(+), 8 deletions(-)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beagle-x15.conf (94%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64-k3r5.conf 
(94%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone-ai64.conf (96%)
 rename {meta-ti-bsp => meta-beagle}/conf/machine/beaglebone.conf (95%)

diff --git a/meta-ti-bsp/conf/machine/beagle-x15.conf 
b/meta-beagle/conf/machine/beagle-x15.conf
similarity index 94%
rename from meta-ti-bsp/conf/machine/beagle-x15.conf
rename to meta-beagle/conf/machine/beagle-x15.conf
index 6f8c435b..e9ab5d40 100644
--- a/meta-ti-bsp/conf/machine/beagle-x15.conf
+++ b/meta-beagle/conf/machine/beagle-x15.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBoard X15
 #@DESCRIPTION: Machine configuration for the BeagleBoard X15
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/am57xx.inc
+require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PREFIX:bsp-ti-6_1 = ""
diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf 
b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
similarity index 94%
rename from meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
rename to meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
index d415a212..95d3abc0 100644
--- a/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64-k3r5.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone AI-64 (R5F)
 #@DESCRIPTION: Machine configuration for the BeagleBone AI-64 (R5F core)
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/k3r5.inc
+require conf/machine/include/beagle-bsp.inc
 
 SYSFW_SOC = "j721e"
 SYSFW_CONFIG = "evm"
diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf 
b/meta-beagle/conf/machine/beaglebone-ai64.conf
similarity index 96%
rename from meta-ti-bsp/conf/machine/beaglebone-ai64.conf
rename to meta-beagle/conf/machine/beaglebone-ai64.conf
index 56e1ed4e..faffd0bb 100644
--- a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf
+++ b/meta-beagle/conf/machine/beaglebone-ai64.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone AI-64 (A72)
 #@DESCRIPTION: Machine configuration for the BeagleBone AI-64 board (A72 core)
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/j721e.inc
+require conf/machine/include/beagle-bsp.inc
 
 IMAGE_SR1_1_HS_FS_FILES:bsp-bb_org = ""
 IMAGE_SR2_HS_SE_FILES:bsp-bb_org = ""
diff --git a/meta-ti-bsp/conf/machine/beaglebone.conf 
b/meta-beagle/conf/machine/beaglebone.conf
similarity index 95%
rename from meta-ti-bsp/conf/machine/beaglebone.conf
rename to meta-beagle/conf/machine/beaglebone.conf
index 0db4d304..6048383b 100644
--- a/meta-ti-bsp/conf/machine/beaglebone.conf
+++ b/meta-beagle/conf/machine/beaglebone.conf
@@ -2,9 +2,8 @@
 #@NAME: BeagleBone machine
 #@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board
 
-TI_PREFERRED_BSP ?= "bb_org"
-
 require conf/machine/include/ti33x.inc
+require conf/machine/include/beagle-bsp.inc
 
 DT_VENDOR_PREFIX = "ti/omap/"
 DT_VENDOR_PREFIX:bsp-ti-6_1 = ""
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18043): 
https://lists.yoctoproject.org/g/meta-ti/message/18043
Mute This Topic: https://lists.yoctoproject.org/mt/109412226/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH 2/6] meta-beagle: create a separate layer for Beagle platforms

2024-11-05 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 meta-beagle/conf/layer.conf | 15 +++
 1 file changed, 15 insertions(+)
 create mode 100644 meta-beagle/conf/layer.conf

diff --git a/meta-beagle/conf/layer.conf b/meta-beagle/conf/layer.conf
new file mode 100644
index ..ca920f29
--- /dev/null
+++ b/meta-beagle/conf/layer.conf
@@ -0,0 +1,15 @@
+# We have a conf and classes directory, append to BBPATH
+BBPATH .= ":${LAYERDIR}"
+
+# We have a recipes directory, add to BBFILES
+BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "meta-beagle"
+BBFILE_PATTERN_meta-beagle := "^${LAYERDIR}/"
+BBFILE_PRIORITY_meta-beagle = "6"
+
+LAYERSERIES_COMPAT_meta-beagle = "scarthgap styhead walnascar"
+
+LAYERDEPENDS_meta-bealge = " \
+meta-ti-bsp \
+"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18041): 
https://lists.yoctoproject.org/g/meta-ti/message/18041
Mute This Topic: https://lists.yoctoproject.org/mt/109412224/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH 6/6] u-boot-bb_org, linux-bb_org: move "bb_org" providers to meta-beagle

2024-11-05 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 .../recipes-bsp/u-boot/u-boot-bb.org_git.bb | 2 +-
 .../0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch | 0
 ...1-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch | 0
 .../recipes-kernel/linux/linux-bb.org/defconfig | 0
 .../recipes-kernel/linux/linux-bb.org_git.bb| 0
 5 files changed, 1 insertion(+), 1 deletion(-)
 rename {meta-ti-bsp => meta-beagle}/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
(92%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 (100%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 (100%)
 rename {meta-ti-bsp => 
meta-beagle}/recipes-kernel/linux/linux-bb.org/defconfig (100%)
 rename {meta-ti-bsp => meta-beagle}/recipes-kernel/linux/linux-bb.org_git.bb 
(100%)

diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb 
b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
similarity index 92%
rename from meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
rename to meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
index 13286564..0b23effc 100644
--- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
+++ b/meta-beagle/recipes-bsp/u-boot/u-boot-bb.org_git.bb
@@ -1,4 +1,4 @@
-require u-boot-ti.inc
+require recipes-bsp/u-boot/u-boot-ti.inc
 
 SUMMARY = "BeagleBoard.org U-Boot"
 
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
similarity index 100%
rename from 
meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
rename to 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-blk-iocost-avoid-64-bit-division-in-ioc_timer_fn.patch
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
similarity index 100%
rename from 
meta-ti-bsp/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
rename to 
meta-beagle/recipes-kernel/linux/linux-bb.org/0001-block-blk-iocost-gcc13-keep-large-values-in-a-new-en.patch
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org/defconfig 
b/meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
similarity index 100%
rename from meta-ti-bsp/recipes-kernel/linux/linux-bb.org/defconfig
rename to meta-beagle/recipes-kernel/linux/linux-bb.org/defconfig
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb 
b/meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
similarity index 100%
rename from meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb
rename to meta-beagle/recipes-kernel/linux/linux-bb.org_git.bb
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18046): 
https://lists.yoctoproject.org/g/meta-ti/message/18046
Mute This Topic: https://lists.yoctoproject.org/mt/109412229/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH 3/6] conf/machine: move "bb_org" BSP settings to meta-beagle

2024-11-05 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Define "bb_org" default BSP settings in meta-beagle layer that all Beagle
platforms will use.

Signed-off-by: Denys Dmytriyenko 
---
 .../conf/machine/include/beagle-bsp.inc   | 24 +++
 meta-ti-bsp/conf/machine/include/ti-bsp.inc   | 21 +---
 2 files changed, 25 insertions(+), 20 deletions(-)
 create mode 100644 meta-beagle/conf/machine/include/beagle-bsp.inc

diff --git a/meta-beagle/conf/machine/include/beagle-bsp.inc 
b/meta-beagle/conf/machine/include/beagle-bsp.inc
new file mode 100644
index ..77d0b483
--- /dev/null
+++ b/meta-beagle/conf/machine/include/beagle-bsp.inc
@@ -0,0 +1,24 @@
+# Use meta-ti-bsp "multi-BSP" facility to create a custom "bb_org" BSP profile
+# with default preferences for Beagle platforms
+
+# Default is bb_org, but can override with any of the existing options
+TI_PREFERRED_BSP ?= "bb_org"
+
+# ==
+# bb_org
+# BeagleBoard.org kernel 6.1, u-boot 2023.04
+# based on TI staging trees with extra Beagle-specific features
+# but may not be up-to-date with TI version
+# ==
+BSP_KERNEL_PROVIDER:bsp-bb_org = "linux-bb.org"
+BSP_KERNEL_VERSION:bsp-bb_org = "%"
+BSP_BOOTLOADER_PROVIDER:bsp-bb_org = "u-boot-bb.org"
+BSP_BOOTLOADER_VERSION:bsp-bb_org = "%"
+
+BSP_SGX_DRIVER_PROVIDER:bsp-bb_org = "ti-sgx-ddk-km"
+BSP_SGX_DRIVER_VERSION:bsp-bb_org = "1.17%"
+BSP_SGX_UMLIBS_VERSION:bsp-bb_org = "1.17%"
+BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org = "ti-img-rogue-driver"
+BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
+BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
+BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
index d27bbe3c..fcb7e2bc 100644
--- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
+++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
@@ -3,7 +3,7 @@
 # preferences for kernel, bootloader and graphics components, as
 # well as a dedicated machine override.
 
-# Supported options are: mainline, next, ti-6_6, ti-6_1, bb_org
+# Supported options are: mainline, next, ti-6_12, ti-6_6, ti-6_1
 TI_PREFERRED_BSP ??= "ti-6_6"
 
 # Use bsp-* namespace for overrides
@@ -80,25 +80,6 @@ BSP_ROGUE_DRIVER_VERSION:bsp-ti-6_1 = "23%"
 BSP_ROGUE_UMLIBS_VERSION:bsp-ti-6_1 = "23%"
 BSP_MESA_PVR_VERSION:bsp-ti-6_1 = "22%"
 
-# ==
-# bb_org
-# BeagleBoard.org kernel 6.1, u-boot 2023.04
-# based on TI staging trees with extra Beagle-specific features
-# but may not be up-to-date with TI version
-# ==
-BSP_KERNEL_PROVIDER:bsp-bb_org = "linux-bb.org"
-BSP_KERNEL_VERSION:bsp-bb_org = "%"
-BSP_BOOTLOADER_PROVIDER:bsp-bb_org = "u-boot-bb.org"
-BSP_BOOTLOADER_VERSION:bsp-bb_org = "%"
-
-BSP_SGX_DRIVER_PROVIDER:bsp-bb_org = "ti-sgx-ddk-km"
-BSP_SGX_DRIVER_VERSION:bsp-bb_org = "1.17%"
-BSP_SGX_UMLIBS_VERSION:bsp-bb_org = "1.17%"
-BSP_ROGUE_DRIVER_PROVIDER:bsp-bb_org = "ti-img-rogue-driver"
-BSP_ROGUE_DRIVER_VERSION:bsp-bb_org = "23%"
-BSP_ROGUE_UMLIBS_VERSION:bsp-bb_org = "23%"
-BSP_MESA_PVR_VERSION:bsp-bb_org = "22%"
-
 # ==
 # sane fallback defaults
 # if specific values are not defined or bsp is set incorrectly
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18042): 
https://lists.yoctoproject.org/g/meta-ti/message/18042
Mute This Topic: https://lists.yoctoproject.org/mt/109412225/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH 1/6] conf/machine: rename beagleplay machine to beagleplay-ti

2024-11-05 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

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 
---
 .../machine/{beagleplay-k3r5.conf => beagleplay-ti-k3r5.conf} | 0
 meta-ti-bsp/conf/machine/{beagleplay.conf => beagleplay-ti.conf}  | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename meta-ti-bsp/conf/machine/{beagleplay-k3r5.conf => 
beagleplay-ti-k3r5.conf} (100%)
 rename meta-ti-bsp/conf/machine/{beagleplay.conf => beagleplay-ti.conf} (100%)

diff --git a/meta-ti-bsp/conf/machine/beagleplay-k3r5.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beagleplay-k3r5.conf
rename to meta-ti-bsp/conf/machine/beagleplay-ti-k3r5.conf
diff --git a/meta-ti-bsp/conf/machine/beagleplay.conf 
b/meta-ti-bsp/conf/machine/beagleplay-ti.conf
similarity index 100%
rename from meta-ti-bsp/conf/machine/beagleplay.conf
rename to meta-ti-bsp/conf/machine/beagleplay-ti.conf
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18045): 
https://lists.yoctoproject.org/g/meta-ti/message/18045
Mute This Topic: https://lists.yoctoproject.org/mt/109412228/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH] ti-bsp: Tighten up versions for PREFERRED_VERSION

2024-11-01 Thread Denys Dmytriyenko

On Thu, Oct 31, 2024 at 03:49:55PM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> 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.

While this is Ok for stable versions in general, which have 6.1.y versioning, 
the first release in the series has implied ".0" and when Linus released it, 
it was versioned as 6.1 (not 6.1.0) until Greg made the first stable release 
as 6.1.1. Just something to keep in mind... I see you haven't changed 6.12% 
matching, so it should be fine even for the first release, when it's out.


> Signed-off-by: Ryan Eatmon 
> ---
>  meta-ti-bsp/conf/machine/include/ti-bsp.inc | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
> b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> index 2eb3bd19..d27bbe3c 100644
> --- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> +++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> @@ -53,7 +53,7 @@ MACHINE_FEATURES:remove:bsp-ti-6_12 = "gpu"
>  # TI staging kernel 6.6, u-boot 2024.04
>  # ==
>  BSP_KERNEL_PROVIDER:bsp-ti-6_6 = "linux-ti-staging"
> -BSP_KERNEL_VERSION:bsp-ti-6_6 = "6.6%"
> +BSP_KERNEL_VERSION:bsp-ti-6_6 = "6.6.%"
>  BSP_BOOTLOADER_PROVIDER:bsp-ti-6_6 = "u-boot-ti-staging"
>  BSP_BOOTLOADER_VERSION:bsp-ti-6_6 = "2024.04%"
>  
> @@ -68,9 +68,9 @@ BSP_MESA_PVR_VERSION:bsp-ti-6_6 = "23%"
>  # TI staging kernel 6.1, u-boot 2023.04
>  # ==
>  BSP_KERNEL_PROVIDER:bsp-ti-6_1 = "linux-ti-staging"
> -BSP_KERNEL_VERSION:bsp-ti-6_1 = "6.1%"
> +BSP_KERNEL_VERSION:bsp-ti-6_1 = "6.1.%"
>  BSP_BOOTLOADER_PROVIDER:bsp-ti-6_1 = "u-boot-ti-staging"
> -BSP_BOOTLOADER_VERSION:bsp-ti-6_1 = "2023%"
> +BSP_BOOTLOADER_VERSION:bsp-ti-6_1 = "2023.04%"
>  
>  BSP_SGX_DRIVER_PROVIDER:bsp-ti-6_1 = "ti-sgx-ddk-km"
>  BSP_SGX_DRIVER_VERSION:bsp-ti-6_1 = "1.17%"
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18033): 
https://lists.yoctoproject.org/g/meta-ti/message/18033
Mute This Topic: https://lists.yoctoproject.org/mt/109322287/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][scarthgap/master][PATCH] sgx: bump version for kernel 6.6 / mesa 23.2.1

2024-11-01 Thread Denys Dmytriyenko

On Thu, Oct 31, 2024 at 06:47:43PM -0500, r...@ti.com wrote:
> From: Randolph Sapp 
> 
> 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 right now (23.2.1).
> These commits are currently compatible with both kernel 6.1 and 6.6.
> 
> Enable SGX by default in the 6.6 BSP provider section logic.

Great to finally get "legacy" SGX working on 6.6! Thanks for doing it.


> Signed-off-by: Randolph Sapp 
> ---
>  meta-ti-bsp/conf/machine/include/ti-bsp.inc   | 4 +++-
>  .../recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb | 2 +-
>  meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb  | 2 +-
>  3 files changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
> b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> index 0c8f657d..d06fed1e 100644
> --- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> +++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> @@ -57,7 +57,9 @@ BSP_KERNEL_VERSION:bsp-ti-6_6 = "6.6%"
>  BSP_BOOTLOADER_PROVIDER:bsp-ti-6_6 = "u-boot-ti-staging"
>  BSP_BOOTLOADER_VERSION:bsp-ti-6_6 = "2024.04%"
>  
> -# Only Rogue is enabled so far, SGX falls back to SW rendering
> +BSP_SGX_DRIVER_PROVIDER:bsp-ti-6_6 = "ti-sgx-ddk-km"
> +BSP_SGX_DRIVER_VERSION:bsp-ti-6_6 = "1.17%"
> +BSP_SGX_UMLIBS_VERSION:bsp-ti-6_6 = "1.17%"
>  BSP_ROGUE_DRIVER_PROVIDER:bsp-ti-6_6 = "ti-img-rogue-driver"
>  BSP_ROGUE_DRIVER_VERSION:bsp-ti-6_6 = "24%"
>  BSP_ROGUE_UMLIBS_VERSION:bsp-ti-6_6 = "24%"
> diff --git 
> a/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb 
> b/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb
> index 100c10c1..31cffaf1 100644
> --- a/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb
> +++ b/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb
> @@ -19,7 +19,7 @@ SRC_URI = 
> "git://git.ti.com/git/graphics/omap5-sgx-ddk-linux.git;protocol=https;
>  
>  S = "${WORKDIR}/git"
>  
> -SRCREV = "652ae16657cc4acda664e669d0c9b4891252f37f"
> +SRCREV = "97c49d302efd50d1e52bf55a25fe8ecf3e5476c3"
>  
>  TARGET_PRODUCT:omap-a15 = "ti572x_linux"
>  TARGET_PRODUCT:ti33x = "ti335x_linux"
> diff --git a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb 
> b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb
> index 21134bc7..fa765a64 100644
> --- a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb
> +++ b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb
> @@ -25,7 +25,7 @@ PACKAGECONFIG:append = " \
>  ${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver', 
> 'ti-sgx-ddk-km', 'sgx', '', d)} \
>  "
>  
> -SRCREV = "b12290126ba6a154f0e8b0a8c8b2b0d64f98e427"
> +SRCREV = "0e75e7ded360ea6aee4140393b30960e152f3994"
>  PV = "23.2.1"
>  
>  PVR_DISPLAY_CONTROLLER_ALIAS ??= "tidss"
> -- 
> 2.47.0
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18032): 
https://lists.yoctoproject.org/g/meta-ti/message/18032
Mute This Topic: https://lists.yoctoproject.org/mt/109324913/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH] linux: Rework the reproducibility patches

2024-10-17 Thread Denys Dmytriyenko

I don't think you need bsp-overrides anymore...


On Thu, Oct 17, 2024 at 02:08:25PM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> It was suggested to move the reproducibility patches out of
> ti-kernel.inc and into the respective recipes.  Take this time to also
> rename the variable being added to the SRC_URI to
> REPRODUCIBILITY_PATCHES to make it clearer about what the patches are
> that it lists.
> 
> This change will also make it easier for the upstream testing flow to
> update the mainline recipe to the new version and update the needed
> patches at the same time.
> 
> Signed-off-by: Ryan Eatmon 
> ---
>  .../linux/linux-ti-mainline_git.bb |  4 
>  .../linux/linux-ti-staging_6.12.bb |  4 
>  .../linux/linux-ti-staging_6.6.bb  |  4 
>  meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc | 18 ++
>  4 files changed, 14 insertions(+), 16 deletions(-)
> 
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb
> index a9048f16..bd06cc2b 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb
> @@ -19,6 +19,10 @@ PV = "6.11"
>  
>  SRC_URI = 
> "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git;protocol=https;branch=master"
>  
> +REPRODUCIBILITY_PATCHES:bsp-mainline = " \
> +file://0001-drivers-gpu-drm-msm-registers-improve-reproducibilit.patch \
> +"
> +
>  DEFCONFIG_NAME = "multi_v7_defconfig"
>  DEFCONFIG_NAME:omapl138 = "davinci_all_defconfig"
>  DEFCONFIG_NAME:k3 = "defconfig"
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.12.bb 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.12.bb
> index f6f8732b..591eb5e3 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.12.bb
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.12.bb
> @@ -33,6 +33,10 @@ KERNEL_GIT_PROTOCOL = "https"
>  SRC_URI += 
> "${KERNEL_GIT_URI};protocol=${KERNEL_GIT_PROTOCOL};branch=${BRANCH} \
>  file://defconfig"
>  
> +REPRODUCIBILITY_PATCHES:bsp-ti-6_12 = " \
> +file://0001-drivers-gpu-drm-msm-registers-improve-reproducibilit.patch \
> +"
> +
>  # Special configuration for remoteproc/rpmsg IPC modules
>  module_conf_rpmsg_client_sample = "blacklist rpmsg_client_sample"
>  module_conf_ti_k3_r5_remoteproc = "softdep ti_k3_r5_remoteproc pre: 
> virtio_rpmsg_bus"
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.6.bb 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.6.bb
> index 9a906a0f..baf5f9f1 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.6.bb
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.6.bb
> @@ -31,6 +31,10 @@ KERNEL_GIT_PROTOCOL = "https"
>  SRC_URI += 
> "${KERNEL_GIT_URI};protocol=${KERNEL_GIT_PROTOCOL};branch=${BRANCH} \
>  file://defconfig"
>  
> +REPRODUCIBILITY_PATCHES:bsp-ti-6_6 = " \
> +file://0001-vt-conmakehash-improve-reproducibility.patch \
> +"
> +
>  # Special configuration for remoteproc/rpmsg IPC modules
>  module_conf_rpmsg_client_sample = "blacklist rpmsg_client_sample"
>  module_conf_ti_k3_r5_remoteproc = "softdep ti_k3_r5_remoteproc pre: 
> virtio_rpmsg_bus"
> diff --git a/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc 
> b/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc
> index 09cfdb12..e51b14d7 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc
> +++ b/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc
> @@ -13,19 +13,5 @@ EXTRA_DTC_ARGS += "${@get_extra_dtc_args(d)}"
>  KERNEL_DTBDEST = "${KERNEL_IMAGEDEST}/dtb"
>  KERNEL_DTBVENDORED = "1"
>  
> -KERNEL_PATCHES = ""
> -
> -KERNEL_PATCHES:bsp-mainline = " \
> -file://0001-vt-conmakehash-improve-reproducibility-for-v6.10.patch \
> -file://0001-drivers-gpu-drm-msm-registers-improve-reproducibilit.patch \
> -"
> -
> -KERNEL_PATCHES:bsp-ti-6_12 = " \
> -file://0001-drivers-gpu-drm-msm-registers-improve-reproducibilit.patch \
> -"
> -
> -KERNEL_PATCHES:bsp-ti-6_6 = " \
> -file://0001-vt-conmakehash-improve-reproducibility.patch \
> -"
> -
> -SRC_URI:append = " ${KERNEL_PATCHES} "
> +REPRODUCIBILITY_PATCHES = ""
> +SRC_URI:append = " ${REPRODUCIBILITY_PATCHES}"
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18014): 
https://lists.yoctoproject.org/g/meta-ti/message/18014
Mute This Topic: https://lists.yoctoproject.org/mt/109069924/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [master/scarthgap][PATCH] conf: machine: k3: use weak assignment for FIT image variables

2024-10-17 Thread Denys Dmytriyenko

On Wed, Oct 16, 2024 at 04:35:17PM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> 
> 
> On 10/16/2024 2:51 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
> >
> >
> >On 10/14/2024 3:27 PM, Sergio Prado wrote:
> >>Use weak assignment to make it possible to override the default
> >>value via classes parsed after the machine configuration file.
> >>
> >>This is the case when using the tdxref-signed class from
> >>meta-toradex-security to generated signed images for AM6X.
> >>
> >>Additionally, explicitly set FIT_SIGN_NUMBITS to 4096 to align with the
> >>default rsa4096 algorithm, preventing potential mismatches between the
> >>signing algorithm and key length.
> >>
> >>Signed-off-by: Sergio Prado 
> >>Signed-off-by: Rogerio Borin 
> >>---
> >>  meta-ti-bsp/conf/machine/include/k3.inc | 9 +
> >>  1 file changed, 5 insertions(+), 4 deletions(-)
> >>
> >>diff --git a/meta-ti-bsp/conf/machine/include/k3.inc
> >>b/meta-ti-bsp/conf/machine/include/k3.inc
> >>index a296f64fa141..07f0bcb48bfc 100644
> >>--- a/meta-ti-bsp/conf/machine/include/k3.inc
> >>+++ b/meta-ti-bsp/conf/machine/include/k3.inc
> >>@@ -26,10 +26,11 @@ UBOOT_SUFFIX = "img"
> >>  UBOOT_SIGN_ENABLE = "1"
> >>  UBOOT_MKIMAGE_DTCOPTS = "-I dts -O dtb"
> >>-UBOOT_SIGN_KEYNAME ?= "custMpk"
> >>-UBOOT_SIGN_KEYDIR ?= "${TI_SECURE_DEV_PKG}/keys"
> >>-FIT_HASH_ALG ?= "sha512"
> >>-FIT_SIGN_ALG ?= "rsa4096"
> >>+UBOOT_SIGN_KEYNAME ??= "custMpk"
> >>+UBOOT_SIGN_KEYDIR ??= "${TI_SECURE_DEV_PKG}/keys"
> >>+FIT_HASH_ALG ??= "sha512"
> >>+FIT_SIGN_ALG ??= "rsa4096"
> >>+FIT_SIGN_NUMBITS ??= "4096"
> >
> >These changes appear to break the build flow.  Since the the only
> >real change is the addition of FIT_SIGN_NUMBITS, I'm going to
> >assume that is the culprit.
> >
> >Signature written to 
> >'/build/arago-tmp-default-glibc/work/am62axx_evm-oe-linux/u-boot-ti-staging/2024.04+git/build/fitImage-linux',
> >node
> >'/configurations/conf-ti_k3-v3link-imx219-0-2.dtbo/signature-1'
> >Public key written to 'u-boot.dtb', node '/signature/key-custMpk'
> >Signature check bad (error 1)
> >Verifying Hash Integrity for node 'conf-ti_k3-am62a7-sk.dtb'...
> >sha256,rsa2048:custMpk-
> >  error!
> >Verification failed for '(null)' hash node in
> >'conf-ti_k3-am62a7-sk.dtb' config node
> >Failed to verify required signature 'key-custMpk'
> 
> I think the issue is that the weak assignment happens at the very
> end of parsing if there no other value for the variable.  But the
> various classes (kernel-fitimage.bbclass, uboot-sign.bbclass,
> etc...) set the variables using the ?= so that means the values we
> want for our stuff never gets set correctly.
> 
> I can see how this works for you in your case, but doing this in
> meta-ti-bsp breaks everyone not using meta-tordex-security.
> 
> I'm not really sure the best solution for this.  Should the tordex
> layer be in final control of these variables and not allow
> overrides?  Should it not be using the ?= assignment and instead use
> the = assignment to force the issue?
> 
> Denys,
> Any ideas?

Yeah, I had my suspicions about the patch, so not surprised by your 
confirmation. I'd suggest using machine or SoC overrides in toradex 
layer to change the defaults set in meta-ti k3.inc

-- 
Denys

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18010): 
https://lists.yoctoproject.org/g/meta-ti/message/18010
Mute This Topic: https://lists.yoctoproject.org/mt/109009846/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH] layer.conf: add compatibility with walnascar

2024-10-12 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

The next Yocto Project release is called walnascar and OE-Core master branch
is now marked accordingly. Add layer compatibility with walnascar.

Signed-off-by: Denys Dmytriyenko 
---
 meta-ti-bsp/conf/layer.conf| 2 +-
 meta-ti-extras/conf/layer.conf | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-ti-bsp/conf/layer.conf b/meta-ti-bsp/conf/layer.conf
index e87221f3..1fffb971 100644
--- a/meta-ti-bsp/conf/layer.conf
+++ b/meta-ti-bsp/conf/layer.conf
@@ -9,7 +9,7 @@ BBFILE_COLLECTIONS += "meta-ti-bsp"
 BBFILE_PATTERN_meta-ti-bsp := "^${LAYERDIR}/"
 BBFILE_PRIORITY_meta-ti-bsp = "6"
 
-LAYERSERIES_COMPAT_meta-ti-bsp = "scarthgap styhead"
+LAYERSERIES_COMPAT_meta-ti-bsp = "scarthgap styhead walnascar"
 
 LICENSE_PATH += "${LAYERDIR}/licenses"
 
diff --git a/meta-ti-extras/conf/layer.conf b/meta-ti-extras/conf/layer.conf
index a8c68343..5c493daa 100644
--- a/meta-ti-extras/conf/layer.conf
+++ b/meta-ti-extras/conf/layer.conf
@@ -9,7 +9,7 @@ BBFILE_COLLECTIONS += "meta-ti-extras"
 BBFILE_PATTERN_meta-ti-extras := "^${LAYERDIR}/"
 BBFILE_PRIORITY_meta-ti-extras = "6"
 
-LAYERSERIES_COMPAT_meta-ti-extras = "scarthgap styhead"
+LAYERSERIES_COMPAT_meta-ti-extras = "scarthgap styhead walnascar"
 
 LICENSE_PATH += "${LAYERDIR}/licenses"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18005): 
https://lists.yoctoproject.org/g/meta-ti/message/18005
Mute This Topic: https://lists.yoctoproject.org/mt/108973477/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [PATCH] layer.conf: add compatibility with walnascar

2024-10-12 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

The next Yocto Project release is called walnascar and OE-Core master branch
is now marked accordingly. Add layer compatibility with walnascar.

Signed-off-by: Denys Dmytriyenko 
---
 meta-ti-bsp/conf/layer.conf| 2 +-
 meta-ti-extras/conf/layer.conf | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-ti-bsp/conf/layer.conf b/meta-ti-bsp/conf/layer.conf
index e87221f3..1fffb971 100644
--- a/meta-ti-bsp/conf/layer.conf
+++ b/meta-ti-bsp/conf/layer.conf
@@ -9,7 +9,7 @@ BBFILE_COLLECTIONS += "meta-ti-bsp"
 BBFILE_PATTERN_meta-ti-bsp := "^${LAYERDIR}/"
 BBFILE_PRIORITY_meta-ti-bsp = "6"
 
-LAYERSERIES_COMPAT_meta-ti-bsp = "scarthgap styhead"
+LAYERSERIES_COMPAT_meta-ti-bsp = "scarthgap styhead walnascar"
 
 LICENSE_PATH += "${LAYERDIR}/licenses"
 
diff --git a/meta-ti-extras/conf/layer.conf b/meta-ti-extras/conf/layer.conf
index a8c68343..5c493daa 100644
--- a/meta-ti-extras/conf/layer.conf
+++ b/meta-ti-extras/conf/layer.conf
@@ -9,7 +9,7 @@ BBFILE_COLLECTIONS += "meta-ti-extras"
 BBFILE_PATTERN_meta-ti-extras := "^${LAYERDIR}/"
 BBFILE_PRIORITY_meta-ti-extras = "6"
 
-LAYERSERIES_COMPAT_meta-ti-extras = "scarthgap styhead"
+LAYERSERIES_COMPAT_meta-ti-extras = "scarthgap styhead walnascar"
 
 LICENSE_PATH += "${LAYERDIR}/licenses"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18004): 
https://lists.yoctoproject.org/g/meta-ti/message/18004
Mute This Topic: https://lists.yoctoproject.org/mt/108973434/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH v3] ti-bsp: Add RT and systest support

2024-10-09 Thread Denys Dmytriyenko

On Wed, Oct 09, 2024 at 08:51:30AM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> 
> I thought of this in the middle of the night and realized it was a
> simpler fix.  Rather than create the extra variable and have to set
> it in all of the BSPs, just add two new PREFERRED_VERSION settings
> with -rt and -system.  The effect is the same, and has the benefit
> of still erroring out if you try to build an RT version of mainline,
> next, or bb_org.

Yeah, this is much cleaner! Looks good.


> On 10/9/2024 8:47 AM, Ryan Eatmon via lists.yoctoproject.org wrote:
> >We were missing controlling the versions for linux-ti-staging-rt and
> >linux-ti-staging-systest using the BSP framework.  Since the
> >PREFERRED_VERSION is not tied to the virtual/kernel we need two
> >additional settings for those alternate kernel package names.
> >
> >For BSPs that do not have the -rt and -systest recipes then the two
> >new variable settings should effectively be ignored and cause no issues.
> >
> >Signed-off-by: Ryan Eatmon 
> >---
> >v3: Typo in commit message.
> >v2: Remove the extra variables and just set PREFERRED_VERSION.
> >
> >  meta-ti-bsp/conf/machine/include/ti-bsp.inc | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> >diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
> >b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> >index 4cb2aab4..0c8f657d 100644
> >--- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> >+++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> >@@ -122,6 +122,8 @@ BSP_MESA_PVR_VERSION ?= ""
> >  # ==
> >  PREFERRED_PROVIDER_virtual/kernel ?= "${BSP_KERNEL_PROVIDER}"
> >  PREFERRED_VERSION_${BSP_KERNEL_PROVIDER} ?= "${BSP_KERNEL_VERSION}"
> >+PREFERRED_VERSION_${BSP_KERNEL_PROVIDER}-rt ?= "${BSP_KERNEL_VERSION}"
> >+PREFERRED_VERSION_${BSP_KERNEL_PROVIDER}-systest ?= "${BSP_KERNEL_VERSION}"
> >  PREFERRED_PROVIDER_virtual/bootloader ?= "${BSP_BOOTLOADER_PROVIDER}"
> >  PREFERRED_PROVIDER_u-boot ?= "${BSP_BOOTLOADER_PROVIDER}"
> >  PREFERRED_VERSION_${BSP_BOOTLOADER_PROVIDER} ?= "${BSP_BOOTLOADER_VERSION}"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18002): 
https://lists.yoctoproject.org/g/meta-ti/message/18002
Mute This Topic: https://lists.yoctoproject.org/mt/108909108/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH 2/4] u-boot-ti-staging: Add v2024.10 recipe

2024-10-08 Thread Denys Dmytriyenko

Same comment with --find-copies-harder, although the recipe itself is quite 
smalle, so the diff could even be larger...


On Fri, Oct 04, 2024 at 10:18:55AM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> Adding needed recipe for initial testing and development of the 2024.10
> version of u-boot for the next LTS.
> 
> Signed-off-by: Ryan Eatmon 
> ---
>  .../recipes-bsp/u-boot/u-boot-ti-staging_2024.10.bb   | 11 +++
>  meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc  |  3 +++
>  2 files changed, 14 insertions(+)
>  create mode 100644 
> meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2024.10.bb
> 
> diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2024.10.bb 
> b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2024.10.bb
> new file mode 100644
> index ..1ab94fcc
> --- /dev/null
> +++ b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2024.10.bb
> @@ -0,0 +1,11 @@
> +require u-boot-ti.inc
> +
> +DEFAULT_PREFERENCE = "-1"
> +
> +include ${@ 'recipes-bsp/u-boot/ti-extras.inc' if d.getVar('TI_EXTRAS') else 
> ''}
> +
> +PR = "r0"
> +
> +BRANCH = "ti-u-boot-2024.10"
> +
> +SRCREV = "c97ada2dc66934ee00a7a03d9ed078bdfb7b4039"
> diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc 
> b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> index e1f1972e..97237d66 100644
> --- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> +++ b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> @@ -26,6 +26,9 @@ SRC_URI = 
> "${UBOOT_GIT_URI};protocol=${UBOOT_GIT_PROTOCOL};branch=${BRANCH}"
>  
>  PV:append = "+git"
>  
> +# u-boot builds a tool mkeficapsule and it needs this
> +DEPENDS += "gnutls-native"

Is this specific to 2024.10? Should it be added in the recipe, not .inc?


> +
>  # u-boot needs devtree compiler to parse dts files
>  DEPENDS += "dtc-native bc-native flex-native bison-native 
> python3-setuptools-native"
>  
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17991): 
https://lists.yoctoproject.org/g/meta-ti/message/17991
Mute This Topic: https://lists.yoctoproject.org/mt/108819038/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH 1/4] linux-ti-staging: Add v6.12 recipe

2024-10-08 Thread Denys Dmytriyenko

This might have been easier to review with --find-copies-harder flag...

And I was wondering if setting KERNEL_PATCHES would be cleaner in the 
corresponding recipes, instead of globally in ti-kernel.inc?


On Fri, Oct 04, 2024 at 10:18:54AM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> Adding needed recipes for initial testing and development of the 6.12
> kernel for the next LTS.
> 
> Signed-off-by: Ryan Eatmon 
> ---
>  .../linux/linux-ti-staging-6.12/defconfig |  2 +
>  .../linux/linux-ti-staging-6.12/k3/defconfig  |  2 +
>  .../linux-ti-staging-6.12/omapl138/defconfig  |  1 +
>  .../linux-ti-staging-6.12/ti33x/defconfig |  2 +
>  .../linux-ti-staging-6.12/ti43x/defconfig |  2 +
>  .../linux/linux-ti-staging-rt-6.12/defconfig  |  2 +
>  .../linux-ti-staging-rt-6.12/k3/defconfig |  2 +
>  .../omapl138/defconfig|  2 +
>  .../linux-ti-staging-rt-6.12/ti33x/defconfig  |  2 +
>  .../linux-ti-staging-rt-6.12/ti43x/defconfig  |  2 +
>  .../linux/linux-ti-staging-rt_6.12.bb |  9 +
>  .../linux-ti-staging-systest-6.12/defconfig   |  2 +
>  .../k3/defconfig  |  2 +
>  .../omapl138/defconfig|  1 +
>  .../linux/linux-ti-staging-systest_6.12.bb|  7 
>  .../linux/linux-ti-staging_6.12.bb| 40 +++
>  .../recipes-kernel/linux/ti-kernel.inc|  4 ++
>  17 files changed, 84 insertions(+)
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/k3/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/omapl138/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/ti33x/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/ti43x/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt-6.12/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt-6.12/k3/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt-6.12/omapl138/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt-6.12/ti33x/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt-6.12/ti43x/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.12.bb
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-systest-6.12/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-systest-6.12/k3/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-systest-6.12/omapl138/defconfig
>  create mode 100644 
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-systest_6.12.bb
>  create mode 100644 meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.12.bb
> 
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/defconfig 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/defconfig
> new file mode 100644
> index ..9d579e41
> --- /dev/null
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/defconfig
> @@ -0,0 +1,2 @@
> +use-kernel-config=multi_v7_defconfig
> +config-fragment=
> diff --git 
> a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/k3/defconfig 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/k3/defconfig
> new file mode 100644
> index ..fd07b34e
> --- /dev/null
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/k3/defconfig
> @@ -0,0 +1,2 @@
> +use-kernel-config=defconfig
> +config-fragment=
> diff --git 
> a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/omapl138/defconfig 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/omapl138/defconfig
> new file mode 100644
> index ..099493af
> --- /dev/null
> +++ 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/omapl138/defconfig
> @@ -0,0 +1 @@
> +use-kernel-config=davinci_all_defconfig
> diff --git 
> a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/ti33x/defconfig 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/ti33x/defconfig
> new file mode 100644
> index ..9d579e41
> --- /dev/null
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/ti33x/defconfig
> @@ -0,0 +1,2 @@
> +use-kernel-config=multi_v7_defconfig
> +config-fragment=
> diff --git 
> a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/ti43x/defconfig 
> b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/ti43x/defconfig
> new file mode 100644
> index ..9d579e41
> --- /dev/null
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-6.12/ti43x/defconfig
> @@ -0,0 +1,2 @@
> +use-kernel-config=multi_v7_defconfig
> +config-fragment=
> diff --git 
> a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt-6.12/defconfig 
> b/meta-ti-bsp/recipes-kernel/linux/li

Re: [meta-ti][master/scarthgap][PATCH 3/4] ti-bsp: Add ti-6_12

2024-10-08 Thread Denys Dmytriyenko

On Fri, Oct 04, 2024 at 10:18:56AM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> Add new BSP for the 6.12 kernel and u-boot 2024.10 versions.
> 
> Signed-off-by: Ryan Eatmon 
> ---
>  meta-ti-bsp/conf/machine/include/ti-bsp.inc | 15 ++-
>  1 file changed, 14 insertions(+), 1 deletion(-)
> 
> diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc 
> b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> index 33611689..9a15e164 100644
> --- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> +++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> @@ -35,6 +35,19 @@ BSP_BOOTLOADER_VERSION:bsp-next = "%"
>  # in next, usually present in TI staging or derivative like BB.org
>  MACHINE_FEATURES:remove:bsp-next = "gpu"
>  
> +# ==
> +# ti-6_12
> +# TI staging kernel 6.12, u-boot 2024.10
> +# ==
> +BSP_KERNEL_PROVIDER:bsp-ti-6_12 = "linux-ti-staging"
> +BSP_KERNEL_VERSION:bsp-ti-6_12 = "6.12%"
> +BSP_BOOTLOADER_PROVIDER:bsp-ti-6_12 = "u-boot-ti-staging"
> +BSP_BOOTLOADER_VERSION:bsp-ti-6_12 = "2024.10%"
> +
> +# GPU support requires out-of-tree SGX and Rogue drivers not available
> +# in 6.12 yet
> +MACHINE_FEATURES:remove:bsp-next = "gpu"

Copy/paste error? bsp-ti_6.12 vs. bsp-next


> +
>  # ==
>  # ti-6_6
>  # TI staging kernel 6.6, u-boot 2024.04
> @@ -42,7 +55,7 @@ MACHINE_FEATURES:remove:bsp-next = "gpu"
>  BSP_KERNEL_PROVIDER:bsp-ti-6_6 = "linux-ti-staging"
>  BSP_KERNEL_VERSION:bsp-ti-6_6 = "6.6%"
>  BSP_BOOTLOADER_PROVIDER:bsp-ti-6_6 = "u-boot-ti-staging"
> -BSP_BOOTLOADER_VERSION:bsp-ti-6_6 = "2024%"
> +BSP_BOOTLOADER_VERSION:bsp-ti-6_6 = "2024.04%"
>  
>  # Only Rogue is enabled so far, SGX falls back to SW rendering
>  BSP_ROGUE_DRIVER_PROVIDER:bsp-ti-6_6 = "ti-img-rogue-driver"
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17987): 
https://lists.yoctoproject.org/g/meta-ti/message/17987
Mute This Topic: https://lists.yoctoproject.org/mt/108819040/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master][PATCH] optee: Update to v4.3.0

2024-10-08 Thread Denys Dmytriyenko

I was wondering if OPTEE and TFA should also be made BSP-aware. Maybe even 
SYSFW and/or other FWs.

How much backward compatibility is ensured and tested here? Will 4.3.0 version 
here work with BSP 6.1?


On Fri, Oct 04, 2024 at 02:08:25PM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> Update all of the components to the upstream 4.3.0 version.
> 
> Signed-off-by: Ryan Eatmon 
> ---
>  .../recipes-security/optee/optee-client-ti-version.inc| 4 ++--
>  .../recipes-security/optee/optee-examples-ti-version.inc  | 2 +-
>  meta-ti-bsp/recipes-security/optee/optee-os-ti-version.inc| 4 ++--
>  meta-ti-bsp/recipes-security/optee/optee-test-ti-version.inc  | 4 ++--
>  4 files changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-client-ti-version.inc 
> b/meta-ti-bsp/recipes-security/optee/optee-client-ti-version.inc
> index 22a363f4..5f06fa03 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-client-ti-version.inc
> +++ b/meta-ti-bsp/recipes-security/optee/optee-client-ti-version.inc
> @@ -1,2 +1,2 @@
> -PV = "4.2.0+git"
> -SRCREV = "3eac340a781c00ccd61b151b0e9c22a8c6e9f9f0"
> +PV = "4.3.0+git"
> +SRCREV = "a5b1ffcd26e328af0bbf18ab448a38ecd558e05c"
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-examples-ti-version.inc 
> b/meta-ti-bsp/recipes-security/optee/optee-examples-ti-version.inc
> index 2d7a95bd..4d9897a7 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-examples-ti-version.inc
> +++ b/meta-ti-bsp/recipes-security/optee/optee-examples-ti-version.inc
> @@ -1,2 +1,2 @@
> -PV = "4.2.0+git"
> +PV = "4.3.0+git"
>  SRCREV = "378dc0db2d5dd279f58a3b6cb3f78ffd6b165035"
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-os-ti-version.inc 
> b/meta-ti-bsp/recipes-security/optee/optee-os-ti-version.inc
> index 790f5f5f..a79e5702 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-os-ti-version.inc
> +++ b/meta-ti-bsp/recipes-security/optee/optee-os-ti-version.inc
> @@ -1,2 +1,2 @@
> -PV = "4.2.0+git"
> -SRCREV = "12d7c4ee4642d2d761e39fbcf21a06fb77141dea"
> +PV = "4.3.0+git"
> +SRCREV = "1c0d52ace3c237ca6276cafb5c73f699a75c1d40"
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-test-ti-version.inc 
> b/meta-ti-bsp/recipes-security/optee/optee-test-ti-version.inc
> index fdfa420c..0b902d69 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-test-ti-version.inc
> +++ b/meta-ti-bsp/recipes-security/optee/optee-test-ti-version.inc
> @@ -1,2 +1,2 @@
> -PV = "4.2.0+git"
> -SRCREV = "526d5bac1b65f907f67c05cd07beca72fbab88dd"
> +PV = "4.3.0+git"
> +SRCREV = "9d4c4fb9638fb533211037016b6da12fbbcc4bb6"
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17986): 
https://lists.yoctoproject.org/g/meta-ti/message/17986
Mute This Topic: https://lists.yoctoproject.org/mt/108823493/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [PATCH] meta-ti-bsp: ti-dm-fw: declare files installed in 'DEPLOYDIR'

2024-09-28 Thread Denys Dmytriyenko

NAK

This does not make any sense. The subject says DEPLOYDIR, then you add 
INSTALL_DM_FW_DIR (that is ${nonarch_base_libdir}/firmware/${DM_FW_DIR}) 
to FILES, which has nothing to do with do_deploy, only do_install.

Moreover, ti-dm-fw.bb includes ti-linux-fw.inc, which already sets FILES 
to include everything in ${nonarch_base_libdir}/firmware


On Sat, Sep 28, 2024 at 09:09:42PM +0200, Adrian DC wrote:
> Errors: ... is trying to install files into a shared area
> when those files already exist.
> Tests: Build clean, rebuild, rebuild clean with sstate
> ---
> 
> Signed-off-by: Adrian DC 
> ---
>  meta-ti-bsp/recipes-bsp/ti-dm-fw/ti-dm-fw.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta-ti-bsp/recipes-bsp/ti-dm-fw/ti-dm-fw.bb 
> b/meta-ti-bsp/recipes-bsp/ti-dm-fw/ti-dm-fw.bb
> index 1ad236ce..39e0eb8c 100644
> --- a/meta-ti-bsp/recipes-bsp/ti-dm-fw/ti-dm-fw.bb
> +++ b/meta-ti-bsp/recipes-bsp/ti-dm-fw/ti-dm-fw.bb
> @@ -77,6 +77,8 @@ do_deploy() {
>  done
>  }
>  
> +FILES:${PN} += "${INSTALL_DM_FW_DIR}"
> +
>  # Set up names for the firmwares
>  ALTERNATIVE:${PN}:am62xx  = "am62-main-r5f0_0-fw"
>  ALTERNATIVE:${PN}:am62pxx  = "am62p-main-r5f0_0-fw"
> -- 
> 2.43.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17977): 
https://lists.yoctoproject.org/g/meta-ti/message/17977
Mute This Topic: https://lists.yoctoproject.org/mt/108708777/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH v2] trusted-firmware-a: Update to v2.11 release tag

2024-08-28 Thread Denys Dmytriyenko

On Tue, Aug 27, 2024 at 05:14:07PM -0500, Ryan Eatmon wrote:
> 
> 
> On 8/27/2024 5:08 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
> >
> >
> >On 8/27/2024 2:38 PM, Denys Dmytriyenko wrote:
> >>On Fri, Aug 16, 2024 at 01:53:07PM -0500, Ryan Eatmon via
> >>lists.yoctoproject.org wrote:
> >>>From: Kamlesh Gurudasani 
> >>>
> >>>Update to latest release tag, i.e. v2.11.
> >>>
> >>>Also update the LIC_FILES_CHKSUM since the license file changed since
> >>>the last SRCREV change.
> >>
> >>Changed in what way? It is recommended to briefly describe
> >>license changes in
> >>the commit log - it forces one to review the changes to ensure
> >>there are no
> >>license incompatibilities or even in the worst case complete
> >>re-licensing of
> >>the product.
> >
> >The license file for that project is a little goofy.  It has a big
> >overall license, but then breaks out some specific features/blocks
> >of code and lists additional license for those sections.  And
> >that's what they changed.  They added some new items to that list.
> >
> >I thought about pushing back on the project and using the
> >begins/ends concept to selectively extract the main license, but
> >then I thought about it realized that was not a good idea.
> >
> >I'm open to suggestions about how to word a commit to handle this
> >kind of thing in the future.
> >
> >Here is the license file:
> >
> >https://git.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/refs/tags/v2.11/docs/license.rst
> >
> >And here is the change that impacts this patch:
> >
> >https://git.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/584052c7f80b40b9597447eeccef4d6deca4%5E%21/docs/license.rst
> 
> The license file above lists these licenses:
> 
> BSD-3-Clause
>   plus
> _FreeBSD: http://www.freebsd.org
> _Linux MIT license: 
> https://raw.githubusercontent.com/torvalds/linux/master/LICENSES/preferred/MIT
> _SCC: http://www.simple-cc.org/
> _Open Profile for DICE: https://pigweed.googlesource.com/open-dice/
> _Apache License 2.0: https://www.apache.org/licenses/LICENSE-2.0.txt
> 
> 
> 
> But the recipe[1][2] only lists this:
> 
> LICENSE = "BSD-3-Clause & MIT"
> 
> Does that mean the base recipe is also "not compliant" and should be
> updated?
> 
> [1] 
> https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> [2] 
> https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.11.0.bb
> 
> 
> >
> >>In this case the changes were not too bad, but apparently the
> >>list of licenses
> >>did change - see this discussion:
> >>
> >>https://lists.yoctoproject.org/g/meta-arm/topic/106488067#msg6004

Have you looked at our upstream meta-arm discussion I linked here?



> >>>Commit:
> >>>https://git.trustedfirmware.org/TF-A/trusted-firmware-a/+/f2735ebccf5173f74c0458736ec526276106097e
> >>>
> >>>Tag:
> >>>https://git.trustedfirmware.org/TF-A/trusted-firmware-a/+/refs/tags/v2.11
> >>>
> >>>Signed-off-by: Kamlesh Gurudasani 
> >>>Tested-by: Manorit Chawdhry 
> >>>Signed-off-by: Ryan Eatmon 
> >>>---
> >>>  .../recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc | 5 +++--
> >>>  1 file changed, 3 insertions(+), 2 deletions(-)
> >>>
> >>>diff --git 
> >>>a/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc 
> >>>b/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc
> >>>index 291259c0..157bdbc5 100644
> >>>--- a/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc
> >>>+++ b/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc
> >>>@@ -1,5 +1,6 @@
> >>>-PV:k3 = "2.10+git"
> >>>-SRCREV_tfa:k3 = "00f1ec6b8740ccd403e641131e294aabacf2a48b"
> >>>+PV:k3 = "2.11+git"
> >>>+SRCREV_tfa:k3 = "f2735ebccf5173f74c0458736ec526276106097e"
> >>>+LIC_FILES_CHKSUM:k3 =
> >>>"file://docs/license.rst;md5=b5fbfdeb6855162dded31fadcd5d4dc5"
> >>>  SRC_URI:k3 = 
> >>>"git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=https;name=tfa;branch=master"
> >>>  COMPATIBLE_MACHINE:k3 = "k3"
> >>>  TFA_BUILD_TARGET:k3 = "all"
> >>>-- 
> >>>2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17956): 
https://lists.yoctoproject.org/g/meta-ti/message/17956
Mute This Topic: https://lists.yoctoproject.org/mt/107937926/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH v2] trusted-firmware-a: Update to v2.11 release tag

2024-08-27 Thread Denys Dmytriyenko

On Fri, Aug 16, 2024 at 01:53:07PM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> From: Kamlesh Gurudasani 
> 
> Update to latest release tag, i.e. v2.11.
> 
> Also update the LIC_FILES_CHKSUM since the license file changed since
> the last SRCREV change.

Changed in what way? It is recommended to briefly describe license changes in 
the commit log - it forces one to review the changes to ensure there are no 
license incompatibilities or even in the worst case complete re-licensing of 
the product.

In this case the changes were not too bad, but apparently the list of licenses 
did change - see this discussion:

https://lists.yoctoproject.org/g/meta-arm/topic/106488067#msg6004


> Commit:
> https://git.trustedfirmware.org/TF-A/trusted-firmware-a/+/f2735ebccf5173f74c0458736ec526276106097e
> 
> Tag:
> https://git.trustedfirmware.org/TF-A/trusted-firmware-a/+/refs/tags/v2.11
> 
> Signed-off-by: Kamlesh Gurudasani 
> Tested-by: Manorit Chawdhry 
> Signed-off-by: Ryan Eatmon 
> ---
>  .../recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git 
> a/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc 
> b/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc
> index 291259c0..157bdbc5 100644
> --- a/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc
> +++ b/meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-ti.inc
> @@ -1,5 +1,6 @@
> -PV:k3 = "2.10+git"
> -SRCREV_tfa:k3 = "00f1ec6b8740ccd403e641131e294aabacf2a48b"
> +PV:k3 = "2.11+git"
> +SRCREV_tfa:k3 = "f2735ebccf5173f74c0458736ec526276106097e"
> +LIC_FILES_CHKSUM:k3 = 
> "file://docs/license.rst;md5=b5fbfdeb6855162dded31fadcd5d4dc5"
>  SRC_URI:k3 = 
> "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=https;name=tfa;branch=master"
>  COMPATIBLE_MACHINE:k3 = "k3"
>  TFA_BUILD_TARGET:k3 = "all"
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17953): 
https://lists.yoctoproject.org/g/meta-ti/message/17953
Mute This Topic: https://lists.yoctoproject.org/mt/107937926/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][PATCH] mesa-pvr: set pv explicitely

2024-08-27 Thread Denys Dmytriyenko

On Tue, Aug 27, 2024 at 08:57:23AM +0200, Max Krummenacher wrote:
> From: Max Krummenacher 
> 
> openembedded-core commit f5cfb3e23603 ("mesa: set PV from the .inc
> file and not via filenames") now sets PV in the mesa.inc file
> explicitely to whatever version oe-core is using.
> Override that setting to the actual version here to prevent the
> following parse error and whatever else would go wrong afterwards.

I had the same fix I was testing last night, but you beat me to it
submitting it this morning.


> | ERROR: .../mesa-pvr_23.2.1.bb: Unable to get checksum for mesa-pvr SRC_URI 
> entry 0001-meson-Disable-cmake-dependency-detector-for-llvm.patch: file could 
> not be found
> | The following paths were searched:
> | 
> .../meta-ti-bsp/recipes-graphics/mesa/mesa-pvr-24.0.7/bsp-ti-6_1/0001-meson-Disable-cmake-dependency-detector-for-llvm.patch
> | ...
> 
> Signed-off-by: Max Krummenacher 

Tested-by: Denys Dmytriyenko 


> ---
> CC: Randolph Sapp 
>  meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb | 1 +
>  meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb 
> b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb
> index 5abd07934d94..09ae0510ce53 100644
> --- a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb
> +++ b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb
> @@ -29,6 +29,7 @@ PACKAGECONFIG:append = " \
>  "
>  
>  SRCREV = "1be98ba80452ebe38546a7fca26b5a70f2629083"
> +PV = "22.3.5"
>  
>  PVR_DISPLAY_CONTROLLER_ALIAS ??= "tidss"
>  PACKAGECONFIG[pvr] = "-Dgallium-pvr-alias=${PVR_DISPLAY_CONTROLLER_ALIAS},"
> diff --git a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb 
> b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb
> index a137f4521e08..21134bc774cf 100644
> --- a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb
> +++ b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb
> @@ -26,6 +26,7 @@ PACKAGECONFIG:append = " \
>  "
>  
>  SRCREV = "b12290126ba6a154f0e8b0a8c8b2b0d64f98e427"
> +PV = "23.2.1"
>  
>  PVR_DISPLAY_CONTROLLER_ALIAS ??= "tidss"
>  PACKAGECONFIG[pvr] = "-Dgallium-pvr-alias=${PVR_DISPLAY_CONTROLLER_ALIAS},"
> -- 
> 2.42.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17952): 
https://lists.yoctoproject.org/g/meta-ti/message/17952
Mute This Topic: https://lists.yoctoproject.org/mt/108118995/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master/scarthgap][PATCH] openmp-rtos: deprecate

2024-08-26 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Remove openmp-rtos component as deprecated and not maintained.

This used to provide OpenMP DSP runtime components for legacy devices.

Signed-off-by: Denys Dmytriyenko 
---
 .../recipes-ti/openmp-rtos/openmp-rtos_git.bb | 62 ---
 1 file changed, 62 deletions(-)
 delete mode 100644 meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb

diff --git a/meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb 
b/meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb
deleted file mode 100644
index aa4bc6cd..
--- a/meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb
+++ /dev/null
@@ -1,62 +0,0 @@
-DESCRIPTION = "TI OpenMP RTOS"
-HOMEPAGE = "git://git.ti.com/git/openmp/ti-openmp-dsp-runtime.git"
-LICENSE = "BSD-3-Clause"
-
-require recipes-ti/includes/ti-paths.inc
-
-inherit features_check
-
-REQUIRED_MACHINE_FEATURES = "dsp"
-REQUIRED_DISTRO_FEATURES = "openmp"
-
-PV = "2_06_03_00"
-PR = "r0"
-
-OPENMP_RTOS_GIT_URI = "git://git.ti.com/git/openmp/ti-openmp-dsp-runtime.git"
-OPENMP_RTOS_GIT_PROTOCOL = "https"
-OPENMP_RTOS_GIT_BRANCH = "master"
-
-BRANCH = "${OPENMP_RTOS_GIT_BRANCH}"
-SRC_URI = 
"${OPENMP_RTOS_GIT_URI};protocol=${OPENMP_RTOS_GIT_PROTOCOL};branch=${BRANCH}"
-
-SRCREV = "c090eb664d9815a36ead0e14f31e102590680fb8"
-
-LIC_FILES_CHKSUM = 
"file://docs/license/omp_manifest_template.html;md5=61a6972303c0447b7c056195d7ebafee"
-
-DEPENDS = "common-csl-ip-rtos doxygen-native libulm ti-xdctools-native 
ti-ipc-rtos ti-sysbios ti-cgt6x-native zip-native"
-
-COMPATIBLE_MACHINE = "omap-a15"
-PACKAGE_ARCH = "${MACHINE_ARCH}"
-
-S = "${WORKDIR}/git"
-export IPC_DIR = "${IPC_INSTALL_DIR}"
-export XDC_DIR = "${XDC_INSTALL_DIR}"
-export BIOS_DIR = "${SYSBIOS_INSTALL_DIR}"
-export ULM_DIR ="${STAGING_DIR_TARGET}/usr/share/ti/ulm"
-export C6636_PDK_DIR ="${PDK_INSTALL_DIR}"
-export AM572_PDK_DIR ="${PDK_INSTALL_DIR}"
-export XDCCGROOT = "${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x"
-
-export BUILD_AM572 = "0"
-
-BUILD_AM572:omap-a15 = "1"
-
-RELEASE_TARGET = ""
-RELEASE_TARGET:omap-a15 = "am57xx"
-
-do_compile() {
-make -f utils/product/Makefile .zipfile
-}
-
-do_install() {
-install -d ${D}${OMP_INSTALL_DIR_RECIPE}
-cp -r ${S}/exports/openmp_dsp_${RELEASE_TARGET}_*/. -d  
${D}${OMP_INSTALL_DIR_RECIPE}
-}
-
-ALLOW_EMPTY:${PN} = "1"
-
-FILES:${PN}-dev += " \
-${OMP_INSTALL_DIR_RECIPE}/ \
-"
-
-INSANE_SKIP:${PN}-dev = "arch"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17949): 
https://lists.yoctoproject.org/g/meta-ti/message/17949
Mute This Topic: https://lists.yoctoproject.org/mt/108110127/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [master][RFC PATCH] openmp-rtos: deprecate

2024-08-26 Thread Denys Dmytriyenko

On Thu, Aug 08, 2024 at 12:17:45PM -0500, Andrew Davis wrote:
> On 8/4/24 11:36 PM, Denys Dmytriyenko wrote:
> >From: Denys Dmytriyenko 
> >
> >Remove openmp-rtos component as deprecated and not maintained.
> >
> >This used to provide OpenMP DSP runtime components for legacy devices.
> >
> 
> With all the OpenCL stuff gone from meta-arago, dsplib/mathlib/imglib/swtools
> can also be dropped.

None of those use OpenCL and are rather self-contained (either prebuilt 
binaries, or use existing components from meta-ti, like CGT).

But they are in the same bucket of deprecated DSP-programming enablement in 
TI-SDK. Moreover, we are seeing deeper issues with old CGT versions generating 
non-reproducible code, so this class of components was pending a second round 
of clean ups...


> On the side, dspdce-fw and ipumm-fw should be updated
> to be shipped as binaries, same as we do with all other sysbios/ti-rtos 
> firmware.
> Then we could also drop out all the remaining sysbios/xdc bits.

Yes, that was the thinking. Someone needs to add prebuilt FW binaries to 
ti-linux-firmware repo before the rest of dependencies can finally be dropped 
from meta-ti.


> Andrew
> 
> >Signed-off-by: Denys Dmytriyenko 
> >---
> >  .../recipes-ti/openmp-rtos/openmp-rtos_git.bb | 62 ---
> >  1 file changed, 62 deletions(-)
> >  delete mode 100644 meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb
> >
> >diff --git a/meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb 
> >b/meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb
> >deleted file mode 100644
> >index aa4bc6cd..
> >--- a/meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb
> >+++ /dev/null
> >@@ -1,62 +0,0 @@
> >-DESCRIPTION = "TI OpenMP RTOS"
> >-HOMEPAGE = "git://git.ti.com/git/openmp/ti-openmp-dsp-runtime.git"
> >-LICENSE = "BSD-3-Clause"
> >-
> >-require recipes-ti/includes/ti-paths.inc
> >-
> >-inherit features_check
> >-
> >-REQUIRED_MACHINE_FEATURES = "dsp"
> >-REQUIRED_DISTRO_FEATURES = "openmp"
> >-
> >-PV = "2_06_03_00"
> >-PR = "r0"
> >-
> >-OPENMP_RTOS_GIT_URI = 
> >"git://git.ti.com/git/openmp/ti-openmp-dsp-runtime.git"
> >-OPENMP_RTOS_GIT_PROTOCOL = "https"
> >-OPENMP_RTOS_GIT_BRANCH = "master"
> >-
> >-BRANCH = "${OPENMP_RTOS_GIT_BRANCH}"
> >-SRC_URI = 
> >"${OPENMP_RTOS_GIT_URI};protocol=${OPENMP_RTOS_GIT_PROTOCOL};branch=${BRANCH}"
> >-
> >-SRCREV = "c090eb664d9815a36ead0e14f31e102590680fb8"
> >-
> >-LIC_FILES_CHKSUM = 
> >"file://docs/license/omp_manifest_template.html;md5=61a6972303c0447b7c056195d7ebafee"
> >-
> >-DEPENDS = "common-csl-ip-rtos doxygen-native libulm ti-xdctools-native 
> >ti-ipc-rtos ti-sysbios ti-cgt6x-native zip-native"
> >-
> >-COMPATIBLE_MACHINE = "omap-a15"
> >-PACKAGE_ARCH = "${MACHINE_ARCH}"
> >-
> >-S = "${WORKDIR}/git"
> >-export IPC_DIR = "${IPC_INSTALL_DIR}"
> >-export XDC_DIR = "${XDC_INSTALL_DIR}"
> >-export BIOS_DIR = "${SYSBIOS_INSTALL_DIR}"
> >-export ULM_DIR ="${STAGING_DIR_TARGET}/usr/share/ti/ulm"
> >-export C6636_PDK_DIR ="${PDK_INSTALL_DIR}"
> >-export AM572_PDK_DIR ="${PDK_INSTALL_DIR}"
> >-export XDCCGROOT = "${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x"
> >-
> >-export BUILD_AM572 = "0"
> >-
> >-BUILD_AM572:omap-a15 = "1"
> >-
> >-RELEASE_TARGET = ""
> >-RELEASE_TARGET:omap-a15 = "am57xx"
> >-
> >-do_compile() {
> >-make -f utils/product/Makefile .zipfile
> >-}
> >-
> >-do_install() {
> >-install -d ${D}${OMP_INSTALL_DIR_RECIPE}
> >-cp -r ${S}/exports/openmp_dsp_${RELEASE_TARGET}_*/. -d  
> >${D}${OMP_INSTALL_DIR_RECIPE}
> >-}
> >-
> >-ALLOW_EMPTY:${PN} = "1"
> >-
> >-FILES:${PN}-dev += " \
> >-${OMP_INSTALL_DIR_RECIPE}/ \
> >-"
> >-
> >-INSANE_SKIP:${PN}-dev = "arch"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17948): 
https://lists.yoctoproject.org/g/meta-ti/message/17948
Mute This Topic: https://lists.yoctoproject.org/mt/107727040/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][RFC PATCH] openmp-rtos: deprecate

2024-08-04 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Remove openmp-rtos component as deprecated and not maintained.

This used to provide OpenMP DSP runtime components for legacy devices.

Signed-off-by: Denys Dmytriyenko 
---
 .../recipes-ti/openmp-rtos/openmp-rtos_git.bb | 62 ---
 1 file changed, 62 deletions(-)
 delete mode 100644 meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb

diff --git a/meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb 
b/meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb
deleted file mode 100644
index aa4bc6cd..
--- a/meta-ti-extras/recipes-ti/openmp-rtos/openmp-rtos_git.bb
+++ /dev/null
@@ -1,62 +0,0 @@
-DESCRIPTION = "TI OpenMP RTOS"
-HOMEPAGE = "git://git.ti.com/git/openmp/ti-openmp-dsp-runtime.git"
-LICENSE = "BSD-3-Clause"
-
-require recipes-ti/includes/ti-paths.inc
-
-inherit features_check
-
-REQUIRED_MACHINE_FEATURES = "dsp"
-REQUIRED_DISTRO_FEATURES = "openmp"
-
-PV = "2_06_03_00"
-PR = "r0"
-
-OPENMP_RTOS_GIT_URI = "git://git.ti.com/git/openmp/ti-openmp-dsp-runtime.git"
-OPENMP_RTOS_GIT_PROTOCOL = "https"
-OPENMP_RTOS_GIT_BRANCH = "master"
-
-BRANCH = "${OPENMP_RTOS_GIT_BRANCH}"
-SRC_URI = 
"${OPENMP_RTOS_GIT_URI};protocol=${OPENMP_RTOS_GIT_PROTOCOL};branch=${BRANCH}"
-
-SRCREV = "c090eb664d9815a36ead0e14f31e102590680fb8"
-
-LIC_FILES_CHKSUM = 
"file://docs/license/omp_manifest_template.html;md5=61a6972303c0447b7c056195d7ebafee"
-
-DEPENDS = "common-csl-ip-rtos doxygen-native libulm ti-xdctools-native 
ti-ipc-rtos ti-sysbios ti-cgt6x-native zip-native"
-
-COMPATIBLE_MACHINE = "omap-a15"
-PACKAGE_ARCH = "${MACHINE_ARCH}"
-
-S = "${WORKDIR}/git"
-export IPC_DIR = "${IPC_INSTALL_DIR}"
-export XDC_DIR = "${XDC_INSTALL_DIR}"
-export BIOS_DIR = "${SYSBIOS_INSTALL_DIR}"
-export ULM_DIR ="${STAGING_DIR_TARGET}/usr/share/ti/ulm"
-export C6636_PDK_DIR ="${PDK_INSTALL_DIR}"
-export AM572_PDK_DIR ="${PDK_INSTALL_DIR}"
-export XDCCGROOT = "${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x"
-
-export BUILD_AM572 = "0"
-
-BUILD_AM572:omap-a15 = "1"
-
-RELEASE_TARGET = ""
-RELEASE_TARGET:omap-a15 = "am57xx"
-
-do_compile() {
-make -f utils/product/Makefile .zipfile
-}
-
-do_install() {
-install -d ${D}${OMP_INSTALL_DIR_RECIPE}
-cp -r ${S}/exports/openmp_dsp_${RELEASE_TARGET}_*/. -d  
${D}${OMP_INSTALL_DIR_RECIPE}
-}
-
-ALLOW_EMPTY:${PN} = "1"
-
-FILES:${PN}-dev += " \
-${OMP_INSTALL_DIR_RECIPE}/ \
-"
-
-INSANE_SKIP:${PN}-dev = "arch"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17923): 
https://lists.yoctoproject.org/g/meta-ti/message/17923
Mute This Topic: https://lists.yoctoproject.org/mt/107727040/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH] conf: machine: omapl138-lcdk: Update KERNEL_DEVICETREE

2024-08-04 Thread Denys Dmytriyenko

On Sun, Aug 04, 2024 at 05:15:09PM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> Update the entry for KERNEL_DEVICETREE to match what is in the 6.10
> kernel.

Will this change work with 6.6 (or even 6.1)?


> Signed-off-by: Ryan Eatmon 
> ---
>  meta-ti-bsp/conf/machine/omapl138-lcdk.conf | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-ti-bsp/conf/machine/omapl138-lcdk.conf 
> b/meta-ti-bsp/conf/machine/omapl138-lcdk.conf
> index fdbaffae..458caaff 100644
> --- a/meta-ti-bsp/conf/machine/omapl138-lcdk.conf
> +++ b/meta-ti-bsp/conf/machine/omapl138-lcdk.conf
> @@ -21,6 +21,6 @@ KERNEL_DEVICETREE_PREFIX = " \
>  "
>  
>  KERNEL_DEVICETREE = " \
> -da850-evm.dtb \
> -da850-lcdk.dtb \
> +ti/davinci/da850-evm.dtb \
> +ti/davinci/da850-lcdk.dtb \
>  "
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17922): 
https://lists.yoctoproject.org/g/meta-ti/message/17922
Mute This Topic: https://lists.yoctoproject.org/mt/107722812/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH v2] linux: Manage the kernel patches using the BSP system

2024-07-24 Thread Denys Dmytriyenko

On Fri, Jul 19, 2024 at 10:10:18AM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> Applying the patches to all kernels is not going to work.  Each kernel
> might need different patches to address reproducibility issues.

Can you also backport this to scarthgap, as these patches fon't apply cleanly 
to bb.org and currently break Beagle builds. Thanks.


> Signed-off-by: Ryan Eatmon 
> ---
> v2: Fix BSP tag for bsp-ti-6_6
> 
>  meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc | 12 
>  1 file changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc 
> b/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc
> index f24fbe51..1831ba66 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc
> +++ b/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc
> @@ -13,8 +13,12 @@ EXTRA_DTC_ARGS += "${@get_extra_dtc_args(d)}"
>  KERNEL_DTBDEST = "${KERNEL_IMAGEDEST}/dtb"
>  KERNEL_DTBVENDORED = "1"
>  
> -SRC_URI:append = " \
> -file://0001-lib-build_OID_registry-fix-reproducibility-issues.patch \
> -file://0001-vt-conmakehash-improve-reproducibility.patch \
> -file://0001-pnmtologo-use-relocatable-file-name.patch \
> +KERNEL_PATCHES = ""
> +
> +KERNEL_PATCHES:bsp-ti-6_6 = " \
> +file://0001-lib-build_OID_registry-fix-reproducibility-issues.patch \
> +file://0001-vt-conmakehash-improve-reproducibility.patch \
> +file://0001-pnmtologo-use-relocatable-file-name.patch \
>  "
> +
> +SRC_URI:append = " ${KERNEL_PATCHES} "
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17905): 
https://lists.yoctoproject.org/g/meta-ti/message/17905
Mute This Topic: https://lists.yoctoproject.org/mt/107436568/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master][PATCH] libulm: Fix "buildpaths" QA error

2024-07-20 Thread Denys Dmytriyenko

On Sat, Jul 20, 2024 at 02:02:01PM -0400, Denys Dmytriyenko wrote:
> On Fri, Jul 19, 2024 at 03:36:03PM -0500, Ryan Eatmon via 
> lists.yoctoproject.org wrote:
> > The TI cl6x compiler does not have a mechanism for replacing paths in
> > the obj files it creates.  So replace the string we want to remove with
> > an equally sized replacement string that does not contain the path.
> > 
> > Signed-off-by: Ryan Eatmon 
> > ---
> >  ...m-makefile-Fix-reproducibility-error.patch | 31 +++
> >  .../recipes-bsp/dsptop/libulm_git.bb  | 12 +--
> >  2 files changed, 41 insertions(+), 2 deletions(-)
> >  create mode 100644 
> > meta-ti-extras/recipes-bsp/dsptop/files/0001-dstop-ulm-makefile-Fix-reproducibility-error.patch
> > 
> > diff --git 
> > a/meta-ti-extras/recipes-bsp/dsptop/files/0001-dstop-ulm-makefile-Fix-reproducibility-error.patch
> >  
> > b/meta-ti-extras/recipes-bsp/dsptop/files/0001-dstop-ulm-makefile-Fix-reproducibility-error.patch
> > new file mode 100644
> > index ..6ea59517
> > --- /dev/null
> > +++ 
> > b/meta-ti-extras/recipes-bsp/dsptop/files/0001-dstop-ulm-makefile-Fix-reproducibility-error.patch
> > @@ -0,0 +1,31 @@
> > +From 8619e4b2f983130bf1909cc9c9bc238cd43ded41 Mon Sep 17 00:00:00 2001
> > +From: Ryan Eatmon 
> > +Date: Fri, 19 Jul 2024 14:37:55 -0500
> > +Subject: [master][PATCH] dstop/ulm/makefile: Fix reproducibility error
> > +
> > +The TI cl6x compiler does not have a mechanism for replacing paths in
> > +the obj files it creates.  So replace the string we want to remove with
> > +an equally sized replacement string that does not contain the path.
> > +
> > +Upstream-Status: Inappropriate [OE-specific]
> > +
> > +Signed-off-by: Ryan Eatmon 
> > +---
> > + makefile | 1 +
> > + 1 file changed, 1 insertion(+)
> > +
> > +diff --git a/makefile b/makefile
> > +index dffb211..586dcc2 100644
> > +--- a/makefile
> >  b/makefile
> > +@@ -82,6 +82,7 @@ $(OBJDIR)/%.obj: %.c $(INCLUDE_FILES)
> > +   @echo "Compiling" $<
> > +   @mkdir -p $(OBJDIR)
> > +   $(CC) $(CFLAGS) $(INCLUDE_PATH) -fe $@ $<
> > ++  perl -pi -e 's#${SEARCH}#${REPLACE}#g' $@
> 
> That assumes perl host tool dependency - is it safe? Can this be done with 
> sed instead?

Never mind - I see you have perl-native in DEPENDS.

And for patching binary files perl is definitely better than sed.


> > + libtiulm.a libtiulm.ae66: $(OBJECTS)
> > +   @echo "Building target" $@
> > +-- 
> > +2.17.1
> > +
> > diff --git a/meta-ti-extras/recipes-bsp/dsptop/libulm_git.bb 
> > b/meta-ti-extras/recipes-bsp/dsptop/libulm_git.bb
> > index 6a2cde30..aafae21f 100644
> > --- a/meta-ti-extras/recipes-bsp/dsptop/libulm_git.bb
> > +++ b/meta-ti-extras/recipes-bsp/dsptop/libulm_git.bb
> > @@ -6,7 +6,7 @@ inherit features_check
> >  
> >  REQUIRED_MACHINE_FEATURES = "dsp"
> >  
> > -DEPENDS = "ti-cgt6x-native"
> > +DEPENDS = "ti-cgt6x-native perl-native"
> >  PR = "${INC_PR}.0"
> >  
> >  S = "${WORKDIR}/git/dsptop/ulm"
> > @@ -14,7 +14,13 @@ S = "${WORKDIR}/git/dsptop/ulm"
> >  DEVICE=""
> >  DEVICE:dra7xx = "DRA7xx"
> >  
> > -EXTRA_OEMAKE = "release DEVICE=${DEVICE} CROSS_COMPILE=${TARGET_PREFIX}"
> > +EXTRA_OEMAKE = " \
> > +release \
> > +DEVICE=${DEVICE} \
> > +CROSS_COMPILE=${TARGET_PREFIX} \
> > +SEARCH=${WORKDIR} \
> > +REPLACE=${@'_'*(len(d.getVar('WORKDIR'))-7)+"workdir"} \
> > +"
> >  
> >  do_compile() {
> >  oe_runmake arm XPORT_ONLY CC="${CC}"
> > @@ -40,6 +46,8 @@ FILES:${PN}-dev += "\
> >  
> >  include dsptop.inc
> >  
> > +SRC_URI += "file://0001-dstop-ulm-makefile-Fix-reproducibility-error.patch"
> > +
> >  ALLOW_EMPTY:${PN} = "1"
> >  
> >  PARALLEL_MAKE= ""
> > -- 
> > 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17901): 
https://lists.yoctoproject.org/g/meta-ti/message/17901
Mute This Topic: https://lists.yoctoproject.org/mt/107442178/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master][PATCH] libulm: Fix "buildpaths" QA error

2024-07-20 Thread Denys Dmytriyenko

On Fri, Jul 19, 2024 at 03:36:03PM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> The TI cl6x compiler does not have a mechanism for replacing paths in
> the obj files it creates.  So replace the string we want to remove with
> an equally sized replacement string that does not contain the path.
> 
> Signed-off-by: Ryan Eatmon 
> ---
>  ...m-makefile-Fix-reproducibility-error.patch | 31 +++
>  .../recipes-bsp/dsptop/libulm_git.bb  | 12 +--
>  2 files changed, 41 insertions(+), 2 deletions(-)
>  create mode 100644 
> meta-ti-extras/recipes-bsp/dsptop/files/0001-dstop-ulm-makefile-Fix-reproducibility-error.patch
> 
> diff --git 
> a/meta-ti-extras/recipes-bsp/dsptop/files/0001-dstop-ulm-makefile-Fix-reproducibility-error.patch
>  
> b/meta-ti-extras/recipes-bsp/dsptop/files/0001-dstop-ulm-makefile-Fix-reproducibility-error.patch
> new file mode 100644
> index ..6ea59517
> --- /dev/null
> +++ 
> b/meta-ti-extras/recipes-bsp/dsptop/files/0001-dstop-ulm-makefile-Fix-reproducibility-error.patch
> @@ -0,0 +1,31 @@
> +From 8619e4b2f983130bf1909cc9c9bc238cd43ded41 Mon Sep 17 00:00:00 2001
> +From: Ryan Eatmon 
> +Date: Fri, 19 Jul 2024 14:37:55 -0500
> +Subject: [master][PATCH] dstop/ulm/makefile: Fix reproducibility error
> +
> +The TI cl6x compiler does not have a mechanism for replacing paths in
> +the obj files it creates.  So replace the string we want to remove with
> +an equally sized replacement string that does not contain the path.
> +
> +Upstream-Status: Inappropriate [OE-specific]
> +
> +Signed-off-by: Ryan Eatmon 
> +---
> + makefile | 1 +
> + 1 file changed, 1 insertion(+)
> +
> +diff --git a/makefile b/makefile
> +index dffb211..586dcc2 100644
> +--- a/makefile
>  b/makefile
> +@@ -82,6 +82,7 @@ $(OBJDIR)/%.obj: %.c $(INCLUDE_FILES)
> + @echo "Compiling" $<
> + @mkdir -p $(OBJDIR)
> + $(CC) $(CFLAGS) $(INCLUDE_PATH) -fe $@ $<
> ++perl -pi -e 's#${SEARCH}#${REPLACE}#g' $@

That assumes perl host tool dependency - is it safe? Can this be done with 
sed instead?


> + 
> + libtiulm.a libtiulm.ae66: $(OBJECTS)
> + @echo "Building target" $@
> +-- 
> +2.17.1
> +
> diff --git a/meta-ti-extras/recipes-bsp/dsptop/libulm_git.bb 
> b/meta-ti-extras/recipes-bsp/dsptop/libulm_git.bb
> index 6a2cde30..aafae21f 100644
> --- a/meta-ti-extras/recipes-bsp/dsptop/libulm_git.bb
> +++ b/meta-ti-extras/recipes-bsp/dsptop/libulm_git.bb
> @@ -6,7 +6,7 @@ inherit features_check
>  
>  REQUIRED_MACHINE_FEATURES = "dsp"
>  
> -DEPENDS = "ti-cgt6x-native"
> +DEPENDS = "ti-cgt6x-native perl-native"
>  PR = "${INC_PR}.0"
>  
>  S = "${WORKDIR}/git/dsptop/ulm"
> @@ -14,7 +14,13 @@ S = "${WORKDIR}/git/dsptop/ulm"
>  DEVICE=""
>  DEVICE:dra7xx = "DRA7xx"
>  
> -EXTRA_OEMAKE = "release DEVICE=${DEVICE} CROSS_COMPILE=${TARGET_PREFIX}"
> +EXTRA_OEMAKE = " \
> +release \
> +DEVICE=${DEVICE} \
> +CROSS_COMPILE=${TARGET_PREFIX} \
> +SEARCH=${WORKDIR} \
> +REPLACE=${@'_'*(len(d.getVar('WORKDIR'))-7)+"workdir"} \
> +"
>  
>  do_compile() {
>  oe_runmake arm XPORT_ONLY CC="${CC}"
> @@ -40,6 +46,8 @@ FILES:${PN}-dev += "\
>  
>  include dsptop.inc
>  
> +SRC_URI += "file://0001-dstop-ulm-makefile-Fix-reproducibility-error.patch"
> +
>  ALLOW_EMPTY:${PN} = "1"
>  
>  PARALLEL_MAKE= ""
> -- 
> 2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17900): 
https://lists.yoctoproject.org/g/meta-ti/message/17900
Mute This Topic: https://lists.yoctoproject.org/mt/107442178/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCH] linux: Manage the kernel patches using the BSP system

2024-07-20 Thread Denys Dmytriyenko

On Fri, Jul 19, 2024 at 09:18:14AM -0500, Ryan Eatmon via 
lists.yoctoproject.org wrote:
> 
> 
> On 7/19/2024 8:29 AM, Ryan Eatmon via lists.yoctoproject.org wrote:
> >
> >
> >On 7/18/2024 11:27 PM, Chirag Shilwant wrote:
> >>Hi Ryan,
> >>On 18/07/24 23:54, Ryan Eatmon via lists.yoctoproject.org wrote:
> >>>Applying the patches to all kernels is not going to work. Each
> >>>kernel might need different patches to address reproducibility
> >>>issues. Signed-off-by: Ryan Eatmon  ---
> >>>meta-ti-bsp/recipes-kernel/linux/ti-kernel. inc | 12
> >>>ZjQcmQRYFpfptBannerStart
> >>>This message was sent from outside of Texas Instruments.
> >>>Do not click links or open attachments unless you recognize
> >>>the source of this email and know the content is safe. If you
> >>>wish to report this message to IT Security, please forward the
> >>>message as an attachment to phish...@list.ti.com
> >>>ZjQcmQRYFpfptBannerEnd
> >>>Applying the patches to all kernels is not going to work.  Each kernel
> >>>might need different patches to address reproducibility issues.
> >>>
> >>>Signed-off-by: Ryan Eatmon 
> >>>---
> >>>  meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc | 12 
> >>>  1 file changed, 8 insertions(+), 4 deletions(-)
> >>>
> >>>diff --git a/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc
> >>>b/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc
> >>>index f24fbe51..8bb30d40 100644
> >>>--- a/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc
> >>>+++ b/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc
> >>>@@ -13,8 +13,12 @@ EXTRA_DTC_ARGS += "${@get_extra_dtc_args(d)}"
> >>>  KERNEL_DTBDEST = "${KERNEL_IMAGEDEST}/dtb"
> >>>  KERNEL_DTBVENDORED = "1"
> >>>-SRC_URI:append = " \
> >>>-file://0001-lib-build_OID_registry-fix-reproducibility-issues.patch \
> >>>-file://0001-vt-conmakehash-improve-reproducibility.patch \
> >>>-file://0001-pnmtologo-use-relocatable-file-name.patch \
> >>>+KERNEL_PATCHES = ""
> >>>+
> >>>+KERNEL_PATCHES:bsp-ti-6.6 = " \
> 
> This is wrong.  Should be bsp-ti-6_6.  Still not used to the name
> scheme for this.  I'll send a v2.

Yeah, this is an override, hence the number of special characters is limited - 
had to replace dot with underscore...


> >>>+ file://0001-lib-build_OID_registry-fix-reproducibility-issues.patch \
> >>>+    file://0001-vt-conmakehash-improve-reproducibility.patch \
> >>>+    file://0001-pnmtologo-use-relocatable-file-name.patch \
> >>>  "
> >>
> >>
> >>
> >>The patch title says [master/scarthgap] but I don't see these
> >>patches in scarthgap getting applied
> >
> >I'll look into it.  I've been a little preoccupied with master
> >this week, but I'll take a look today.
> >
> >
> >  [1]
> >>Additionally the patches itself are missing in scarthgap branch [2]
> >>Are they applicable to scarthgap?
> >
> >Yes, they are.
> >
> >
> >>[1]: 
> >>https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-bsp/recipes-kernel/linux/ti-kernel.inc?h=scarthgap
> >>
> >>[2]: 
> >>https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-bsp/recipes-kernel/linux/files?h=scarthgap
> >>
> >>
> >>
> >>>+
> >>>+SRC_URI:append = " ${KERNEL_PATCHES} "
> >>>-- 
> >>>2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17899): 
https://lists.yoctoproject.org/g/meta-ti/message/17899
Mute This Topic: https://lists.yoctoproject.org/mt/107421992/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH] ti-cgt-pru: remove install log to avoid "buildpaths" QA error

2024-07-15 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Installer log contains absolute paths and is not really needed.

Signed-off-by: Denys Dmytriyenko 
---
 meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb 
b/meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb
index 47bd6a51..b77aa612 100644
--- a/meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb
+++ b/meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb
@@ -28,6 +28,7 @@ do_install() {
 install -d ${D}${TI_CGT_PRU_INSTALL_DIR_RECIPE}
 cp -r ${UNPACKDIR}/ti-cgt-pru_${PV}/. \
   ${D}${TI_CGT_PRU_INSTALL_DIR_RECIPE}/
+rm ${D}${TI_CGT_PRU_INSTALL_DIR_RECIPE}/*installer_install.log
 }
 
 do_install:class-target() {
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17865): 
https://lists.yoctoproject.org/g/meta-ti/message/17865
Mute This Topic: https://lists.yoctoproject.org/mt/107244952/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master][PATCH 1/2] linux: remove old unused patches

2024-07-15 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

These patches are not used anywhere now.

Signed-off-by: Denys Dmytriyenko 
---
 ...s-Fix-build-for-upcoming-GCC-release.patch |  46 
 ...ture-changes-causes-compile-failures.patch | 111 --
 2 files changed, 157 deletions(-)
 delete mode 100644 
meta-ti-bsp/recipes-kernel/linux/files/0001-gcc-plugins-Fix-build-for-upcoming-GCC-release.patch
 delete mode 100644 
meta-ti-bsp/recipes-kernel/linux/files/init_disassemble_info-signature-changes-causes-compile-failures.patch

diff --git 
a/meta-ti-bsp/recipes-kernel/linux/files/0001-gcc-plugins-Fix-build-for-upcoming-GCC-release.patch
 
b/meta-ti-bsp/recipes-kernel/linux/files/0001-gcc-plugins-Fix-build-for-upcoming-GCC-release.patch
deleted file mode 100644
index 3dfa31a1..
--- 
a/meta-ti-bsp/recipes-kernel/linux/files/0001-gcc-plugins-Fix-build-for-upcoming-GCC-release.patch
+++ /dev/null
@@ -1,46 +0,0 @@
-From 3cd29a3d7c25cca9989e7d8966141f725fa99c68 Mon Sep 17 00:00:00 2001
-From: Palmer Dabbelt 
-Date: Fri, 13 Jan 2023 09:30:33 -0800
-Subject: [PATCH] gcc-plugins: Fix build for upcoming GCC release
-
-The upcoming GCC release has refactored the gimple plugin interface a
-bit and unless gimple-iterator.h is included before gimple-fold.h I end
-up with a bunch of missing declarations when building the stack
-protector plugin.
-
-Upstream-Status: Backport 
[https://lore.kernel.org/all/20230113173033.4380-1-pal...@rivosinc.com/]
-Reported-by: Palmer Dabbelt 
-Acked-by: Palmer Dabbelt 
-Link: https://lore.kernel.org/all/20230113173033.4380-1-pal...@rivosinc.com/
-Cc: linux-harden...@vger.kernel.org
-Signed-off-by: Kees Cook 

- scripts/gcc-plugins/gcc-common.h | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
 a/scripts/gcc-plugins/gcc-common.h
-+++ b/scripts/gcc-plugins/gcc-common.h
-@@ -108,7 +108,9 @@
- #include "varasm.h"
- #include "stor-layout.h"
- #include "internal-fn.h"
-+#include "gimple.h"
- #include "gimple-expr.h"
-+#include "gimple-iterator.h"
- #include "gimple-fold.h"
- #include "context.h"
- #include "tree-ssa-alias.h"
-@@ -124,13 +126,10 @@
- #include "gimplify.h"
- #endif
-
--#include "gimple.h"
--
- #if BUILDING_GCC_VERSION >= 4009
- #include "tree-ssa-operands.h"
- #include "tree-phinodes.h"
- #include "tree-cfg.h"
--#include "gimple-iterator.h"
- #include "gimple-ssa.h"
- #include "ssa-iterators.h"
- #endif
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/files/init_disassemble_info-signature-changes-causes-compile-failures.patch
 
b/meta-ti-bsp/recipes-kernel/linux/files/init_disassemble_info-signature-changes-causes-compile-failures.patch
deleted file mode 100644
index e1e04c34..
--- 
a/meta-ti-bsp/recipes-kernel/linux/files/init_disassemble_info-signature-changes-causes-compile-failures.patch
+++ /dev/null
@@ -1,111 +0,0 @@
-
-Adaption of a patch [A] applied to meta-arm for the kernel.  But since TI has 
it's own
-kernel we have to "adjust" the patch to match our files.
-
-[A] 
https://patchwork.yoctoproject.org/project/arm/patch/20220824025819.4888-1-jon.ma...@arm.com/#5104
-
-Upstream-Status: Pending
-
-Signed-off-by: Ryan Eatmon 
-
-
-
-From 1b2013986271de39360cf79e62ed9b7d2cc59f9b Mon Sep 17 00:00:00 2001
-From: Andres Freund 
-Date: Wed, 22 Jun 2022 11:19:18 -0700
-Subject: [PATCH] init_disassemble_info() signature changes causes compile
- failures
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Hi,
-
-binutils changed the signature of init_disassemble_info(), which now causes
-perf and bpftool to fail to compile (e.g. on debian unstable).
-
-Relevant binutils commit: 
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=60a3da00bd5407f07d64dff82a4dae98230dfaac
-
-util/annotate.c: In function ?symbol__disassemble_bpf?:
-util/annotate.c:1765:9: error: too few arguments to function 
?init_disassemble_info?
- 1765 | init_disassemble_info(&info, s,
-  | ^
-In file included from util/annotate.c:1718:
-/usr/include/dis-asm.h:472:13: note: declared here
-  472 | extern void init_disassemble_info (struct disassemble_info *dinfo, 
void *stream,
-  | ^
-
-with equivalent failures in
-
-tools/bpf/bpf_jit_disasm.c
-tools/bpf/bpftool/jit_disasm.c
-
-The fix is easy enough, add a wrapper around fprintf() that conforms to the
-new signature.
-
-However I assume the necessary feature test and wrapper should only be added
-once? I don't know the kernel stuff well enough to choose the right structure
-here.
-
-Attached is my local fix for perf. Obviously would need work to be a real
-solution.
-
-Greetings,
-
-Andres Freund

-
-binutils 2.39 changed the signature of init_disassemble_info(),
-which now causes perf and bpftool to fail to compile.

[meta-ti] [master][PATCH 2/2] linux: add linux-yocto reproducibility patches

2024-07-15 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Add reproducibility patches from linux-yocto to resolve "buildpaths"
QA errors.

Signed-off-by: Denys Dmytriyenko 
---
 ..._registry-fix-reproducibility-issues.patch | 46 +++
 ...-pnmtologo-use-relocatable-file-name.patch | 55 ++
 ...-conmakehash-improve-reproducibility.patch | 56 +++
 .../recipes-kernel/linux/ti-kernel.inc|  6 ++
 4 files changed, 163 insertions(+)
 create mode 100644 
meta-ti-bsp/recipes-kernel/linux/files/0001-lib-build_OID_registry-fix-reproducibility-issues.patch
 create mode 100644 
meta-ti-bsp/recipes-kernel/linux/files/0001-pnmtologo-use-relocatable-file-name.patch
 create mode 100644 
meta-ti-bsp/recipes-kernel/linux/files/0001-vt-conmakehash-improve-reproducibility.patch

diff --git 
a/meta-ti-bsp/recipes-kernel/linux/files/0001-lib-build_OID_registry-fix-reproducibility-issues.patch
 
b/meta-ti-bsp/recipes-kernel/linux/files/0001-lib-build_OID_registry-fix-reproducibility-issues.patch
new file mode 100644
index ..98af632f
--- /dev/null
+++ 
b/meta-ti-bsp/recipes-kernel/linux/files/0001-lib-build_OID_registry-fix-reproducibility-issues.patch
@@ -0,0 +1,46 @@
+From 2fca0fd719812ea2ff67630b01355aa80481623e Mon Sep 17 00:00:00 2001
+From: Bruce Ashfield 
+Date: Sun, 10 Jul 2022 22:56:53 -0400
+Subject: [PATCH] lib/build_OID_registry: fix reproducibility issues
+
+The script build_OID_registry captures the full path of itself
+in the generated data. This causes reproduciblity issues as the
+path is captured and packaged.
+
+We use the basename of the script instead, and that allows us
+to be reprodicible, with slightly less information captured in
+the output data (but the generating script can still easily
+be found).
+
+Signed-off-by: Bruce Ashfield 
+
+Upstream-Status: Inappropriate
+
+Signed-off-by: Denys Dmytriyenko 
+---
+ lib/build_OID_registry | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/lib/build_OID_registry b/lib/build_OID_registry
+index d7fc32ea8ac2..f6de0a7f7457 100755
+--- a/lib/build_OID_registry
 b/lib/build_OID_registry
+@@ -8,6 +8,7 @@
+ #
+ 
+ use strict;
++use File::Basename;
+ 
+ my @names = ();
+ my @oids = ();
+@@ -35,7 +36,7 @@ close IN_FILE || die;
+ #
+ open C_FILE, ">$ARGV[1]" or die;
+ print C_FILE "/*\n";
+-print C_FILE " * Automatically generated by ", $0, ".  Do not edit\n";
++print C_FILE " * Automatically generated by ", basename $0, ".  Do not 
edit\n";
+ print C_FILE " */\n";
+ 
+ #
+-- 
+2.25.1
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/files/0001-pnmtologo-use-relocatable-file-name.patch
 
b/meta-ti-bsp/recipes-kernel/linux/files/0001-pnmtologo-use-relocatable-file-name.patch
new file mode 100644
index ..7427b168
--- /dev/null
+++ 
b/meta-ti-bsp/recipes-kernel/linux/files/0001-pnmtologo-use-relocatable-file-name.patch
@@ -0,0 +1,55 @@
+From a40d2daf2795d89e3ef8af0413b25190558831ec Mon Sep 17 00:00:00 2001
+From: Bruce Ashfield 
+Date: Thu, 14 Jul 2022 14:43:46 -0400
+Subject: [PATCH] pnmtologo: use relocatable file name
+
+The logo generation utility is capturing the source of the logo
+in the generated .c file. The source file is absolute (as passed
+by make), so the full path is captured.
+
+This makes the source fail reproducibility tests.
+
+We use basename() to just get the source file name, and use
+that in the generated .c file.
+
+Signed-off-by: Bruce Ashfield 
+
+Upstream-Status: Inappropriate
+
+Signed-off-by: Denys Dmytriyenko 
+---
+ drivers/video/logo/pnmtologo.c | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/drivers/video/logo/pnmtologo.c b/drivers/video/logo/pnmtologo.c
+index ada5ef6e51b7..7527be845443 100644
+--- a/drivers/video/logo/pnmtologo.c
 b/drivers/video/logo/pnmtologo.c
+@@ -13,7 +13,7 @@
+ #include 
+ #include 
+ #include 
+-
++#include 
+ 
+ static const char *programname;
+ static const char *filename;
+@@ -223,6 +223,7 @@ static inline int is_equal(struct color c1, struct color 
c2)
+ 
+ static void write_header(void)
+ {
++  char *filename_basename = basename(filename);
+   /* open logo file */
+   if (outputname) {
+   out = fopen(outputname, "w");
+@@ -235,7 +236,7 @@ static void write_header(void)
+   fputs("/*\n", out);
+   fputs(" *  DO NOT EDIT THIS FILE!\n", out);
+   fputs(" *\n", out);
+-  fprintf(out, " *  It was automatically generated from %s\n", filename);
++  fprintf(out, " *  It was automatically generated from %s\n", 
filename_basename);
+   fputs(" *\n", out);
+   fprintf(out, " *  Linux logo %s\n", logoname);
+   fputs(" */\n\n", out);
+-- 
+2.25.1
diff --git 
a/meta-ti-bsp/recipes-kernel/linux/files/0001-vt-conmakehash-improve-reproducibility.patch
 
b/meta-ti-bsp/recipes-kernel/linux/files/0001-vt-co

[meta-ti] [master][PATCH] ti-cgt-pru: UNPACKDIR cleanup

2024-07-15 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Fix warning that S does not exist, since it defaults to ${WORKDIR}/${BP}

Signed-off-by: Denys Dmytriyenko 
---
 meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb | 7 +--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb 
b/meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb
index 47bd6a51..75bb7262 100644
--- a/meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb
+++ b/meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb
@@ -24,14 +24,17 @@ SRC_URI[cgt-pru-x86.sha256sum] = 
"1f1405167214f2c0ef848591b17a7799fdcd9f55f11bc9
 SRC_URI[cgt-pru-arm.md5sum] = "648a6d7d8162fd6a89f381c7b974e6b0"
 SRC_URI[cgt-pru-arm.sha256sum] = 
"8390cb77b46b728ce2940595b81406f76d86dfed58c21258e3206a7c1232ccf2"
 
+S = "${WORKDIR}/sources"
+UNPACKDIR = "${S}"
+
 do_install() {
 install -d ${D}${TI_CGT_PRU_INSTALL_DIR_RECIPE}
-cp -r ${UNPACKDIR}/ti-cgt-pru_${PV}/. \
+cp -r ${S}/ti-cgt-pru_${PV}/. \
   ${D}${TI_CGT_PRU_INSTALL_DIR_RECIPE}/
 }
 
 do_install:class-target() {
-${UNPACKDIR}/${BINFILE} --prefix ${D}
+${S}/${BINFILE} --prefix ${D}
 }
 
 FILES:${PN} += "${datadir}/ti/*"
-- 
2.35.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17861): 
https://lists.yoctoproject.org/g/meta-ti/message/17861
Mute This Topic: https://lists.yoctoproject.org/mt/107237660/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [master/scarthgap][PATCH] recipes-ti: jailhouse: Update jailhouse for scarthgap

2024-07-09 Thread Denys Dmytriyenko

On Tue, Jul 09, 2024 at 06:03:59PM +0530, Paresh Bhagat via 
lists.yoctoproject.org wrote:
> Update SRCREV for jailhouse which incorporates makefile changes for
> scarthgap.
> Add ${ARAGO_IMAGE_SUFFIX} so that jailhouse can pick correct inmate

NAK - this is meta-ti, no Arago specifics here.


> image for RT build.
> Skip QA checks for usrmerge and buildpath. This is required to package
> jailhouse in image.
> Update FILES:${PN}.
> 
> Signed-off-by: Paresh Bhagat 
> ---
>  .../recipes-ti/jailhouse/jailhouse_git.bb | 20 +--
>  .../recipes-ti/jailhouse/ti-jailhouse.inc |  2 +-
>  2 files changed, 10 insertions(+), 12 deletions(-)
> 
> diff --git a/meta-ti-extras/recipes-ti/jailhouse/jailhouse_git.bb 
> b/meta-ti-extras/recipes-ti/jailhouse/jailhouse_git.bb
> index 98ec0e9e..32e94dd0 100644
> --- a/meta-ti-extras/recipes-ti/jailhouse/jailhouse_git.bb
> +++ b/meta-ti-extras/recipes-ti/jailhouse/jailhouse_git.bb
> @@ -51,11 +51,11 @@ do_install() {
>   install -d ${D}/boot
>   if [ -n "${JH_RAMFS_IMAGE}" ]
>   then
> - if [ -f ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ]
> + if [ -f 
> ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}${ARAGO_IMAGE_SUFFIX}-${MACHINE}.rootfs.cpio
>  ]
>   then
> - install -m 0644 
> ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ${D}/boot
> + install -m 0644 
> ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}${ARAGO_IMAGE_SUFFIX}-${MACHINE}.rootfs.cpio
>  ${D}/boot
>   else
> - bberror "Could not find JH_RAMFS_IMAGE 
> (${JH_RAMFS_IMAGE}-${MACHINE}.cpio)!"
> + bberror "Could not find JH_RAMFS_IMAGE 
> (${JH_RAMFS_IMAGE}${ARAGO_IMAGE_SUFFIX}-${MACHINE}.rootfs.cpio)!"
>   bberror "Please make sure that \"cpio\" is in 
> IMAGE_FSTYPES."
>   fi
>   fi
> @@ -68,7 +68,7 @@ do_install() {
>   ./jailhouse-cell-linux -w ${D}${JH_DATADIR}/${JH_INMATE_DTB} \
>   -a ${JH_ARCH} -c "${JH_CMDLINE}" \
>   -d ../configs/${JH_ARCH}/dts/${JH_INMATE_DTB} \
> - -i ${D}/boot/${JH_RAMFS_IMAGE}-${MACHINE}.cpio \
> + -i 
> ${D}/boot/${JH_RAMFS_IMAGE}${ARAGO_IMAGE_SUFFIX}-${MACHINE}.rootfs.cpio \
>   ${D}${CELL_DIR}/${JH_LINUX_DEMO_CELL} \
>   ${DEPLOY_DIR_IMAGE}/Image \
>   | tr -cd '\11\12\15\40-\176' \
> @@ -96,7 +96,8 @@ RDEPENDS:pyjailhouse = "python3-core python3-ctypes 
> python3-fcntl python3-shell"
>  
>  RRECOMMENDS:${PN} = "${PN}-tools"
>  
> -INSANE_SKIP:${PN} = "ldflags"
> +INSANE_SKIP:${PN} = "ldflags usrmerge"
> +INSANE_SKIP:${PN}-dbg = "usrmerge buildpaths"
>  
>  KERNEL_MODULE_AUTOLOAD += "jailhouse"
>  
> @@ -117,10 +118,7 @@ python __anonymous () {
>  }
>  
>  FILES:${PN} = " \
> -/boot/* \
> -/usr/libexec \
> -/usr/sbin/* \
> -/usr/libexec/* \
> -/usr/share/* \
> -/lib/firmware/* \
> +/boot \
> +/usr \
> +/lib \
>  "
> diff --git a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc 
> b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> index 6faf16b8..2831e560 100644
> --- a/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> +++ b/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc
> @@ -14,7 +14,7 @@ LIC_FILES_CHKSUM = " \
>  COMPATIBLE_MACHINE = "am62xx|am62pxx"
>  TARGET_CC_ARCH += "${LDFLAGS}"
>  PV = "0.12+git"
> -SRCREV = "603819ef9a771a3c253a141220daab8e61751a43"
> +SRCREV = "9b494ddf4bd8845a2c1063352d08a274ef61777b"
>  BRANCH = "master"
>  SRC_URI = " \
>  
> git://git.ti.com/git/jailhouse/ti-jailhouse.git;protocol=https;branch=${BRANCH}
>  \
> -- 
> 2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17847): 
https://lists.yoctoproject.org/g/meta-ti/message/17847
Mute This Topic: https://lists.yoctoproject.org/mt/107121442/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][scarthgap][PATCH 0/3] conf: machine: j784s4/am68/am69 : Pick reused CSI overlays

2024-06-27 Thread Denys Dmytriyenko

Does this apply to master?


On Thu, Jun 27, 2024 at 02:04:28PM +0530, Vaishnav Achath via 
lists.yoctoproject.org wrote:
> CSI2 connectivity of J721E SK, AM68 SK and AM69 SK is similar and
> the camera overlays can be reused, this series adds the necessary
> changes to pick the reused overlays across these platforms.
> 
> Thanks and Regards,
> Vaishnav
> 
> Vaishnav Achath (3):
>   conf: machine: j784s4-evm: Pick overlays for CSI2 and FPD-Link
>   conf: machine: am68-sk: Pick overlays for IMX219 and FPD-Link
>   conf: machine: am69-sk: Pick overlays for IMX219 and FPD-Link
> 
>  meta-ti-bsp/conf/machine/am68-sk.conf| 2 ++
>  meta-ti-bsp/conf/machine/am69-sk.conf| 3 +++
>  meta-ti-bsp/conf/machine/j784s4-evm.conf | 2 ++
>  3 files changed, 7 insertions(+)
> 
> -- 
> 2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17814): 
https://lists.yoctoproject.org/g/meta-ti/message/17814
Mute This Topic: https://lists.yoctoproject.org/mt/106905382/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [RFC][master/scarthgap][PATCH 1/4] cc33conf: add new cc33conf tool for cc33xx devices

2024-06-24 Thread Denys Dmytriyenko

On Thu, Jun 20, 2024 at 03:40:22PM -0500, Sabeeh Khan via 
lists.yoctoproject.org wrote:
> 
> On 6/20/2024 3:20 PM, Denys Dmytriyenko wrote:
> >On Wed, Jun 19, 2024 at 10:21:59PM -0500, Sabeeh Khan via 
> >lists.yoctoproject.org wrote:
> >>cc33conf is a tool provided by TI to configure
> >>cc33xx WLAN devices. It can be used to change
> >>the RF parameters and other features of the target.
> >>Documentation for this tool is provided within the following link:
> >>https://www.ti.com/tool/CC33XX-SOFTWARE
> >>
> >>Signed-off-by: Sabeeh Khan
> >>---
> >>  .../cc33conf/cc33conf_git.bb  | 29 +++
> >>  1 file changed, 29 insertions(+)
> >>  create mode 100644 
> >> meta-ti-extras/recipes-connectivity/cc33conf/cc33conf_git.bb
> >>
> >>diff --git a/meta-ti-extras/recipes-connectivity/cc33conf/cc33conf_git.bb 
> >>b/meta-ti-extras/recipes-connectivity/cc33conf/cc33conf_git.bb
> >>new file mode 100644
> >>index ..1e4faa77
> >>--- /dev/null
> >>+++ b/meta-ti-extras/recipes-connectivity/cc33conf/cc33conf_git.bb
> >>@@ -0,0 +1,29 @@
> >>+DESCRIPTION = "Configuration utility for TI CC33xx wireless devices"
> >>+LICENSE = "BSD-3-Clause"
> >>+LIC_FILES_CHKSUM ="file://COPYING;md5=d5fc448a36efe573623542dcb989afc4"
> >>+
> >>+SRCREV = "a2f84140b8d67cfc94472cf92676a409d1e47d86"
> >>+SRC_URI = 
> >>"git://git.ti.com/git/cc33xx-wlan/cc33xx-utils.git;branch=master;protocol=https"
> >>+
> >>+PV = "1.7.0.120"
> >>+
> >>+S = "${WORKDIR}/git/cc33conf"
> >>+
> >>+EXTRA_OEMAKE = "CC="${CC}""
> >>+
> >>+do_install() {
> >>+   install -d ${D}${sbindir}
> >>+   install -d ${D}${sbindir}/cc33conf/
> >>+
> >>+   install -m 0755 cc33xxconf ${D}${sbindir}/cc33conf/
> >>+   install -m 0755 dictionary.txt ${D}${sbindir}/cc33conf/
> >>+   install -m 0755 default.conf ${D}${sbindir}/cc33conf/
> >>+   install -m 0755 README ${D}${sbindir}/cc33conf/
> >>+   install -m 0755 cc33xx-conf.conf ${D}${sbindir}/cc33conf/
> >>+   install -m 0755 cc33xx-conf.ini ${D}${sbindir}/cc33conf/
> >>+   install -m 0755 conf.h ${D}${sbindir}/cc33conf/
> >Should all these files really go into sbindir?
> 
> This recipe and tool is based off of wlconf. Since wlconf was
> already accepted,
> 
> I figured installing to a similar location would be practical.
> 
> However, I am open to other locations if you have suggestions.
> 
> The tool does use all of these files.

Well, wlconf does indeed set a bad precedent...

Are those files being used relative to the binary and hence should reside 
there?

The standard is to have conf files in /etc, binaries in /usr/bin or /bin, 
docs/READMEs in /usr/share/doc and .h headers in /usr/include.

And bitbake.conf sets all the corresponding variables accordingly, such as 
sysconfdir, bindir, datadir, docdir, includedir, etc:
https://git.openembedded.org/openembedded-core/tree/meta/conf/bitbake.conf

So, if the tool is capable of locating its files in the proper system-wide 
locations, the recipe should definitely install them in the right location.

-- 
Denys

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17805): 
https://lists.yoctoproject.org/g/meta-ti/message/17805
Mute This Topic: https://lists.yoctoproject.org/mt/106774312/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti][master/scarthgap][PATCHv2 0/2] gcc 14 and bsp provider fixup

2024-06-24 Thread Denys Dmytriyenko

On Mon, Jun 24, 2024 at 01:17:12PM -0500, r...@ti.com wrote:
> From: Randolph Sapp 
> 
> Resolve some issues afer the new bsp-provider selection logic was added and 
> add
> some patches to help with compilation flag checks in the KM.

FWIW, the new bsp-provider selection logic was not causing any new issues.

Anyone using meta-ti master and scarthgap from early February until late May 
were already exposed to this.

While 6.1 LTS was still the default, this change to 23.3 got merged on Feb 9:
https://git.yoctoproject.org/meta-ti/commit/?id=737807fc4360b7fe3cbe493a6104558c4658a046

Separate new 24.1 DDK for the 6.6 LTS was added on May 2, still disabled:
https://git.yoctoproject.org/meta-ti/commit/?id=d89907ec2322f23271917d75f052217dd8a2c27a

And then 6.6 LTS got flipped to become the default on May 23:
https://git.yoctoproject.org/meta-ti/commit/?id=d41d49cfdc6deee33a40ab44d453167c36462c89

When adding the BSP provider code and setting preferred versions, I did see 
the first commit that switched branches from 6.1 to 6.6, and I was considering 
reverting it (like you are proposing here with patch #1). But I didn't want to 
upset anyone and figured since this was already the default config for almost 
4 months (!) of using the updated 23.3 DDK with 6.1 LTS, I just left it alone.

So, the BSP provider logic just formalized all the existing defaults.


> This includes equivalent patches from the following post for GCC 14 compat:
> https://lists.yoctoproject.org/g/meta-ti/topic/106806264
> 
> Randolph Sapp (2):
>   ti-img-rogue-*_23.3: gcc 14 compat and branch sel
>   ti-img-rogue-driver_24.1: gcc 14 compat
> 
>  .../powervr-drivers/ti-img-rogue-driver_23.3.6512818.bb   | 4 ++--
>  .../powervr-drivers/ti-img-rogue-driver_24.1.6554834.bb   | 2 +-
>  .../powervr-umlibs/ti-img-rogue-umlibs_23.3.6512818.bb| 2 +-
>  3 files changed, 4 insertions(+), 4 deletions(-)
> 
> -- 
> 2.45.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17804): 
https://lists.yoctoproject.org/g/meta-ti/message/17804
Mute This Topic: https://lists.yoctoproject.org/mt/106855269/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [RFC][master/scarthgap][PATCH 4/4] cc33xx-target-scripts: add cc33xx scripts to control TI cc33xx WLAN device

2024-06-20 Thread Denys Dmytriyenko

On Thu, Jun 20, 2024 at 03:37:12PM -0500, Khan, Sabeeh wrote:
> 
> On 6/20/2024 3:27 PM, Denys Dmytriyenko wrote:
> >On Wed, Jun 19, 2024 at 10:22:02PM -0500, Sabeeh Khan via 
> >lists.yoctoproject.org wrote:
> >>[...]
> >>
> >>diff --git 
> >>a/meta-ti-extras/recipes-connectivity/cc33xx-target-scripts/cc33xx-target-scripts.bb
> >> 
> >>b/meta-ti-extras/recipes-connectivity/cc33xx-target-scripts/cc33xx-target-scripts.bb
> >>new file mode 100644
> >>index ..2f13f911
> >>--- /dev/null
> >>+++ 
> >>b/meta-ti-extras/recipes-connectivity/cc33xx-target-scripts/cc33xx-target-scripts.bb
> >>@@ -0,0 +1,22 @@
> >>+DESCRIPTION = "Scripts and configuration files for TI cc33xx wireless 
> >>drivers"
> >SUMMARY
> 
> Apologies for not being familiar, but are you suggesting here
> 
> to have "SUMMARY" variable instead of "DESCRIPTION", or in addition to?
> 
> Can I please have some more context over the ask here?
> 
> I don't see "SUMMARY" variable in other meta-ti recipes, so I'm
> looking for a reference.

https://docs.yoctoproject.org/ref-manual/variables.html#term-SUMMARY
https://docs.yoctoproject.org/ref-manual/variables.html#term-DESCRIPTION

SUMMARY is a shorter version of the package description (one-line under 72 
characters), while DESCRIPTION can be a longer multi-line description.

DESCRIPTION can be omitted and will be derived from SUMMARY, but not the other 
way around.

In the very old days only the DESCRIPTION was used, hence old recipes still 
don't set SUMMARY, but newly added recipes should not do that.

Here's one of the many recipes in meta-ti that properly uses/sets both:
https://git.yoctoproject.org/meta-ti/tree/meta-ti-extras/recipes-ti/jailhouse/ti-jailhouse.inc


> >>[...]
> >>+
> >>+do_install() {
> >>+   install -d ${D}${datadir}/cc33xx/
> >>+
> >>+   scripts=`find ./* -type f -name "*.*"`
> >Is this find command necessary?
> 
> The recipe should install .sh and .conf files from the git repo only.
> 
> This was done to ignore any README or license files and not have
> them installed.

I believe you can use globs directly with install, unless there's a 
directory hierarchy:

install -m 0755 *.* ${D}${datadir}/cc33xx/

-- 
Denys

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17789): 
https://lists.yoctoproject.org/g/meta-ti/message/17789
Mute This Topic: https://lists.yoctoproject.org/mt/106774315/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master/scarthgap][PATCH] linux: cleanup and unify mainline and next kernel recipes

2024-06-20 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Share the most commonality between the recipes, except:

* SRC_URI torvalds vs. linux-next
* SRCREV and PV
* Device Tree list vs. DT prefix
* SUMMARY

Signed-off-by: Denys Dmytriyenko 
---
 .../linux/linux-ti-mainline_git.bb| 19 +++
 .../recipes-kernel/linux/linux-ti-next_git.bb | 19 ++-
 2 files changed, 5 insertions(+), 33 deletions(-)

diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb 
b/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb
index 47b573e1..77ebb11e 100644
--- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb
+++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb
@@ -9,30 +9,17 @@ require recipes-kernel/linux/ti-kernel.inc
 
 DEPENDS += "gmp-native libmpc-native"
 
-KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT} \
- ${EXTRA_DTC_ARGS}"
+KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT} ${EXTRA_DTC_ARGS}"
 
 S = "${WORKDIR}/git"
 
 # 6.6 Mainline version
 SRCREV = "ffc253263a1375a65fa6c9f62a893e9767fbebfa"
-PV = "6.6+git"
+PV = "6.6"
 
-KERNEL_GIT_URI = 
"git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git"
-KERNEL_GIT_PROTOCOL = "https"
-KERNEL_GIT_BRANCH = "master"
-SRC_URI += " \
-   
${KERNEL_GIT_URI};protocol=${KERNEL_GIT_PROTOCOL};branch=${KERNEL_GIT_BRANCH} \
-"
+SRC_URI = 
"git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git;protocol=https;branch=master"
 
 DEFCONFIG_NAME = "multi_v7_defconfig"
 DEFCONFIG_NAME:omapl138 = "davinci_all_defconfig"
 DEFCONFIG_NAME:k3 = "defconfig"
 KERNEL_CONFIG_COMMAND = "oe_runmake -C ${S} O=${B} ${DEFCONFIG_NAME}"
-
-do_shared_workdir:prepend() {
-   cd ${B}
-   echo >> Module.symvers
-}
-
-FILES:${KERNEL_PACKAGE_NAME}-devicetree += "/${KERNEL_IMAGEDEST}/*.itb"
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-next_git.bb 
b/meta-ti-bsp/recipes-kernel/linux/linux-ti-next_git.bb
index f1a14ab1..3c206754 100644
--- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-next_git.bb
+++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-next_git.bb
@@ -1,26 +1,11 @@
-SECTION = "kernel"
-SUMMARY = "Linux-next kernel for TI devices"
-LICENSE = "GPL-2.0-only"
-LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
+require linux-ti-mainline_git.bb
 
-inherit kernel
+SUMMARY = "Linux-next kernel for TI devices"
 
-require recipes-kernel/linux/ti-kernel.inc
 include ${@ 'recipes-kernel/linux/ti-kernel-devicetree-prefix.inc' if 
d.getVar('KERNEL_DEVICETREE_PREFIX') else ''}
 
-DEPENDS += "gmp-native libmpc-native"
-
-KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT} ${EXTRA_DTC_ARGS}"
-
-S = "${WORKDIR}/git"
-
 # 6.6.0-rc3+ version
 SRCREV = "6465e260f48790807eef06b583b38ca9789b6072"
 PV = "6.6.0-rc3+git"
 
 SRC_URI = 
"git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git;protocol=https;branch=master"
-
-DEFCONFIG_NAME = "multi_v7_defconfig"
-DEFCONFIG_NAME:omapl138 = "davinci_all_defconfig"
-DEFCONFIG_NAME:k3 = "defconfig"
-KERNEL_CONFIG_COMMAND = "oe_runmake -C ${S} O=${B} ${DEFCONFIG_NAME}"
-- 
2.35.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17788): 
https://lists.yoctoproject.org/g/meta-ti/message/17788
Mute This Topic: https://lists.yoctoproject.org/mt/106791513/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master/scarthgap][PATCH] ti-rtos-metadata: remove

2024-06-20 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

The use of external metadata file to control RTOS binary firmware
integration has been deprecated some time ago. Remove it now.

Signed-off-by: Denys Dmytriyenko 
---
 .../recipes-ti/ti-rtos-bin/files/empty|  1 -
 .../ti-rtos-bin/ti-rtos-metadata.bb   | 47 ---
 2 files changed, 48 deletions(-)
 delete mode 100644 meta-ti-bsp/recipes-ti/ti-rtos-bin/files/empty
 delete mode 100644 meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb

diff --git a/meta-ti-bsp/recipes-ti/ti-rtos-bin/files/empty 
b/meta-ti-bsp/recipes-ti/ti-rtos-bin/files/empty
deleted file mode 100644
index c6cac692..
--- a/meta-ti-bsp/recipes-ti/ti-rtos-bin/files/empty
+++ /dev/null
@@ -1 +0,0 @@
-empty
diff --git a/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb 
b/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
deleted file mode 100644
index feee1cf9..
--- a/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
+++ /dev/null
@@ -1,47 +0,0 @@
-LICENSE = "BSD-3-Clause"
-LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/BSD-3-Clause;md5=550794465ba0ec5312d6919e203a55f9"
-
-COMPATIBLE_MACHINE = "j721e|j7200|am65xx|am64xx"
-
-PACKAGE_ARCH = "${MACHINE_ARCH}"
-
-INHIBIT_DEFAULT_DEPS = "1"
-
-inherit nopackages deploy
-
-PLAT_SFX = ""
-PLAT_SFX:j721e = "/j721e"
-PLAT_SFX:j7200 = "/j7200"
-PLAT_SFX:am65xx = "/am65xx"
-PLAT_SFX:am64xx = "/am64x"
-
-# Use weak assignment to set defaults to TI_RTOS_METADATA_* variables
-TI_RTOS_METADATA_URI ?= 
"git://git.ti.com/git/processor-sdk/coresdk_rtos_releases.git"
-TI_RTOS_METADATA_PROTOCOL ?= "https"
-TI_RTOS_METADATA_SRCREV ?= "2ecbf45af64bc47806623cc5bf7ab493489acaf9"
-TI_RTOS_METADATA_BRANCH ?= "master"
-TI_RTOS_METADATA_DIR ?= "${PLAT_SFX}"
-TI_RTOS_METADATA_FILE ?= "${S}${TI_RTOS_METADATA_DIR}/metadata.inc"
-TI_RTOS_METADATA_FILE:am64xx ?= 
"${S}${TI_RTOS_METADATA_DIR}/mcusdk_metadata.inc"
-
-PV = "1.0.0+git"
-
-S = "${WORKDIR}/git"
-
-SRC_URI = 
"${TI_RTOS_METADATA_URI};branch=${TI_RTOS_METADATA_BRANCH};protocol=${TI_RTOS_METADATA_PROTOCOL}"
-SRCREV = "${TI_RTOS_METADATA_SRCREV}"
-
-do_configure[noexec] = "1"
-do_compile[noexec] = "1"
-do_install[noexec] = "1"
-
-do_deploy () {
-   :
-}
-
-do_deploy:k3 () {
-   install -d ${DEPLOYDIR}
-   install -m 0644 ${TI_RTOS_METADATA_FILE} ${DEPLOYDIR}/
-}
-
-addtask deploy before do_build after do_compile
-- 
2.35.3


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17787): 
https://lists.yoctoproject.org/g/meta-ti/message/17787
Mute This Topic: https://lists.yoctoproject.org/mt/106791512/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [RFC][master/scarthgap][PATCH 4/4] cc33xx-target-scripts: add cc33xx scripts to control TI cc33xx WLAN device

2024-06-20 Thread Denys Dmytriyenko

On Wed, Jun 19, 2024 at 10:22:02PM -0500, Sabeeh Khan via 
lists.yoctoproject.org wrote:
> Add scripts and conf files to be used to control and configure
> the cc33xx WLAN device. Documentation for these scripts can be found here:
> https://www.ti.com/tool/CC33XX-SOFTWARE
> 
> Signed-off-by: Sabeeh Khan 
> ---
>  .../cc33xx-target-scripts.bb  | 22 +++
>  1 file changed, 22 insertions(+)
>  create mode 100644 
> meta-ti-extras/recipes-connectivity/cc33xx-target-scripts/cc33xx-target-scripts.bb
> 
> diff --git 
> a/meta-ti-extras/recipes-connectivity/cc33xx-target-scripts/cc33xx-target-scripts.bb
>  
> b/meta-ti-extras/recipes-connectivity/cc33xx-target-scripts/cc33xx-target-scripts.bb
> new file mode 100644
> index ..2f13f911
> --- /dev/null
> +++ 
> b/meta-ti-extras/recipes-connectivity/cc33xx-target-scripts/cc33xx-target-scripts.bb
> @@ -0,0 +1,22 @@
> +DESCRIPTION = "Scripts and configuration files for TI cc33xx wireless 
> drivers"

SUMMARY


> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=904443cf7fae5c09c3d5f83f8557c265"
> +
> +SRCREV = "4371c93ea01b339f6f73f77d6d6bfcc185def8c0"
> +BRANCH = "master"
> +SRC_URI = 
> "git://git.ti.com/git/cc33xx-wlan/cc33xx-target-scripts.git;protocol=https;branch=${BRANCH}
>  \
> +"
> +
> +S = "${WORKDIR}/git"
> +
> +FILES:${PN} += "${datadir}/cc33xx/"
> +
> +do_install() {
> + install -d ${D}${datadir}/cc33xx/
> +
> + scripts=`find ./* -type f -name "*.*"`

Is this find command necessary?


> + for s in $scripts
> + do
> + install -m 0755 $s ${D}${datadir}/cc33xx/
> + done
> +}
> -- 
> 2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17783): 
https://lists.yoctoproject.org/g/meta-ti/message/17783
Mute This Topic: https://lists.yoctoproject.org/mt/106774315/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [RFC][master/scarthgap][PATCH 2/4] cc33calibrator: add new cc33calibrator tool for cc33xx devices

2024-06-20 Thread Denys Dmytriyenko

On Wed, Jun 19, 2024 at 10:22:00PM -0500, Sabeeh Khan via 
lists.yoctoproject.org wrote:
> cc33calibrator is a tool provided by TI to manually control the
> radio frontend of the cc33xx device. This tool can also be used
> for production line testing of the radio.
> Documentation for this tool is provided within the following link:
> https://www.ti.com/tool/CC33XX-SOFTWARE
> 
> Signed-off-by: Sabeeh Khan 
> ---
>  .../cc33calibrator/cc33calibrator_git.bb  | 24 +++
>  1 file changed, 24 insertions(+)
>  create mode 100644 
> meta-ti-extras/recipes-connectivity/cc33calibrator/cc33calibrator_git.bb
> 
> diff --git 
> a/meta-ti-extras/recipes-connectivity/cc33calibrator/cc33calibrator_git.bb 
> b/meta-ti-extras/recipes-connectivity/cc33calibrator/cc33calibrator_git.bb
> new file mode 100644
> index ..da2d0453
> --- /dev/null
> +++ b/meta-ti-extras/recipes-connectivity/cc33calibrator/cc33calibrator_git.bb
> @@ -0,0 +1,24 @@
> +DESCRIPTION = "The calibrator utility for TI wireless solution based on 
> cc33xx driver"

SUMMARY


> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d5fc448a36efe573623542dcb989afc4"
> +
> +SRCREV = "a2f84140b8d67cfc94472cf92676a409d1e47d86"
> +SRC_URI = 
> "git://git.ti.com/git/cc33xx-wlan/cc33xx-utils.git;branch=master;protocol=https"
> +
> +PV = "1.0.0.50"
> +
> +DEPENDS = "libnl"
> +
> +S = "${WORKDIR}/git/cc33calibrator"
> +
> +export CROSS_COMPILE = "${TARGET_PREFIX}"
> +
> +EXTRA_OEMAKE = "CFLAGS="${CFLAGS} -I${STAGING_INCDIR}/libnl3/ 
> -DCONFIG_LIBNL32 " \
> + LDFLAGS="${LDFLAGS} -L${STAGING_LIBDIR}" \
> + CC="${CC}" \
> + NLVER=3"
> +
> +do_install() {
> +install -d ${D}${bindir}
> +install -m 0755 cc33calibrator ${D}${bindir}/
> +}
> -- 
> 2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17782): 
https://lists.yoctoproject.org/g/meta-ti/message/17782
Mute This Topic: https://lists.yoctoproject.org/mt/106774313/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [RFC][master/scarthgap][PATCH 1/4] cc33conf: add new cc33conf tool for cc33xx devices

2024-06-20 Thread Denys Dmytriyenko

On Wed, Jun 19, 2024 at 10:21:59PM -0500, Sabeeh Khan via 
lists.yoctoproject.org wrote:
> cc33conf is a tool provided by TI to configure
> cc33xx WLAN devices. It can be used to change
> the RF parameters and other features of the target.
> Documentation for this tool is provided within the following link:
> https://www.ti.com/tool/CC33XX-SOFTWARE
> 
> Signed-off-by: Sabeeh Khan 
> ---
>  .../cc33conf/cc33conf_git.bb  | 29 +++
>  1 file changed, 29 insertions(+)
>  create mode 100644 
> meta-ti-extras/recipes-connectivity/cc33conf/cc33conf_git.bb
> 
> diff --git a/meta-ti-extras/recipes-connectivity/cc33conf/cc33conf_git.bb 
> b/meta-ti-extras/recipes-connectivity/cc33conf/cc33conf_git.bb
> new file mode 100644
> index ..1e4faa77
> --- /dev/null
> +++ b/meta-ti-extras/recipes-connectivity/cc33conf/cc33conf_git.bb
> @@ -0,0 +1,29 @@
> +DESCRIPTION = "Configuration utility for TI CC33xx wireless devices"
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d5fc448a36efe573623542dcb989afc4"
> +
> +SRCREV = "a2f84140b8d67cfc94472cf92676a409d1e47d86"
> +SRC_URI = 
> "git://git.ti.com/git/cc33xx-wlan/cc33xx-utils.git;branch=master;protocol=https"
> +
> +PV = "1.7.0.120"
> +
> +S = "${WORKDIR}/git/cc33conf"
> +
> +EXTRA_OEMAKE = "CC="${CC}""
> +
> +do_install() {
> + install -d ${D}${sbindir}
> + install -d ${D}${sbindir}/cc33conf/
> +
> + install -m 0755 cc33xxconf ${D}${sbindir}/cc33conf/
> + install -m 0755 dictionary.txt ${D}${sbindir}/cc33conf/
> + install -m 0755 default.conf ${D}${sbindir}/cc33conf/
> + install -m 0755 README ${D}${sbindir}/cc33conf/
> + install -m 0755 cc33xx-conf.conf ${D}${sbindir}/cc33conf/
> + install -m 0755 cc33xx-conf.ini ${D}${sbindir}/cc33conf/
> + install -m 0755 conf.h ${D}${sbindir}/cc33conf/

Should all these files really go into sbindir?


> +}
> +
> +FILES:${PN} += " \
> + ${sbindir}/cc33conf \
> +"
> -- 
> 2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17781): 
https://lists.yoctoproject.org/g/meta-ti/message/17781
Mute This Topic: https://lists.yoctoproject.org/mt/106774312/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-ti] [RFC][master/scarthgap][PATCH 3/4] cc33xx-fw: install cc33xx firmware

2024-06-20 Thread Denys Dmytriyenko

On Wed, Jun 19, 2024 at 10:22:01PM -0500, Sabeeh Khan via 
lists.yoctoproject.org wrote:
> Download and install the cc33xx firmware and binaries
> to be used with the cc33xx drivers.
> 
> FW Version: 1.7.0.120
> 
> Signed-off-by: Sabeeh Khan 
> ---
>  .../recipes-bsp/cc33xx-fw/cc33xx-fw_git.bb| 26 +++
>  1 file changed, 26 insertions(+)
>  create mode 100644 meta-ti-extras/recipes-bsp/cc33xx-fw/cc33xx-fw_git.bb
> 
> diff --git a/meta-ti-extras/recipes-bsp/cc33xx-fw/cc33xx-fw_git.bb 
> b/meta-ti-extras/recipes-bsp/cc33xx-fw/cc33xx-fw_git.bb
> new file mode 100644
> index ..152e3501
> --- /dev/null
> +++ b/meta-ti-extras/recipes-bsp/cc33xx-fw/cc33xx-fw_git.bb
> @@ -0,0 +1,26 @@
> +DESCRIPTION = "Firmware files for use with TI cc33xx"
> +LICENSE = "TI-TSPA"
> +LIC_FILES_CHKSUM = "file://LICENCE;md5=df68504cbd0a4da1643ebcfd5783dbc9"
> +
> +SRC_URI = " \
> + 
> git://git.ti.com/git/cc33xx-wlan/cc33xx-fw.git;protocol=https;branch=${BRANCH}
>  
> +"
> +
> +PV = "1.7.0.120"
> +
> +SRCREV = "988ded3a7d4d0e46de62e9ebfcb685c502bd9edf"
> +BRANCH = "master"
> +
> +CLEANBROKEN = "1"
> +
> +S = "${WORKDIR}/git"
> +
> +do_compile() {
> +:
> +}

do_compile[noexec] = "1"


> +do_install() {
> +oe_runmake 'DEST_DIR=${D}' install
> +}
> +
> +FILES:${PN} = "${nonarch_base_libdir}/firmware/ti-connectivity/*"
> -- 
> 2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17779): 
https://lists.yoctoproject.org/g/meta-ti/message/17779
Mute This Topic: https://lists.yoctoproject.org/mt/106774314/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master/scarthgap][PATCH 1/2] beaglebone-ai64: BB.org does not support all SR and HS variants

2024-06-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Adjust IMAGE_BOOT_FILES list as BB.org BSP does not support all combinations
of SR1.1, SR2.0, HS-FS and HS-SE variants, same as J721e EVM in mainline.

Signed-off-by: Denys Dmytriyenko 
---
 meta-ti-bsp/conf/machine/beaglebone-ai64.conf | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf 
b/meta-ti-bsp/conf/machine/beaglebone-ai64.conf
index 2d681827..56e1ed4e 100644
--- a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf
+++ b/meta-ti-bsp/conf/machine/beaglebone-ai64.conf
@@ -6,6 +6,9 @@ TI_PREFERRED_BSP ?= "bb_org"
 
 require conf/machine/include/j721e.inc
 
+IMAGE_SR1_1_HS_FS_FILES:bsp-bb_org = ""
+IMAGE_SR2_HS_SE_FILES:bsp-bb_org = ""
+
 UBOOT_MACHINE = "j721e_evm_a72_config"
 UBOOT_MACHINE:bsp-ti-6_6 = "j721e_beagleboneai64_a72_defconfig"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17763): 
https://lists.yoctoproject.org/g/meta-ti/message/17763
Mute This Topic: https://lists.yoctoproject.org/mt/106748014/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[meta-ti] [master/scarthgap][PATCH 2/2] j7200: mainline BSP doesn't support all SR and HS variants

2024-06-18 Thread Denys Dmytriyenko

From: Denys Dmytriyenko 

Adjust IMAGE_BOOT_FILES list as mainline BSP does not support all combinations
of SR1.0, SR2.0, HS-FS and HS-SE variants.

Suggested-by: Aniket Limaye 
Signed-off-by: Denys Dmytriyenko 
---
 meta-ti-bsp/conf/machine/include/j7200.inc | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta-ti-bsp/conf/machine/include/j7200.inc 
b/meta-ti-bsp/conf/machine/include/j7200.inc
index caa79876..2a11e3dd 100644
--- a/meta-ti-bsp/conf/machine/include/j7200.inc
+++ b/meta-ti-bsp/conf/machine/include/j7200.inc
@@ -5,10 +5,14 @@ SOC_FAMILY:append = ":j7200"
 IMAGE_BOOT_FILES += "tiboot3-j7200-gp-evm.bin"
 
 # Since default tiboot3.bin on J7200 is for GP, add a version for SR1.0 HS-FS
-IMAGE_BOOT_FILES += "tiboot3-j7200-hs-fs-evm.bin"
+IMAGE_SR1_HS_FS_FILES = "tiboot3-j7200-hs-fs-evm.bin"
+IMAGE_SR1_HS_FS_FILES:bsp-mainline = ""
+IMAGE_BOOT_FILES += "${IMAGE_SR1_HS_FS_FILES}"
 
 # Since default tiboot3.bin on J7200 is for GP, add a version for SR1.0 HS-SE
-IMAGE_BOOT_FILES += "tiboot3-j7200-hs-evm.bin"
+IMAGE_SR1_HS_SE_FILES = "tiboot3-j7200-hs-evm.bin"
+IMAGE_SR1_HS_SE_FILES:bsp-mainline = ""
+IMAGE_BOOT_FILES += "${IMAGE_SR1_HS_SE_FILES}"
 
 # Since default tiboot3.bin on J7200 is for GP, add a version for SR2.0 HS-FS
 IMAGE_BOOT_FILES += "tiboot3-j7200_sr2-hs-fs-evm.bin"
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17764): 
https://lists.yoctoproject.org/g/meta-ti/message/17764
Mute This Topic: https://lists.yoctoproject.org/mt/106748016/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 1073 matches

Mail list logo