All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Brandon Brnich <b-brnich@ti.com>,
	meta-arago@lists.yoctoproject.org,
	Darren Etheridge <detheridge@ti.com>
Subject: Re: [meta-arago][master][PATCH] ti-test: Add Required Multimedia Packages to ti-test
Date: Thu, 26 Feb 2026 17:22:58 -0500	[thread overview]
Message-ID: <20260226222258.GE11121@denix.org> (raw)
In-Reply-To: <60f134bd-9981-4c2d-ae95-e35c9a5bd5d0@ti.com>

On Wed, Feb 25, 2026 at 02:04:30PM -0600, Ryan Eatmon via lists.yoctoproject.org wrote:
> 
> 
> On 2/25/2026 1:03 PM, Brandon Brnich wrote:
> >FFMPEG and MPV are required during automated testing. Explicitly add
> >these to ti-test.
> >
> >Signed-off-by: Brandon Brnich <b-brnich@ti.com>
> >---
> >  meta-arago-test/recipes-core/packagegroups/ti-test.bb | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> >
> >diff --git a/meta-arago-test/recipes-core/packagegroups/ti-test.bb b/meta-arago-test/recipes-core/packagegroups/ti-test.bb
> >index f2ae1aef..c694545d 100644
> >--- a/meta-arago-test/recipes-core/packagegroups/ti-test.bb
> >+++ b/meta-arago-test/recipes-core/packagegroups/ti-test.bb
> >@@ -16,6 +16,7 @@ TI_TEST_BASE = "\
> >      dosfstools \
> >      ethtool \
> >      evtest \
> >+    ffmpeg \
> 
> This might be a problem... there are licensing issues related to
> ffmpeg that we address in meta-arago-distro, but moving this to
> meta-arago-test (a layer that *should* be able to be stand alone) is
> going to cause issues.
> 
> Denys,
> 
> Any ideas on how to address this?

So, we already explicitly include ffmpeg and mpv in the multimedia 
packagegroup in meta-arago-distro. Since ffmpeg and libav may include some 
codecs with questionable patent statuses, they are marked as "commercial" 
and need to be allowed explicitly, which we do in arago.conf with the 
corresponding LICENSE_FLAGS_ACCEPTED. That simply allows building those 
packages, but whether the corresponding codecs are enabled or not is 
determined by their PACKAGECONFIGs.

https://git.yoctoproject.org/meta-arago/tree/meta-arago-distro/conf/distro/arago.conf#n149
https://docs.yoctoproject.org/dev-manual/licenses.html#enabling-commercially-licensed-recipes

And I'd think for meta-arago-test layer it would be even easier, as it is not 
expected to be used for production. And we can set LICENSE_FLAGS_ACCEPTED in 
its layer.conf to make it work with other Distros besides Arago.


> >      fio \
> >      git \
> >      gst-devtools \
> >@@ -36,6 +37,7 @@ TI_TEST_BASE = "\
> >      lsof \
> >      media-ctl \
> >      memtester \
> >+    mpv \
> >      mstpd \
> >      mtd-utils \
> >      mtd-utils-ubifs \
> >@@ -145,7 +147,7 @@ TI_TEST_TI_TOOLS:append:am65xx   = " \
> >  "
> >  # Disable due to breakage
> >-#    viddec-test-app
> >+#    viddec-test-app
> >  TI_TEST_TI_TOOLS:append:j721e = " \
> >      pru-icss \
> >      ufs-utils \


      reply	other threads:[~2026-02-26 22:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 19:03 [meta-arago][master][PATCH] ti-test: Add Required Multimedia Packages to ti-test Brandon Brnich
2026-02-25 19:16 ` PRC Automation
2026-02-25 19:57 ` Denys Dmytriyenko
2026-02-25 19:58   ` Brandon Brnich
2026-02-26 15:34     ` Andrew Davis
2026-02-25 20:04 ` Ryan Eatmon
2026-02-26 22:22   ` Denys Dmytriyenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260226222258.GE11121@denix.org \
    --to=denis@denix.org \
    --cc=b-brnich@ti.com \
    --cc=detheridge@ti.com \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.