[meta-arago,master,v2] meta-arago-test: recipes-core: Add udev rules for MCAN to meta-arago-test

Move udev rules from meta-arago-distro to meta-arago-test so that MCAN tests
run successfully with other distros such as "poky" as well.

Signed-off-by: Anurag Dutta <a-dutta@ti.com>
---

Link to v1 : https://lore.kernel.org/all/20260106060815.868724-1-a-dutta@ti.com/

Changelog: v2:
1. moved all the rules from meta-arago-distro to meta-arago-test
2. removed udev* from meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb

 .../recipes-core/packagegroups/packagegroup-arago-base.bb       | 2 --
 meta-arago-test/recipes-core/packagegroups/ti-test.bb           | 1 +
 .../recipes-core/udev/udev-aragoconf/37-can-am62.rules          | 0
 .../recipes-core/udev/udev-aragoconf/37-can-dra7.rules          | 0
 .../recipes-core/udev/udev-aragoconf/37-can-j7.rules            | 0
 .../recipes-core/udev/udev-aragoconf/37-can-ti33x.rules         | 0
 .../recipes-core/udev/udev-aragoconf/50-arago.rules             | 0
 .../recipes-core/udev/udev-aragoconf_1.bb                       | 0
 8 files changed, 1 insertion(+), 2 deletions(-)
 rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf/37-can-am62.rules (100%)
 rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf/37-can-dra7.rules (100%)
 rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf/37-can-j7.rules (100%)
 rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf/37-can-ti33x.rules (100%)
 rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf/50-arago.rules (100%)
 rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf_1.bb (100%)

meta-arago / na / 20260107052154.1598698-1-a-dutta

PRC Results: PASS

=========================================================
  check-yocto-patches: PASS
=========================================================
Patches
----------------------------------------
WARN - [meta-arago][master][PATCH v2] meta-arago-test: recipes-core: Add udev rules for MCAN to meta-arago-test
    WARN: Commit message does not include file/recipe name: meta-arago-test: recipes-core: Add udev rules for MCAN to meta-arago-test. (COMMIT-MESSAGE-2)
        patch
    
    WARN: Commit message should not include directory path to recipe: meta-arago-test: recipes-core: Add udev rules for MCAN to meta-arago-test.
              meta-arago-test
              recipes-core (COMMIT-MESSAGE-3)
        patch
    
    For details on the above errors/warnings visit: https://lists.yoctoproject.org/g/meta-ti/wiki/40887



=========================================================
  apply-yocto-patch: PASS
=========================================================
master
=====================
Summary:
- Patch Series: [meta-arago][master][PATCH v2] meta-arago-test: recipes-core: Add udev rules for MCAN to meta-arago-test
- Submitter: From: Anurag Dutta <a-dutta@ti.com>
- Date: Date: Wed, 7 Jan 2026 10:51:54 +0530
- Num Patches: 1
- Mailing List (public inbox) Commit SHA: d8dc6a7e3484ef941a32505b838788839186b8dc

Applied to:
- Repository: lcpd-prc-meta-arago
- Base Branch: master-wip
- Commit Author: Ryan Eatmon <reatmon@ti.com>
- Commit Subject: libdrm: Remove upstreamed patch
- Commit SHA: 8c190b1e4f6a53ea641ba9d6150ef873f561c706

Patches
----------------------------------------
All patches applied



=========================================================
  check-yocto-repo: PASS
=========================================================
master
=====================
PASS



=========================================================
  yocto-check-layers: PASS
=========================================================
master - PASS
=====================
All checks passed

On 1/6/2026 11:21 PM, Anurag Dutta wrote:
> Move udev rules from meta-arago-distro to meta-arago-test so that MCAN tests
> run successfully with other distros such as "poky" as well.

If these rules should be available for other distros, then I feel like 
this should move to meta-ti.  Well, everything except for the arago 
rules which seem like they are distro specific and not hardware 
specific.  You might be able to use the MACHINE_EXTRA_RDEPENDS variable 
in each of the impacted platforms to ensure that new recipe in meta-ti 
is included in all images.

Denys, thoughts?


> 
> Signed-off-by: Anurag Dutta <a-dutta@ti.com>
> ---
> 
> Link to v1 : https://lore.kernel.org/all/20260106060815.868724-1-a-dutta@ti.com/
> 
> Changelog: v2:
> 1. moved all the rules from meta-arago-distro to meta-arago-test
> 2. removed udev* from meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb
> 
>   .../recipes-core/packagegroups/packagegroup-arago-base.bb       | 2 --
>   meta-arago-test/recipes-core/packagegroups/ti-test.bb           | 1 +
>   .../recipes-core/udev/udev-aragoconf/37-can-am62.rules          | 0
>   .../recipes-core/udev/udev-aragoconf/37-can-dra7.rules          | 0
>   .../recipes-core/udev/udev-aragoconf/37-can-j7.rules            | 0
>   .../recipes-core/udev/udev-aragoconf/37-can-ti33x.rules         | 0
>   .../recipes-core/udev/udev-aragoconf/50-arago.rules             | 0
>   .../recipes-core/udev/udev-aragoconf_1.bb                       | 0
>   8 files changed, 1 insertion(+), 2 deletions(-)
>   rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf/37-can-am62.rules (100%)
>   rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf/37-can-dra7.rules (100%)
>   rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf/37-can-j7.rules (100%)
>   rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf/37-can-ti33x.rules (100%)
>   rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf/50-arago.rules (100%)
>   rename {meta-arago-distro => meta-arago-test}/recipes-core/udev/udev-aragoconf_1.bb (100%)
> 
> diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb
> index b80697e5..6df03e60 100644
> --- a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb
> +++ b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb
> @@ -21,8 +21,6 @@ ARAGO_BASE = "\
>       ethtool \
>       bash \
>       opkg-bash-completion \
> -    udev-extraconf \
> -    udev-aragoconf \
>       libgpiod \
>       libgpiod-tools \
>   "
> diff --git a/meta-arago-test/recipes-core/packagegroups/ti-test.bb b/meta-arago-test/recipes-core/packagegroups/ti-test.bb
> index dad5571c..47f8fcac 100644
> --- a/meta-arago-test/recipes-core/packagegroups/ti-test.bb
> +++ b/meta-arago-test/recipes-core/packagegroups/ti-test.bb
> @@ -104,6 +104,7 @@ TI_TEST_TI_TOOLS = " \
>       input-utils \
>       ltp-ddt \
>       openssl-perf \
> +    udev-aragoconf \
>       uvc-gadget \
>   "
>   
> diff --git a/meta-arago-distro/recipes-core/udev/udev-aragoconf/37-can-am62.rules b/meta-arago-test/recipes-core/udev/udev-aragoconf/37-can-am62.rules
> similarity index 100%
> rename from meta-arago-distro/recipes-core/udev/udev-aragoconf/37-can-am62.rules
> rename to meta-arago-test/recipes-core/udev/udev-aragoconf/37-can-am62.rules
> diff --git a/meta-arago-distro/recipes-core/udev/udev-aragoconf/37-can-dra7.rules b/meta-arago-test/recipes-core/udev/udev-aragoconf/37-can-dra7.rules
> similarity index 100%
> rename from meta-arago-distro/recipes-core/udev/udev-aragoconf/37-can-dra7.rules
> rename to meta-arago-test/recipes-core/udev/udev-aragoconf/37-can-dra7.rules
> diff --git a/meta-arago-distro/recipes-core/udev/udev-aragoconf/37-can-j7.rules b/meta-arago-test/recipes-core/udev/udev-aragoconf/37-can-j7.rules
> similarity index 100%
> rename from meta-arago-distro/recipes-core/udev/udev-aragoconf/37-can-j7.rules
> rename to meta-arago-test/recipes-core/udev/udev-aragoconf/37-can-j7.rules
> diff --git a/meta-arago-distro/recipes-core/udev/udev-aragoconf/37-can-ti33x.rules b/meta-arago-test/recipes-core/udev/udev-aragoconf/37-can-ti33x.rules
> similarity index 100%
> rename from meta-arago-distro/recipes-core/udev/udev-aragoconf/37-can-ti33x.rules
> rename to meta-arago-test/recipes-core/udev/udev-aragoconf/37-can-ti33x.rules
> diff --git a/meta-arago-distro/recipes-core/udev/udev-aragoconf/50-arago.rules b/meta-arago-test/recipes-core/udev/udev-aragoconf/50-arago.rules
> similarity index 100%
> rename from meta-arago-distro/recipes-core/udev/udev-aragoconf/50-arago.rules
> rename to meta-arago-test/recipes-core/udev/udev-aragoconf/50-arago.rules
> diff --git a/meta-arago-distro/recipes-core/udev/udev-aragoconf_1.bb b/meta-arago-test/recipes-core/udev/udev-aragoconf_1.bb
> similarity index 100%
> rename from meta-arago-distro/recipes-core/udev/udev-aragoconf_1.bb
> rename to meta-arago-test/recipes-core/udev/udev-aragoconf_1.bb

On Wed, Jan 07, 2026 at 06:33:47AM -0600, Ryan Eatmon via lists.yoctoproject.org wrote:
> 
> On 1/6/2026 11:21 PM, Anurag Dutta wrote:
> >Move udev rules from meta-arago-distro to meta-arago-test so that MCAN tests
> >run successfully with other distros such as "poky" as well.
> 
> If these rules should be available for other distros, then I feel
> like this should move to meta-ti.  Well, everything except for the
> arago rules which seem like they are distro specific and not
> hardware specific.  You might be able to use the
> MACHINE_EXTRA_RDEPENDS variable in each of the impacted platforms to
> ensure that new recipe in meta-ti is included in all images.
> 
> Denys, thoughts?

Had to do some digging to untangle many changes over the years...

First of all, 50-arago.rules is a simple SD card automount back from when 
there were none. These days systemd does that automatically, I believe - 
I wonder if we still need to keep it in Arago for sysvinit use case?

As of the CAN rules - those rules are for persistent naming of corresponding 
device nodes, so seem useful even outside of testing. Hence I agree with Ryan 
those rules may be moved to meta-ti-bsp.

MACHINE_ESSENTIAL_EXTRA_RDEPENDS and MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS are 
the 2 variables that can be used to automatically pull in packages to images. 
The first is a list of REQUIRED packages to boot the platform, usually kernel 
images, device trees, etc. The second lists RECOMMENDED packages to get full 
functionality from the platform, but not necessarily required to just boot it. 
Things like firmware images, etc. Which is a better fit for this.

That said, these are udev rules and will only work when dev-manager is udev 
(either systemd or sysvinit), but not mdev, I believe. So, if anyone is using 
meta-ti in that configuration, the functionality won't change, they'll just 
get unused rules...