From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtpcmd0872.aruba.it (smtpcmd0872.aruba.it [62.149.156.72]) by mx.groups.io with SMTP id smtpd.web10.8738.1614242444592707318 for ; Thu, 25 Feb 2021 00:40:46 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@aruba.it header.s=a1 header.b=aPivdtPC; spf=none, err=permanent DNS error (domain: faresoftware.it, ip: 62.149.156.72, mailfrom: mauro@faresoftware.it) Received: from [10.0.3.95] ([213.213.6.58]) by Aruba Outgoing Smtp with ESMTPSA id FCCOlsZceHTbyFCCOloESs; Thu, 25 Feb 2021 09:40:42 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aruba.it; s=a1; t=1614242443; bh=1vFqQ8/DCon+ZDYz13EtXyCNY2ZT5fthfv8qLyBLbTo=; h=To:From:Subject:Date:MIME-Version:Content-Type; b=aPivdtPCqr5qKMnfn2mraDqcEBDL1GJeMJGsUyOjyuKvaj2WairvqIN7RtXYSKx2P HgEJJI6eW7+2WhUf3o/VFgJcQvyB4GilulMVidJBQQInqmE0d/nXir3ynYxlUszTai u3NPtsM5kDpuJsKtWyLd5t+QlWQM1qJWLoxvELzNXr4Rp4rDEoW/Yc1LOCyA2HFJQn JrzPiSYh1AJCyYjc1JoT8FYaR10cDqoiu3QEQnLOCnnmBEMZDDNZgI6IW2pDg+cBiG XQ8gqtm+Uw43+tarBNWCaPQMl1ZNlt5M+7VYYDW3VqgNZ+9Ykkp6fpNPQULuwkTnzZ yMHylsxZvNFRA== To: "meta-freescale@lists.yoctoproject.org" From: "Mauro Ziliani" Subject: imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx? Message-ID: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it> Date: Thu, 25 Feb 2021 09:40:35 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 X-CMAE-Envelope: MS4wfOhSP7fp3d27dH+wujnRO6fbpSD/w1VIL3UBIsba6fDUIgD/CweiOAzf0EYJEL1GU6DnLl5rD2DNl12v/TNkzZIkfdlxnTuWs5BVO55y43Y+/4IPnHXo mSO/XMdg1YNp5bb9LuCS3eTYowmoM7egoSGpsHO8vwEQhgq6YHx/eqQcIpvAsL30uaMVOQJ7rtSa4A== Content-Type: multipart/alternative; boundary="------------194F62046336E2CC9DB5102F" Content-Language: en-US --------------194F62046336E2CC9DB5102F Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: 8bit Hi all. I'm porting and old system based on Krogoth to Dunfell. In Krogoth the kernel was linux-imx. Now in Dunfell which is the right kernel? linux-fslc o linux-fslc-imx? Thanks all    MZ --------------194F62046336E2CC9DB5102F Content-Type: text/html; charset=iso-8859-15 Content-Transfer-Encoding: 8bit

Hi all.

I'm porting and old system based on Krogoth to Dunfell.

In Krogoth the kernel was linux-imx.

Now in Dunfell which is the right kernel?

linux-fslc o linux-fslc-imx?


Thanks all

   MZ

--------------194F62046336E2CC9DB5102F-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) by mx.groups.io with SMTP id smtpd.web12.8934.1614242880344345482 for ; Thu, 25 Feb 2021 00:48:00 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=EunkkwjX; spf=pass (domain: gmail.com, ip: 209.85.208.182, mailfrom: andrey.z@gmail.com) Received: by mail-lj1-f182.google.com with SMTP id q14so5562716ljp.4 for ; Thu, 25 Feb 2021 00:47:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=H1fsXrMJfr4zojt60IXcOEBa6dGD97lYVAW5FKzTwIY=; b=EunkkwjXLf+s3FsEuZ6LH5qphGvHfFuWUmQENZbXjrroogZN7ITO+dQ1HLAJP854DN XmW20JVB6fsjHJvRQpElEnajVoVFm+KP+6KHuC3omFD7+AxM8poVU3RlKKaFxF5kgeMd K08B6++vipKzjJOtsc9CkCPvAdECGT8m+S+aiMUJ748mTgy6gXBJXiM3cR7cVMFXwMJ4 STYkqoss+lyrZF4HySzJykqD644VmwCQ4BFUieqzzMTq1UjboKkynewe/Nk6cwraB4yn rVfFZ7HXDyxdLx8HbSOK5Mc734gLL6R8fWqWx0aggNkElBL5O1yr7j9+4q1WCZgOlqjx Ez9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=H1fsXrMJfr4zojt60IXcOEBa6dGD97lYVAW5FKzTwIY=; b=dlOgVT7pitREzaKVm8583Oh05x4c2YROdLHjxEN0dsHoV0RSj5mv64nBgbprUsjicI Jmt2dXKf+Nx4fAotjkLihEjgrlH94LQWdsD8ukhKSrcwkLdc5Kfp0Sv9DrkZ/G5Wqiwf Hx65h6PixAgCv8u26OudZ/1w79HdPQa2qv1EaGASc+YtBLv8/QTPlTI3lzrhIpmSaD2S Sw2gSLkBUuloSbcV0+uAp0QqsoUd2d5iXj17n773r/nP1PExipNizElz1GWsDORB3uAn HW15cl6Pd6bm2tkfQ4fooiGmbForSrDrgTqkjcNLYkmhFRxjORw6WClDZHSX2Y/RATe7 HIEQ== X-Gm-Message-State: AOAM533vgTTPx22//oZGdrOc3tC5gxd7GRjdApOusN6+U1zdY0inNT7n vWjCyffoqIpSI6DEzLhqmD6mZdsC2JZjGYqx33M= X-Google-Smtp-Source: ABdhPJy/T2GuRGSW9CPP++k1uQAVNfIHFXfdyZqA54jIcDNGZL8hk9IPt8vW6mLGdUTEy8Jq4ppY5xUhyFhsqWUrCSc= X-Received: by 2002:a2e:9196:: with SMTP id f22mr1022727ljg.419.1614242878111; Thu, 25 Feb 2021 00:47:58 -0800 (PST) MIME-Version: 1.0 References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it> In-Reply-To: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it> From: "Andrey Zhizhikin" Date: Thu, 25 Feb 2021 09:47:46 +0100 Message-ID: Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx? To: Mauro Ziliani Cc: "meta-freescale@lists.yoctoproject.org" Content-Type: text/plain; charset="UTF-8" Hello Mauro, On Thu, Feb 25, 2021 at 9:40 AM Mauro Ziliani wrote: > > Hi all. > > I'm porting and old system based on Krogoth to Dunfell. > > In Krogoth the kernel was linux-imx. > > Now in Dunfell which is the right kernel? Depends on what you define as "right". :) If you build any`fsl-` distro, then you should use either `linux-imx` of `linux-fslc-imx` kernel. If you rather opt for any of `fslc-` distro, then the kernel provider would be set to `linux-fslc`. > > linux-fslc o linux-fslc-imx? - `linux-fslc` is an upstream kernel (from stable korg), which has few patches not upstreamed yet - `linux-fslc-imx` is NXP kernel with latest patch level applied from stable korg. This is based on the NXP release (2.1.0 in [dunfell]), and then maintained in terms of security fixes applied in LTS branch. - `linux-imx` is a "pure" NXP kernel, which is provided as a part of their release(s). Current NXP release version present on the [dunfell] branch is 2.1.0 > > > Thanks all > > MZ > > -- Regards, Andrey. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailgate1.beam.ltd.uk (mailgate1.beam.ltd.uk [88.96.138.49]) by mx.groups.io with SMTP id smtpd.web09.8886.1614243659415389660 for ; Thu, 25 Feb 2021 01:01:00 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: beam.ltd.uk, ip: 88.96.138.49, mailfrom: terry@beam.ltd.uk) Received: from study.kingnet (king.kingnet [82.69.10.222]) by mailgate1.beam.ltd.uk (Postfix) with ESMTPSA id 523B46A1BB1 for ; Thu, 25 Feb 2021 09:00:54 +0000 (GMT) Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx? To: meta-freescale@lists.yoctoproject.org References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it> From: "Terry Barnaby" Message-ID: <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> Date: Thu, 25 Feb 2021 09:00:53 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE, NICE_REPLY_A autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on portal.beamnet Content-Type: multipart/alternative; boundary="------------D3DF96773B901B84609BCBAF" Content-Language: en-GB --------------D3DF96773B901B84609BCBAF Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 25/02/2021 08:47, Andrey Zhizhikin wrote: > Hello Mauro, > > On Thu, Feb 25, 2021 at 9:40 AM Mauro Ziliani wrote: >> Hi all. >> >> I'm porting and old system based on Krogoth to Dunfell. >> >> In Krogoth the kernel was linux-imx. >> >> Now in Dunfell which is the right kernel? > Depends on what you define as "right". :) > > If you build any`fsl-` distro, then you should use either `linux-imx` > of `linux-fslc-imx` kernel. If you rather opt for any of `fslc-` > distro, then the kernel provider would be set to `linux-fslc`. > >> linux-fslc o linux-fslc-imx? > - `linux-fslc` is an upstream kernel (from stable korg), which has few > patches not upstreamed yet > - `linux-fslc-imx` is NXP kernel with latest patch level applied from > stable korg. This is based on the NXP release (2.1.0 in [dunfell]), > and then maintained in terms of security fixes applied in LTS branch. > - `linux-imx` is a "pure" NXP kernel, which is provided as a part of > their release(s). Current NXP release version present on the [dunfell] > branch is 2.1.0 > >> >> Thanks all >> >> MZ >> >> > > > For a novice to NXP Freescale builds, what setup would you recommend as a basic test Yocto build for a Wandboard IMX6 dual lite system in order to test the performance of the hardware video processing system using gstreamer*imx (VPU etc) ? Would fslc-x11 or fslc-xwayland distro with the linux-fslc-imx kernel be the best approach or would some fsl-* distro with the linux-imx kernel be the best approach ? The standard Wandboard build uses linux-fslc which does not seem to support the imx hardware features and so I am trying to build a suitable test platform but having no luck trying various build combinations that either wont build or wont run properly in various ways, so any pointers would be gratefully received ! Terry --------------D3DF96773B901B84609BCBAF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
On 25/02/2021 08:47, Andrey Zhizhikin wrote:
Hello Mauro,

On Thu, Feb 25, 2021 at 9:40 AM Mauro Ziliani <mauro@faresoftware.it> wrote:

Hi all.

I'm porting and old system based on Krogoth to Dunfell.

In Krogoth the kernel was linux-imx.

Now in Dunfell which is the right kernel?

Depends on what you define as "right". :)

If you build any`fsl-` distro, then you should use either `linux-imx`
of `linux-fslc-imx` kernel. If you rather opt for any of `fslc-`
distro, then the kernel provider would be set to `linux-fslc`.


linux-fslc o linux-fslc-imx?

- `linux-fslc` is an upstream kernel (from stable korg), which has few
patches not upstreamed yet
- `linux-fslc-imx` is NXP kernel with latest patch level applied from
stable korg. This is based on the NXP release (2.1.0 in [dunfell]),
and then maintained in terms of security fixes applied in LTS branch.
- `linux-imx` is a "pure" NXP kernel, which is provided as a part of
their release(s). Current NXP release version present on the [dunfell]
branch is 2.1.0



Thanks all

   MZ




      

      

      




    

    
For a novice to NXP Freescale builds, what setup would you
      recommend as a basic test Yocto build for a Wandboard IMX6 dual
      lite system in order to test the performance of the hardware video
      processing system using gstreamer*imx (VPU etc) ?

    
Would fslc-x11 or fslc-xwayland distro with the linux-fslc-imx
      kernel be the best approach or would some fsl-* distro with the
      linux-imx kernel be the best approach ?

    
The standard Wandboard build uses linux-fslc which does not seem
      to support the imx hardware features and so I am trying to build a
      suitable test platform but having no luck trying various build
      combinations that either wont build or wont run properly in
      various ways, so any pointers would be gratefully received !

    
Terry

    

  


--------------D3DF96773B901B84609BCBAF--

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45])
 by mx.groups.io with SMTP id smtpd.web12.9270.1614245390417894404
 for ;
 Thu, 25 Feb 2021 01:29:50 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=IW8HtXT3;
 spf=pass (domain: gmail.com, ip: 209.85.167.45, mailfrom: andrey.z@gmail.com)
Received: by mail-lf1-f45.google.com with SMTP id m22so7558193lfg.5
        for ; Thu, 25 Feb 2021 01:29:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc:content-transfer-encoding;
        bh=MvuVGoia06KRLKF/K2WC9uqvip+I35giOeq9HpGJw6Q=;
        b=IW8HtXT3liMZghuVOVu+1O3UCCppIZJBeW1tFKpJpU1r/KOSTke8gzZyv1QkhiwC+c
         TfpOcGOCn9U/93yxJyQ83p7TTk52M/N95/DI5gDFO8KeMFAoE7E+OkgkiH4vmJGh4hKA
         wQD4GzOhQ/JjMJoqfwtkLM0MbggJUwMRxg1R7UbXiR49vgDl3p93hOzrXuEbf+1d9bqg
         LtJak+sKymEEmCbIL4UWTejjLCjqskGG78Q/1ntuwPxF4XNqD7JD8RATVdLwkipXB29c
         Ca8GrR6k95r3VYVeIkMYWuK9MRQCoaG3MMmGi7gjpUMXGQiGZZMoxJeZ/YhiChe3teiu
         3PNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc:content-transfer-encoding;
        bh=MvuVGoia06KRLKF/K2WC9uqvip+I35giOeq9HpGJw6Q=;
        b=FyFisUQVX3meQsV1NiqRZQ+79y5pznaUIDTJMnTgwQToibEQY7rIQEHEbPNopVMBlJ
         HjRtPOjKFTml52Via4DGzc6ue4ogjUU0ys1VvAauyZj/0zkc8G5ELmAYXeT9NsaWAkEI
         quuYTAbCg1c+5IyuniPTKlg5SIjFBFxqoDF2pOK7/4EiekNMG92WlAe8doXGTm0gFE44
         3pxzLCJnFs2PUDlOEQGBj5kn5kVkyui9pvY8GqM7esYTdBFuswjJw0WQ+6pP2zYHusAY
         YwFmcbrU4LaNLFsApgHxagXVqqHfW3/LkcuSp5pxg2BHF03kvMV8EKNWgoVaYjDcRAgO
         FlVg==
X-Gm-Message-State: AOAM530jT+inTgAi6dsDO1OrCerMmiML0AgpMbPqJVVZqWtPqONESMEJ
	BRZ9IBHez3taZoJD36X5qPWUoRxwGGlVUuQzcZc=
X-Google-Smtp-Source: ABdhPJxqM47t1Mogls37u+qB4bHfLrT9HXOxyc1Iy7o57Qn8FViuFoh/dKs2iQx6Er9qUDWsKbiYEqy+Wzgw9xKdXfY=
X-Received: by 2002:ac2:58c4:: with SMTP id u4mr1534856lfo.138.1614245388142;
 Thu, 25 Feb 2021 01:29:48 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
  <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
In-Reply-To: <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
From: "Andrey Zhizhikin" 
Date: Thu, 25 Feb 2021 10:29:36 +0100
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Terry Barnaby 
Cc: meta-freescale@lists.yoctoproject.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello Terry,

On Thu, Feb 25, 2021 at 10:01 AM Terry Barnaby  wrote:
>
>
> For a novice to NXP Freescale builds, what setup would you recommend as a=
 basic test Yocto build for a Wandboard IMX6 dual lite system in order to t=
est the performance of the hardware video processing system using gstreamer=
*imx (VPU etc) ?

Since I do not have any of the i.MX6 HW and unaware of the state of
VPU support - I can only speak from distro perspective. Anyone who
posses the HW can clarify points from machine perspective here.

>
> Would fslc-x11 or fslc-xwayland distro with the linux-fslc-imx kernel be =
the best approach or would some fsl-* distro with the linux-imx kernel be t=
he best approach ?

The first recommendation from my side would be: choose the distro
flavor. There are 2 types of distro in the layer: Community and
NXP-based.

1. All distros with `fsl-` prefix are generally NXP-based, and include
packages that NXP supplies as a part of their distribution. When it
comes to kernel and U-Boot support - `linux-imx` and `u-boot-imx`
packages are set as providers of `virtual/kernel` and
`virtual/bootloader` respectively. This automatically means that if
you take any of those distros prefixed with `fsl-` - you would be
building NXP-based distribution. In addition, all packages that are
marked as compatible with this BSP flavor would be included, in your
case that would include the `gstreamer*imx` package.
NOTE: you can switch the kernel provider to `linux-fslc-imx` for this
BSP flavor, which would include the kernel type I described already in
this thread (NXP release 2.1.0 + latest LTS patch level applied).
`linux-fslc` cannot be set with this type of distro.

2. All distros with `fslc-` prefix are Community-based distros, which
aims to include the upstream OSS packages and avoid using packages
which has "Proprietary" license types in them. Kernel provider is set
to `linux-fslc`, U-Boot provider is set to `u-boot-fslc`. As for the
`gstreamer*imx` - I do not know if the compatibility set in the recipe
would allow it to be included in this type of distro.
NOTE: in this type of distro - only `linux-fslc` can be used as kernel prov=
ider.

>
> The standard Wandboard build uses linux-fslc which does not seem to suppo=
rt the imx hardware features and so I am trying to build a suitable test pl=
atform but having no luck trying various build combinations that either won=
t build or wont run properly in various ways, so any pointers would be grat=
efully received !

This means that Wandboard sets IMX_DEFAULT_BSP =3D "mainline" somewhere
in its machine configuration, which targets the Community-based
distribution. You can try to find where it is set and change it to
IMX_DEFAULT_BSP =3D "nxp" to target NXP-based distro, and then use any
of `fsl-` prefixed configuration files on your DISTRO variable.

What you will get with this setup is then NXP-based distribution, but
since as I said above I do not have any i.MX6 HW - I cannot guarantee
that this setup would be 100% operable. Also in this case you would
opt-in to use NXP distribution, so you should watch for licensing
terms.

>
> Terry
>
>

--
Regards,
Andrey.

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailgate1.beam.ltd.uk (mailgate1.beam.ltd.uk [88.96.138.49])
 by mx.groups.io with SMTP id smtpd.web08.9173.1614246792352185252
 for ;
 Thu, 25 Feb 2021 01:53:12 -0800
Authentication-Results: mx.groups.io;
 dkim=missing; spf=pass (domain: beam.ltd.uk, ip: 88.96.138.49, mailfrom: terry@beam.ltd.uk)
Received: from study.kingnet (king.kingnet [82.69.10.222])
	by mailgate1.beam.ltd.uk (Postfix) with ESMTPSA id 1E4D96A1BB1;
	Thu, 25 Feb 2021 09:53:07 +0000 (GMT)
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Andrey Zhizhikin 
Cc: meta-freescale@lists.yoctoproject.org
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
 
From: "Terry Barnaby" 
Message-ID: <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk>
Date: Thu, 25 Feb 2021 09:53:07 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,NICE_REPLY_A
	autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on portal.beamnet
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB

On 25/02/2021 09:29, Andrey Zhizhikin wrote:
> Hello Terry,
>
> On Thu, Feb 25, 2021 at 10:01 AM Terry Barnaby  wrote:
>>
>> For a novice to NXP Freescale builds, what setup would you recommend as a basic test Yocto build for a Wandboard IMX6 dual lite system in order to test the performance of the hardware video processing system using gstreamer*imx (VPU etc) ?
> Since I do not have any of the i.MX6 HW and unaware of the state of
> VPU support - I can only speak from distro perspective. Anyone who
> posses the HW can clarify points from machine perspective here.
>
>> Would fslc-x11 or fslc-xwayland distro with the linux-fslc-imx kernel be the best approach or would some fsl-* distro with the linux-imx kernel be the best approach ?
> The first recommendation from my side would be: choose the distro
> flavor. There are 2 types of distro in the layer: Community and
> NXP-based.
>
> 1. All distros with `fsl-` prefix are generally NXP-based, and include
> packages that NXP supplies as a part of their distribution. When it
> comes to kernel and U-Boot support - `linux-imx` and `u-boot-imx`
> packages are set as providers of `virtual/kernel` and
> `virtual/bootloader` respectively. This automatically means that if
> you take any of those distros prefixed with `fsl-` - you would be
> building NXP-based distribution. In addition, all packages that are
> marked as compatible with this BSP flavor would be included, in your
> case that would include the `gstreamer*imx` package.
> NOTE: you can switch the kernel provider to `linux-fslc-imx` for this
> BSP flavor, which would include the kernel type I described already in
> this thread (NXP release 2.1.0 + latest LTS patch level applied).
> `linux-fslc` cannot be set with this type of distro.
>
> 2. All distros with `fslc-` prefix are Community-based distros, which
> aims to include the upstream OSS packages and avoid using packages
> which has "Proprietary" license types in them. Kernel provider is set
> to `linux-fslc`, U-Boot provider is set to `u-boot-fslc`. As for the
> `gstreamer*imx` - I do not know if the compatibility set in the recipe
> would allow it to be included in this type of distro.
> NOTE: in this type of distro - only `linux-fslc` can be used as kernel provider.
>
>> The standard Wandboard build uses linux-fslc which does not seem to support the imx hardware features and so I am trying to build a suitable test platform but having no luck trying various build combinations that either wont build or wont run properly in various ways, so any pointers would be gratefully received !
> This means that Wandboard sets IMX_DEFAULT_BSP = "mainline" somewhere
> in its machine configuration, which targets the Community-based
> distribution. You can try to find where it is set and change it to
> IMX_DEFAULT_BSP = "nxp" to target NXP-based distro, and then use any
> of `fsl-` prefixed configuration files on your DISTRO variable.
>
> What you will get with this setup is then NXP-based distribution, but
> since as I said above I do not have any i.MX6 HW - I cannot guarantee
> that this setup would be 100% operable. Also in this case you would
> opt-in to use NXP distribution, so you should watch for licensing
> terms.
>
>> Terry
>>
>>
> --
> Regards,
> Andrey.

Hi Andrey,

Many thanks for your time and info on this, that is a great help to firm 
up where I should be starting from and which distros are compatible (to 
some degree anyway) with which kernel.

 From what I am seeing I will have to use a NXP fsl-* based distribution 
to support the imx hardware video processing features. I have built such 
a distro with both linux-fslc-imx and limux-imx kernels (I think!) for 
the Wandboard, which boots and runs but the HDMI display was not 
functional. I will persevere looking at that.

Terry


From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-qk1-f178.google.com (mail-qk1-f178.google.com [209.85.222.178])
 by mx.groups.io with SMTP id smtpd.web08.9866.1614252088948242908
 for ;
 Thu, 25 Feb 2021 03:21:29 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@ossystems-com-br.20150623.gappssmtp.com header.s=20150623 header.b=qpkC667K;
 spf=pass (domain: ossystems.com.br, ip: 209.85.222.178, mailfrom: otavio.salvador@ossystems.com.br)
Received: by mail-qk1-f178.google.com with SMTP id h8so5225508qkk.6
        for ; Thu, 25 Feb 2021 03:21:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=ossystems-com-br.20150623.gappssmtp.com; s=20150623;
        h=from:mime-version:references:in-reply-to:date:message-id:subject:to
         :cc:content-transfer-encoding;
        bh=UDMr/494QLa8vGSWYuQFJ0aGCcX1HchdZwJHnkpRGdY=;
        b=qpkC667Kvolj47KvkbM4J2KvujYkQp1ByuRxHcqOTvxWKqPZIvIHoee3NZnqLVbV8+
         XrPWKCVucUEdKrHtDBbwPOaygHP5RM50hko9S3bw/BymUaPgTOhZCtZdGqgDcdTXJgI7
         WmWYvDMgUCpQT5x7+boc5ovrluu1Cmws1ltqbHu4PN+rUYkXaMksTX5+WKYClNGwu+KK
         ULcKvUQ+E/VvrbY+uJpDL8yAwrr0EzM+4k1zczbnqViablpK6NDTul7fUVjsTflLknYI
         dI0EjkJsIzeHYK7KQzNDodswKyoYL66aWzFjIH4CBYwMqad8wGKYUzOu87gut3IgScQx
         /csw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:from:mime-version:references:in-reply-to:date
         :message-id:subject:to:cc:content-transfer-encoding;
        bh=UDMr/494QLa8vGSWYuQFJ0aGCcX1HchdZwJHnkpRGdY=;
        b=pfbyO+APveRmlAUNJs9kQn1QtSFtZz7yZlRbd4GzshXmG4pfq3GX02QXhPTAYyT77V
         eIIchUkGPsbstLTeRe5pGgsNaPWPCnVAggVCYwnzTu1QiouaWGsnLKSxppsSL1m74/0q
         /JZK1DaWPzxtzrrgonI/0KOiMUMt/VRR1beifPZQbk6OylRGbOR1AKQOXqHZkN9kmjs1
         62XPSL2TIBqoAkkFhfjlqMN7p3EmWgzaEOHT5yryZoqVs9y83HRpgP7zgNTPeQjTYgu4
         ckqWWiINbgIJnPMwnuKYp5kXos5QiFLKd/0+ihANxX/g+L5t0LFrAw309iCp7Ed6+/hB
         bw0A==
X-Gm-Message-State: AOAM533PBfd+HzV4vHxLHZsvOLAntUdGQAExZ/N0I5cn+LWxT0T45jnf
	SKdxF69Acsibd01GWvdf7mD5kchPkMaM9sQV
X-Google-Smtp-Source: ABdhPJyI1OTx9DSmcTVuXjiCX45xxPFqDtuebdLjU7kLo1hX1MbOywuprqvGQPk5Ro06ArLfKcVcbA==
X-Received: by 2002:ae9:ef97:: with SMTP id d145mr2057796qkg.50.1614252087738;
        Thu, 25 Feb 2021 03:21:27 -0800 (PST)
Return-Path: 
Received: from mail-qk1-f173.google.com (mail-qk1-f173.google.com. [209.85.222.173])
        by smtp.gmail.com with ESMTPSA id w53sm3473060qtb.54.2021.02.25.03.21.27
        for 
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Thu, 25 Feb 2021 03:21:27 -0800 (PST)
From: "Otavio Salvador" 
X-Google-Original-From: Otavio Salvador 
Received: by mail-qk1-f173.google.com with SMTP id z190so5206022qka.9
        for ; Thu, 25 Feb 2021 03:21:27 -0800 (PST)
X-Received: by 2002:a37:a8d3:: with SMTP id r202mr563682qke.383.1614252087072;
 Thu, 25 Feb 2021 03:21:27 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk>
In-Reply-To: <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk>
Date: Thu, 25 Feb 2021 08:21:15 -0300
X-Gmail-Original-Message-ID: 
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Terry Barnaby 
Cc: Andrey Zhizhikin , meta-freescale@lists.yoctoproject.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
 escreveu:
>  From what I am seeing I will have to use a NXP fsl-* based distribution
> to support the imx hardware video processing features. I have built such
> a distro with both linux-fslc-imx and limux-imx kernels (I think!) for
> the Wandboard, which boots and runs but the HDMI display was not
> functional. I will persevere looking at that.

No, you don't. You can use linux-fslc (mainline) and fslc-* distros as
i.MX6 has full mainline support. At O.S. Systems we have been using
Linux mainline with many customers with great success.

--=20
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.51])
 by mx.groups.io with SMTP id smtpd.web08.10041.1614253684710645432
 for ;
 Thu, 25 Feb 2021 03:48:05 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=DG4+y6E3;
 spf=pass (domain: gmail.com, ip: 209.85.167.51, mailfrom: festevam@gmail.com)
Received: by mail-lf1-f51.google.com with SMTP id j19so8061975lfr.12
        for ; Thu, 25 Feb 2021 03:48:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=yzglRjfUI1VlJRheJ+S1ART0PG8wvffq6aaVeUN0Ts8=;
        b=DG4+y6E3GJYAcFtQ+aQ7lFkbaeST5FxzFbh/cpab+JYdzyaB9a5aVqZQ1R8qkN476A
         991rlBqEukSOy3eudi+OWqCW54/1DH5Jle0CDh9m9Jgl8D+dJz9B+ptVbwz+FZ/8UYNo
         3kE/x92AI9T/X0FnLwWGgzZQiTC/S0ShwOT1icS1MVo/2Gsdbzor2t0Qk07esAj2sajC
         9Ahfo9z9ddr+FizHyoGDr3RaF48Y/IPrZ3GHlGQFYrVPDxNhPUl/cRXDIL+XBorjFLY/
         lVxZsxRVgWfntTaLMo+e1bht8a22iyT04bLWPiqiP1CNSh3/y2FOA9EV9DZzW6vSsxHf
         oDOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=yzglRjfUI1VlJRheJ+S1ART0PG8wvffq6aaVeUN0Ts8=;
        b=mpf4NaOrRIBu6j0Uc35M0Ex6L3a+NLewj48v9X7cyepotzxGM3Z/a9Glv7/XFwc5RR
         +LPl3M69mGY/IyDsQTMRAwjN1gQHxrg3aMoa/b+iKVhLh25R+Q2l1PPhFmoPt84/uCCg
         n8MgjC5Mdp+GPYX0MJR8g+NZ9u2m/1i0Fe2IRSOzN66oKz6tma3QPbWMLv7UTsP395wV
         T21SE8BNiqbZxUWOm6nxvJwD1OZrThe8TwWFuTS1Yuh7Xj9WJwg5iVg3j+xh3rkbP2s7
         SCubOiqoKvzuQ0KObO2wN0uKSYHvtV9yZZ3rOAa8Pu6xU+dl3PsMK7iKw3S7XMt69BZM
         mK3A==
X-Gm-Message-State: AOAM532Ol1+RWF84klPjnqiQdE3M3VOuJnPHEVNSrqHDVbgYTKUQrq8V
	YOefPPYRZnPBz2v8I/ETDycSP+5b0GhmeOp1vvY=
X-Google-Smtp-Source: ABdhPJzffM0Q5iDz2sk8FQMDFCmD8sU7PK60Z5JalXzVCaIKxhzFXdAia005d5nsZnqqoItOAKqfWOLcb+yYYg4NGaU=
X-Received: by 2002:a05:6512:10c5:: with SMTP id k5mr1672228lfg.583.1614253682706;
 Thu, 25 Feb 2021 03:48:02 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> 
In-Reply-To: 
From: "Fabio Estevam" 
Date: Thu, 25 Feb 2021 08:47:51 -0300
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Andrey Zhizhikin 
Cc: Terry Barnaby , meta-freescale@lists.yoctoproject.org
Content-Type: text/plain; charset="UTF-8"

Hi Terry,

On Thu, Feb 25, 2021 at 6:29 AM Andrey Zhizhikin  wrote:

> > For a novice to NXP Freescale builds, what setup would you recommend as a basic test Yocto build for a Wandboard IMX6 dual lite system in order to test the performance of the hardware video processing system using gstreamer*imx (VPU etc) ?
>
> Since I do not have any of the i.MX6 HW and unaware of the state of
> VPU support - I can only speak from distro perspective. Anyone who
> posses the HW can clarify points from machine perspective here.

Yes, imx6 is well supported in mainline kernels including VPU support.

Please note that with the mainline kernel, you should use the standard
gstreamer packages, not the gstreamer-imx ones.

The gstreamer-imx packages are meant to be used only with NXP kernels.

Regards,

Fabio Estevam

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailgate1.beam.ltd.uk (mailgate1.beam.ltd.uk [88.96.138.49])
 by mx.groups.io with SMTP id smtpd.web08.10060.1614253828036176171
 for ;
 Thu, 25 Feb 2021 03:50:28 -0800
Authentication-Results: mx.groups.io;
 dkim=missing; spf=pass (domain: beam.ltd.uk, ip: 88.96.138.49, mailfrom: terry@beam.ltd.uk)
Received: from study.kingnet (king.kingnet [82.69.10.222])
	by mailgate1.beam.ltd.uk (Postfix) with ESMTPSA id A65966A1BB1;
	Thu, 25 Feb 2021 11:50:23 +0000 (GMT)
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Otavio Salvador 
Cc: Andrey Zhizhikin ,
 meta-freescale@lists.yoctoproject.org
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk>
 
From: "Terry Barnaby" 
Message-ID: <66670eb7-6ade-bf48-7a88-b2dc56944f10@beam.ltd.uk>
Date: Thu, 25 Feb 2021 11:50:23 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,NICE_REPLY_A
	autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on portal.beamnet
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable

On 25/02/2021 11:21, Otavio Salvador wrote:
> Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
>  escreveu:
>>   From what I am seeing I will have to use a NXP fsl-* based distribut=
ion
>> to support the imx hardware video processing features. I have built su=
ch
>> a distro with both linux-fslc-imx and limux-imx kernels (I think!) for
>> the Wandboard, which boots and runs but the HDMI display was not
>> functional. I will persevere looking at that.
> No, you don't. You can use linux-fslc (mainline) and fslc-* distros as
> i.MX6 has full mainline support. At O.S. Systems we have been using
> Linux mainline with many customers with great success.
>
Thanks for the info, I must be getting something wrong then.

If I do, what I think is a standard http://freescale.github.io dunfell=20
build, using "MACHINE ??=3D 'wandboard'", "DISTRO ?=3D 'fslc-x11'" and ad=
d=20
IMAGE_INSTALL_append=3D" gstreamer1.0-plugins-imx" to get the gstreamer=20
plugs for the imx video processing hardware support built (they are not=20
there by default, this uses linux-fslc), I get an error:

ERROR: Nothing RPROVIDES 'gstreamer1.0-plugins-imx' (but=20
/datal3/DartSystems/ds200i-system/fsl-community-bsp/sources/meta-freescal=
e-distro/recipes-fsl/images/fsl-image-multimedia-full.bb=20
RDEPENDS on or otherwise requires it)
gstreamer1.0-plugins-imx was skipped: incompatible with machine=20
wandboard (not in COMPATIBLE_MACHINE)

If I use an IMX_DEFAULT_BSP=3D"nxp" based build the=20
gstreamer1.0-plugins-imx gets built. So what am i doing wrong ?


From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailgate1.beam.ltd.uk (mailgate1.beam.ltd.uk [88.96.138.49])
 by mx.groups.io with SMTP id smtpd.web10.10290.1614254281282102016
 for ;
 Thu, 25 Feb 2021 03:58:01 -0800
Authentication-Results: mx.groups.io;
 dkim=missing; spf=pass (domain: beam.ltd.uk, ip: 88.96.138.49, mailfrom: terry@beam.ltd.uk)
Received: from study.kingnet (king.kingnet [82.69.10.222])
	by mailgate1.beam.ltd.uk (Postfix) with ESMTPSA id 60DD06A1BB1;
	Thu, 25 Feb 2021 11:57:57 +0000 (GMT)
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Fabio Estevam , Andrey Zhizhikin 
Cc: meta-freescale@lists.yoctoproject.org
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
 
 
From: "Terry Barnaby" 
Message-ID: 
Date: Thu, 25 Feb 2021 11:57:57 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,NICE_REPLY_A
	autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on portal.beamnet
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB

On 25/02/2021 11:47, Fabio Estevam wrote:
> Hi Terry,
>
> On Thu, Feb 25, 2021 at 6:29 AM Andrey Zhizhikin  wrote:
>
>>> For a novice to NXP Freescale builds, what setup would you recommend as a basic test Yocto build for a Wandboard IMX6 dual lite system in order to test the performance of the hardware video processing system using gstreamer*imx (VPU etc) ?
>> Since I do not have any of the i.MX6 HW and unaware of the state of
>> VPU support - I can only speak from distro perspective. Anyone who
>> posses the HW can clarify points from machine perspective here.
> Yes, imx6 is well supported in mainline kernels including VPU support.
>
> Please note that with the mainline kernel, you should use the standard
> gstreamer packages, not the gstreamer-imx ones.
>
> The gstreamer-imx packages are meant to be used only with NXP kernels.
>
> Regards,
>
> Fabio Estevam

Many thanks for that info, from Internet info it looked like the 
gstreamer-imx package and associated lower libraries/drivers were 
needed, I will try another build, the gstreamer video hardware support 
wasn't there (as reported by gst-inspect-1.0) when I tried, maybe I got 
lost in a tangle of distro, kernel and bitbake targets.

Terry


From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172])
 by mx.groups.io with SMTP id smtpd.web12.10430.1614254553789600572
 for ;
 Thu, 25 Feb 2021 04:02:34 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=WI2axGxR;
 spf=pass (domain: gmail.com, ip: 209.85.208.172, mailfrom: festevam@gmail.com)
Received: by mail-lj1-f172.google.com with SMTP id u4so6175116lja.3
        for ; Thu, 25 Feb 2021 04:02:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=7Bs/BBd1kxpz4ouREc2kKCTFYwW2MS6LFJ+h0Q4M64A=;
        b=WI2axGxR6TNuDnG7q92hjG0XWq5b4BwpTHWg1kXdlTcRcGdlB/Qyyp8umqN3DJpS+k
         SvAK4P0MvUyJEl3P4JcNoJ/V4SkKzOuTBxRH4l/X2d3BkjxfSa6pI1kt6rT8EMu+U7Hw
         9+8YKTGm76ho47eSoqQjFepPXjVOkYHRHJ77nOR3UXZJX7aMh+d/2CU121qwCp51BBXf
         bt8gLPMqOgo2dQuM5qpP45fSwE2yqIgPhnnvnjbc+MbsBldl/CZJpR20YWK+Umx/lNmv
         G9tkClD0JWBzaSJdsTtZX/zFFv60oPzqoX5B5w5KVUnVAKd2FEEOrxVs7NNt41oqxBh1
         VD7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=7Bs/BBd1kxpz4ouREc2kKCTFYwW2MS6LFJ+h0Q4M64A=;
        b=JY8S3Xt0qY/gQh6PRe57650H1jjQ2otTuzUod7JlNFb6Vo1VPftvogM9dOtHVXcwCJ
         Yv65BvPTw8ylgBz+Iz235wZ5WzASDjQH310OKiDzZE5sDY6uNOIMjzGUXARDHlJu5FaF
         pmTFC7OTYZITr5SFq4ddGcqDmv/iJIwd7eqojzCU1PM2NBnlrBxmSQcu19ZruQuX7UfF
         xOEbi6Q+0VHVcWHr/aL+AJB+T1vr6hZiKdbphNrQvcueNtjko+lQD2pbOZBZedSLFTh2
         PB2TRJuBSxmOwu6tUJ3jVuB50aK+sr13lIal5dBDl/qafmw7y9fG7r5z94A5lNbOC12h
         6Btg==
X-Gm-Message-State: AOAM530d2iClCr12n7mOM0UVYy3uKIHjITtAsx79wBPTgMRUIVGzmD++
	+SBa4Mtxnmq45Yf3vPkjmM6nqSLqF1jwy23hvoM=
X-Google-Smtp-Source: ABdhPJwVs0cTkcKYAHfCPklH8I+i39FMyVBkMQpIElsppit40cHwbuA48/Mot+n7ybqWlBW0umWN0dFlohSLaLHsbbs=
X-Received: by 2002:a2e:8357:: with SMTP id l23mr1459974ljh.116.1614254551748;
 Thu, 25 Feb 2021 04:02:31 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> 
  
In-Reply-To: 
From: "Fabio Estevam" 
Date: Thu, 25 Feb 2021 09:02:20 -0300
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Terry Barnaby 
Cc: Andrey Zhizhikin , meta-freescale@lists.yoctoproject.org
Content-Type: text/plain; charset="UTF-8"

On Thu, Feb 25, 2021 at 8:58 AM Terry Barnaby  wrote:

> Many thanks for that info, from Internet info it looked like the
> gstreamer-imx package and associated lower libraries/drivers were
> needed, I will try another build, the gstreamer video hardware support
> wasn't there (as reported by gst-inspect-1.0) when I tried, maybe I got
> lost in a tangle of distro, kernel and bitbake targets.

The v4l2dec/enc plugins only show up if the VPU driver were successfully loaded.

Make sure that the VPU (coda) driver is being loaded correctly with
the associated firmware.

After that, these v4l2dec/enc plugins should be reported by gst-inspect.

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from hosting.emcodev.net (hosting.emcodev.net [178.18.92.162])
 by mx.groups.io with SMTP id smtpd.web11.10355.1614255493735907672
 for ;
 Thu, 25 Feb 2021 04:18:14 -0800
Authentication-Results: mx.groups.io;
 dkim=fail reason="signature has expired" header.i=@basmevissen.nl header.s=default header.b=dbVKVqIj;
 spf=pass (domain: basmevissen.nl, ip: 178.18.92.162, mailfrom: abuse@basmevissen.nl)
Received: from localhost (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id 4585A212011;
	Thu, 25 Feb 2021 13:18:10 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=basmevissen.nl;
	 h=message-id:user-agent:references:in-reply-to:subject:subject
	:from:from:date:date:content-transfer-encoding:content-type
	:content-type:mime-version; s=default; t=1614255486; x=
	1616069887; bh=27+qgRhlSUpBxMpNX/P+Vu3tmfLAJFjrEKrT3FJPe0I=; b=d
	bVKVqIjisGpBTc+NQjyy4Kz90BOKOIxT2ibMRZ4+plx483KEXxj/UcCcYCn9weot
	QmAnw08RhI980FP2GleqKnf8JJQN3EZFTqaQBmnEPDgHrE2GqRGJPcxjEQ9aPqYK
	bG+lN5RULQTslEHVskfRLZ9Thw23JETI0f7NI/25hxrowdph9Huqg9MhHHGRJD1K
	BjUJg5R+sab7RVpjbgTj/qXn1DTxNsvQqPmVAKPrQuqTvPn2xzVjkDPzH9vVkpLT
	OdM7JqUNkmOu2/EtKdJXOPeyHligvENt7vLStesGVtV0FKAyV0VS/24/MfHvN8B9
	v9iz3SXiUNaIZSiI03TdGvMPSbIKOrlkHvebJXnniFRLF6CMS1vAkNE3coqsq36s
	l2YIJvssUDNl8E1pDNYQlN6HnSMCDur0Fuhp1iNBPV+u+2eap/6fg1crg2MPL0Qz
	d6RakVsWT6UyRPn8/JCfRGGIy+znojr8JRvNVCpaLEktZXPOPSq4082A+t/kQqKH
	72YuDME8uUlDjgHQvb4qKCgZcBHDIjDderBrepBY+tAqsoA810lUk97Rh0OV5t0Q
	tIjutEFfaLJzUk8kfu2Kear0+2TNNmqaIa2wO3JkrQaUBWxOJioO9YHi35jIcIZ1
	gyrhl+Q8RqQ6rLS2L8YKEfwJeMW7b8thJplGupDuZ4=
Received: from hosting.emcodev.net ([127.0.0.1])
	by localhost (hosting.emcodev.net [127.0.0.1]) (amavisd-new, port 10026)
	with LMTP id ecqULx7-sPy1; Thu, 25 Feb 2021 13:18:06 +0100 (CET)
Received: from emcodev.nl (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id 8232121200B;
	Thu, 25 Feb 2021 13:18:06 +0100 (CET)
MIME-Version: 1.0
Date: Thu, 25 Feb 2021 13:18:06 +0100
From: "Bas Mevissen" 
To: Otavio Salvador 
Cc: Terry Barnaby , Andrey Zhizhikin
 , meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
In-Reply-To: 
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk>
 
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl>
X-Sender: abuse@basmevissen.nl
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: quoted-printable

On 2021-02-25 12:21, Otavio Salvador wrote:
> Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
>  escreveu:
>>  From what I am seeing I will have to use a NXP fsl-* based=20
>> distribution
>> to support the imx hardware video processing features. I have built=20
>> such
>> a distro with both linux-fslc-imx and limux-imx kernels (I think!) for
>> the Wandboard, which boots and runs but the HDMI display was not
>> functional. I will persevere looking at that.
>=20
> No, you don't. You can use linux-fslc (mainline) and fslc-* distros as
> i.MX6 has full mainline support. At O.S. Systems we have been using
> Linux mainline with many customers with great success.
>=20

Wouldn't make sense to first evaluate the performance of the platform=20
(as Terry plans to do) first on an NXP fsl-* distro? In that case one=20
can get direct support from NXP if required. After that, derive your own=
=20
distro from fslc-*.

BTW Would kernel.org stable kernel work as well on i.MX6 if you need=20
graphics and video? I used it successfully for headless IOT=20
applications.

Bas.

>=20
>=20


From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175])
 by mx.groups.io with SMTP id smtpd.web08.10374.1614255906093805344
 for ;
 Thu, 25 Feb 2021 04:25:06 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=Vn0U+6dW;
 spf=pass (domain: gmail.com, ip: 209.85.208.175, mailfrom: andrey.z@gmail.com)
Received: by mail-lj1-f175.google.com with SMTP id h4so6037011ljl.0
        for ; Thu, 25 Feb 2021 04:25:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc:content-transfer-encoding;
        bh=QmrNpS5afN18sJuN8XmdoyZNTyB3U0PDJOWJtc/IHiE=;
        b=Vn0U+6dW/+xUADRLJ6n8rgt2jxDPW8kanIvuHQ6TJgoD1HCXwpxmxG3nZU/rOdVbEJ
         j0YO6dlCx9jp40fDvN7Cheq2dXgNpdEvGnoCiGD+Jo+0trVHiOaJZOvEqf9r8A+wGbCl
         v1ByrZT8utvRMPttJnt0gU1MGN5/hWnV4YN0G84OjVSDPqchwmkOSb7vqRQIvbqPo4ih
         cWZWeJzidLUSn4yXl10RuIaW4fFzdczx9cIBFGLD7ka2P0c3DuHymTmM2pjyyOejhlAh
         IbdMzxg4bqFzh1j4lcZqvWFvTKKhvlrMw2GExhnVP8fUb8wMrdeYeuyePEFm1fa4/DEO
         YFJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc:content-transfer-encoding;
        bh=QmrNpS5afN18sJuN8XmdoyZNTyB3U0PDJOWJtc/IHiE=;
        b=ugrzEFWVhAOsfOzQDjFRbZ+2ped9QATbfrRPBwHqpUP5snDzDEQZFxB8DFyib1uqdL
         pmcXmIMdeqGg4oKWh/QYlvPUyoKlkmAI7wY/q0kosNAWg8uUQHsiAVi1D75f/gkKHGTd
         sflkagTBs4M3oBdeaYlt88rdsZ/EO3nZprI2gwFLMukE9ucZtC79Qo85u1i5/cIyYWvg
         y7LAWNog/9K9rzeeu3gj8VJ2FvgXuRxK4v2uVOpI8NoybT/y5uWRmz+cqq4oLtqqHyYc
         omaaS3cZlY6Gx1OOWlh9gGDLCgkT3Fy9I2pdLQoWiTpb7N5bO7lfPa5NBjJMKN0WJOLE
         14xQ==
X-Gm-Message-State: AOAM533dva57ZE/sUUsavGJDkLf5Mk6zr4ft/2dujkDvpTuMe1t6uM+Q
	DwzxO6uFRyK/6hhKCyJUwHVH0Z243jt1J/Aaxk0=
X-Google-Smtp-Source: ABdhPJxD+dWCNwvSDVeCsyaaWNY1YCfXQ8UgJDJzqzy516+MiaGuM9fw8uH7SswvByZ/M5bMSnimsi0sA4wZ6M+1dDw=
X-Received: by 2002:a2e:8512:: with SMTP id j18mr1446425lji.331.1614255904134;
 Thu, 25 Feb 2021 04:25:04 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk> 
 <66670eb7-6ade-bf48-7a88-b2dc56944f10@beam.ltd.uk>
In-Reply-To: <66670eb7-6ade-bf48-7a88-b2dc56944f10@beam.ltd.uk>
From: "Andrey Zhizhikin" 
Date: Thu, 25 Feb 2021 13:24:52 +0100
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Terry Barnaby 
Cc: Otavio Salvador , meta-freescale@lists.yoctoproject.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 25, 2021 at 12:50 PM Terry Barnaby  wrote:
>
> On 25/02/2021 11:21, Otavio Salvador wrote:
> > Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
> >  escreveu:
> >>   From what I am seeing I will have to use a NXP fsl-* based distribut=
ion
> >> to support the imx hardware video processing features. I have built su=
ch
> >> a distro with both linux-fslc-imx and limux-imx kernels (I think!) for
> >> the Wandboard, which boots and runs but the HDMI display was not
> >> functional. I will persevere looking at that.
> > No, you don't. You can use linux-fslc (mainline) and fslc-* distros as
> > i.MX6 has full mainline support. At O.S. Systems we have been using
> > Linux mainline with many customers with great success.
> >
> Thanks for the info, I must be getting something wrong then.
>
> If I do, what I think is a standard http://freescale.github.io dunfell
> build, using "MACHINE ??=3D 'wandboard'", "DISTRO ?=3D 'fslc-x11'" and ad=
d
> IMAGE_INSTALL_append=3D" gstreamer1.0-plugins-imx" to get the gstreamer
> plugs for the imx video processing hardware support built (they are not
> there by default, this uses linux-fslc), I get an error:
>
> ERROR: Nothing RPROVIDES 'gstreamer1.0-plugins-imx' (but
> /datal3/DartSystems/ds200i-system/fsl-community-bsp/sources/meta-freescal=
e-distro/recipes-fsl/images/fsl-image-multimedia-full.bb
> RDEPENDS on or otherwise requires it)
> gstreamer1.0-plugins-imx was skipped: incompatible with machine
> wandboard (not in COMPATIBLE_MACHINE)

This is expected, and actually follows to what I previously said:
gstreamer1.0-plugins-imx package is not compatible with Community BSP
(chosen by setting  IMX_DEFAULT_BSP=3D"mainline").

As Fabio already indicated, gstreamer1.0-plugins-imx should be used
**only** with NXP-based BSP (selected by setting
IMX_DEFAULT_BSP=3D"nxp") as it requires the NXP-specific modifications
in the kernel, which are not upstreamed (and probably would not be).

>
> If I use an IMX_DEFAULT_BSP=3D"nxp" based build the
> gstreamer1.0-plugins-imx gets built. So what am i doing wrong ?
>

This is also expected behavior. Once opted for NXP-based BSP - package
compatibility becomes valid, hence it can be built and installed.

So in a sense - you're not doing anything wrong here. You're changing
the BSP flavor from Community to NXP-based one.

--=20
Regards,
Andrey.

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-lf1-f53.google.com (mail-lf1-f53.google.com [209.85.167.53])
 by mx.groups.io with SMTP id smtpd.web12.10743.1614256361710713193
 for ;
 Thu, 25 Feb 2021 04:32:42 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=u6Efijo2;
 spf=pass (domain: gmail.com, ip: 209.85.167.53, mailfrom: andrey.z@gmail.com)
Received: by mail-lf1-f53.google.com with SMTP id d24so8290611lfs.8
        for ; Thu, 25 Feb 2021 04:32:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc:content-transfer-encoding;
        bh=+me5iamOVBnykuGbt09dkEQDnah/gz+Diejh5BVDBcU=;
        b=u6Efijo2GmWlUd6hPisLMLd1rSWrCqK+5beA+AdIh/pHn5QlbKD88TpWEQ+6WbBg7j
         Kakeb35AdnYRp2NMYNBD39bBfukS4wHLM63iEZoAwE4W/YQHvorXRTF+jP0xQ8CoNUcR
         3IKhrk/Eug1mZTuvqwwAIH+DmWlHgR6OcLCqg99HpgsFdApi9L0uecBdL5Ri4Ek3hfwP
         4hfdjgmjHY+qQUTYvDB6bf4yEdtLds5/E+Xwz6qJz5qS/gmCo8OolE4NEWJXzVyn2Gbh
         eyIyPappFVN6rAiixcW/yQb/f96olHT50T/breIouUSBj6qs7oJgjUwHXeDEC6EoufqG
         9w3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc:content-transfer-encoding;
        bh=+me5iamOVBnykuGbt09dkEQDnah/gz+Diejh5BVDBcU=;
        b=BRiBWFOBNd+fivf7/nDTXCkkawb5mmM/j2wWKks2zqMe9W2rGYePcbWY/a3FhnfCPe
         FAA8FgMZMOFlTsQ1TcdQWRKUXdF3jNi3p+smszQcOuWL2gf+cRJcyr73uxhXqFcNZbis
         lqoztDpO6NUSf6c7a9Y27qxaS10WuXBfoBdg7WcpVTtCY9XEvwGsCegNOlguBJYbd3wy
         /2MNOIaCQaL+oFBVgOvOpF5wm9ZMq++GcVT7ut5lYWvIeeKg7GBhyEVwvLd4NFsH+mFi
         zV3OIRR5iPFXPuQI7WgCVGNp3bnlXxbxhSYn1z0DNq5cVhi/nR8cyMg22volBz4s6Cjs
         aSeQ==
X-Gm-Message-State: AOAM531oKleIJtCpipjgqneLOEHaUOdCxbSTSR+JOQY00ulRIs46r0in
	Als5kaqmsJpngx7M3M4tIqXFI1D/y2RIzsJI7hM=
X-Google-Smtp-Source: ABdhPJyxA3CKIV1CvsnwxWUlIbzykAOFM/VBs9VcloSJ2BvhbTlqpWmuUd5p+2Co1b7rQmcxlW2RG89qHR6+bXjE9mk=
X-Received: by 2002:ac2:58c4:: with SMTP id u4mr1919011lfo.138.1614256359769;
 Thu, 25 Feb 2021 04:32:39 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk> 
 <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl>
In-Reply-To: <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl>
From: "Andrey Zhizhikin" 
Date: Thu, 25 Feb 2021 13:32:28 +0100
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Bas Mevissen 
Cc: Otavio Salvador , Terry Barnaby , 
	meta-freescale@lists.yoctoproject.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello Bas,

On Thu, Feb 25, 2021 at 1:18 PM Bas Mevissen  wrote:
>
> On 2021-02-25 12:21, Otavio Salvador wrote:
> > Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
> >  escreveu:
> >>  From what I am seeing I will have to use a NXP fsl-* based
> >> distribution
> >> to support the imx hardware video processing features. I have built
> >> such
> >> a distro with both linux-fslc-imx and limux-imx kernels (I think!) for
> >> the Wandboard, which boots and runs but the HDMI display was not
> >> functional. I will persevere looking at that.
> >
> > No, you don't. You can use linux-fslc (mainline) and fslc-* distros as
> > i.MX6 has full mainline support. At O.S. Systems we have been using
> > Linux mainline with many customers with great success.
> >
>
> Wouldn't make sense to first evaluate the performance of the platform
> (as Terry plans to do) first on an NXP fsl-* distro? In that case one
> can get direct support from NXP if required. After that, derive your own
> distro from fslc-*.

This might not be quite indicative, as the NXP kernel might have some
"shortcuts" to boost performance in certain areas, sacrificing
conformance of the source code.

You might experience the situation that video performs quite well, but
then after opting for NXP kernel - you might find that some other
areas are not working as expected (some other domains). This would put
you in a situation that you've already committed to choose and deploy
the NXP-based BSP and would leave you to solve the issues in those
domains on your own efforts.

This is my pure speculation here, so take it with a grain of salt though. :=
)

IMHO, this should be considered and before the final product receives
commitment to use either of BSP flavors - all areas should be
validated, not only the performance aspects of Multimedia domain.

>
> BTW Would kernel.org stable kernel work as well on i.MX6 if you need
> graphics and video? I used it successfully for headless IOT
> applications.

As Fabio already indicated - this is possible.

>
> Bas.
>

--
Regards,
Andrey.

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from hosting.emcodev.net (hosting.emcodev.net [178.18.92.162])
 by mx.groups.io with SMTP id smtpd.web11.10703.1614257720018698360
 for ;
 Thu, 25 Feb 2021 04:55:21 -0800
Authentication-Results: mx.groups.io;
 dkim=fail reason="signature has expired" header.i=@basmevissen.nl header.s=default header.b=jdEPkqRL;
 spf=pass (domain: basmevissen.nl, ip: 178.18.92.162, mailfrom: abuse@basmevissen.nl)
Received: from localhost (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id D57C5212011;
	Thu, 25 Feb 2021 13:55:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=basmevissen.nl;
	 h=message-id:user-agent:references:in-reply-to:subject:subject
	:from:from:date:date:content-transfer-encoding:content-type
	:content-type:mime-version; s=default; t=1614257715; x=
	1616072116; bh=C3evSHGhUykWJ9tE/iQgbz5FDEysCY93IoGMKpImOIc=; b=j
	dEPkqRLf+EdoQbBCiAARaagHVpkrbbO1XzuwFymUEOxcMIRM9wYEROP6YN/Zycir
	+1ypOFye4KIkfWXW053xhartcz8/qGIIJVzvz7WkiF5lL57chiVWIzhA1hOw0BIu
	b52zSKHeIkwED9mAG7mdEfAD+x+ZjfMC7AMXHxisFPz5BwROMx3EfW3CHrqRs01x
	1sG3km0SYGizGNhb6kfAqqGBy6JM1IkSTmnmWemUF0Nfw1iR/hNEjCjpzyeqzatp
	QU1DV7HqjW8G+Fz34RwhXxxcs1gm2Gem4cxEtxP2mKv1P8ZhAh+AWHm/AiY0Vlmt
	nfGpwA1XB5IotIpr8Hx4U5MiiqNM6EPEmlwjuJnr1HYAiE0T2m9e5QhXArjQnXFQ
	JZNqpGQ12mjAN/PdrF0xANTTfS9k+nf5yrqbT4XoY14awz8MkC4uzP0Qj/rM4WCh
	D/o7VWIMTuyiMr0U875vwnSWDnvo3FwgNIW24u/D/+ud7Of0Jim2RRKb47umJj8a
	Y3EMbvcfiuqRWeJkfVDfdTPWJyn3vN4eQrQew9xMXbZGnEnpxXY12zEiByMKixWN
	9LeEfbqo9LD4lk6/I/hTXVTA8Z/3wsqS2GoSKQRVQVqRopQOurwlcEI7GQqxhlnf
	rJwqQdVLTJrUmdHW6E6CnQEYeN14UTLqcY6KbXTU2M=
Received: from hosting.emcodev.net ([127.0.0.1])
	by localhost (hosting.emcodev.net [127.0.0.1]) (amavisd-new, port 10026)
	with LMTP id fn9Antem8g6G; Thu, 25 Feb 2021 13:55:15 +0100 (CET)
Received: from emcodev.nl (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id 4D14821200B;
	Thu, 25 Feb 2021 13:55:15 +0100 (CET)
MIME-Version: 1.0
Date: Thu, 25 Feb 2021 13:55:15 +0100
From: "Bas Mevissen" 
To: Andrey Zhizhikin 
Cc: Otavio Salvador , Terry Barnaby
 , meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
In-Reply-To: 
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk>
 
 <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl>
 
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl>
X-Sender: abuse@basmevissen.nl
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: quoted-printable

On 2021-02-25 13:32, Andrey Zhizhikin wrote:
> Hello Bas,
>=20
> On Thu, Feb 25, 2021 at 1:18 PM Bas Mevissen =20
> wrote:
>>=20
>> On 2021-02-25 12:21, Otavio Salvador wrote:
>> > Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
>> >  escreveu:
>> >>  From what I am seeing I will have to use a NXP fsl-* based
>> >> distribution
>> >> to support the imx hardware video processing features. I have built
>> >> such
>> >> a distro with both linux-fslc-imx and limux-imx kernels (I think!) f=
or
>> >> the Wandboard, which boots and runs but the HDMI display was not
>> >> functional. I will persevere looking at that.
>> >
>> > No, you don't. You can use linux-fslc (mainline) and fslc-* distros a=
s
>> > i.MX6 has full mainline support. At O.S. Systems we have been using
>> > Linux mainline with many customers with great success.
>> >
>>=20
>> Wouldn't make sense to first evaluate the performance of the platform
>> (as Terry plans to do) first on an NXP fsl-* distro? In that case one
>> can get direct support from NXP if required. After that, derive your=20
>> own
>> distro from fslc-*.
>=20
> This might not be quite indicative, as the NXP kernel might have some
> "shortcuts" to boost performance in certain areas, sacrificing
> conformance of the source code.
>=20

At least you get an idea of what the HW platform can do.

> You might experience the situation that video performs quite well, but
> then after opting for NXP kernel - you might find that some other
> areas are not working as expected (some other domains). This would put
> you in a situation that you've already committed to choose and deploy
> the NXP-based BSP and would leave you to solve the issues in those
> domains on your own efforts.
>=20
> This is my pure speculation here, so take it with a grain of salt=20
> though. :)
>=20
IMHO, you should never base your *product* on FSL. It is (at least, that=
=20
is what was told me by (then) Freescale field engineers) only there to=20
demonstrate the platform. Maybe that has changed over time.

When there is a huge performance difference between fsl and fslc, it=20
needs to be resolved.

> IMHO, this should be considered and before the final product receives
> commitment to use either of BSP flavors - all areas should be
> validated, not only the performance aspects of Multimedia domain.
>=20

Yes, when you have decided on the hardware to use. If you are evaluating=
=20
the hardware to see whether it meets your requirements, you might want=20
to take the option that gives you the best impression of the performance=
=20
that can be achieved without too much of a hassle.
(it is an important step to do, at a stage of the development where time=
=20
is usually very limited, so you want a quick but reliable result).

>>=20
>> BTW Would kernel.org stable kernel work as well on i.MX6 if you need
>> graphics and video? I used it successfully for headless IOT
>> applications.
>=20
> As Fabio already indicated - this is possible.
>=20

Fabio said "mainline". I'm not sure whether meant linux-fslc (as Otavio=20
used it) or kernel.org.
So I wanted to check that.

>>=20
>> Bas.
>>=20
>=20
> --
> Regards,
> Andrey.
>=20
>=20
>=20

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-lf1-f41.google.com (mail-lf1-f41.google.com [209.85.167.41])
 by mx.groups.io with SMTP id smtpd.web08.10725.1614258126834847878
 for ;
 Thu, 25 Feb 2021 05:02:07 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=KCg/CHYZ;
 spf=pass (domain: gmail.com, ip: 209.85.167.41, mailfrom: festevam@gmail.com)
Received: by mail-lf1-f41.google.com with SMTP id h125so8413880lfd.7
        for ; Thu, 25 Feb 2021 05:02:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=hlvFQxcIjrS8ikGwFfftvgJmmlNN/jKjJDCoUIbFi2o=;
        b=KCg/CHYZFqmtZwh82zpsdfwH9BwKMCCgWxpC74yadTAJONSLZYJrSQz7ceYLQ822OT
         XGxWFsmyRLc6w5raD1wMmG7LDAjlZiE+SsNiedz4MF6ZJc5u6ZDRqLDyFYQNnv+aQoCo
         r+k8vQ0BiOh/YxJ+SsGJ/OmGJAyw4LNKwtBpDMsVLkKNk6JGIZLdCsc4ak5t/v75NiIh
         6Qx9ZcR3elpXFjsu+rBlSyXowkazB+CRt9b39peYucvLwZF+fo3ahZVb9cN0r2B3UrMi
         O0pgEgKuqqHcW8wflrMobi4pPMzZIstz5UHHkWRGbWc/j+waLjqFd4HsaG3BSi7H/aec
         Gc5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=hlvFQxcIjrS8ikGwFfftvgJmmlNN/jKjJDCoUIbFi2o=;
        b=Oz1fWjILUXfSYYOcIMFSPBXcxrnOzTyxvWEGVlJBCyznYIS/FVCdOj6sxu9gBSTnPb
         5YmwYwRot6jZe7M1dyieL871uIeVFaRY1qCmocRLYJy39jxKBGtrhCFTXN9UhIubnjdH
         v9ZrGNjAaQcirWi2RauuAGSCIVE1Du5/Bhf0xwfgXVbDBZufnD40kWCW+IiPQDUKV03Q
         QYLAhmyBpWzoVQ8IAKp4rdS7R7sg7wg5NAej2dRB6A4ExNXn7l1cI0h2nbChqjqOY2YD
         BrsF4+uPZZoBGdTC7xr8G6jcS6k57PhPI+Gpqf3ME0w/DlchNR+wQdVwRGbFlEkCN6fW
         bO5Q==
X-Gm-Message-State: AOAM53178stJvpiTd6OsIsiOzEAGniC6rt2bT2k/1Nnamd4H+dHPfEyO
	5CmN9e2Ei2dbIJanZPoWpaKRRF+qM/h8DppDOL4=
X-Google-Smtp-Source: ABdhPJxguwJ8I/D08Akp4mWI4cyqfvPkMYxUByFc3T/NjO6mmIdzJ9WgXGjV+HXJTmut9+NcDPbXs89Bu2AXfWK2nMA=
X-Received: by 2002:a05:6512:3884:: with SMTP id n4mr1907558lft.539.1614258124759;
 Thu, 25 Feb 2021 05:02:04 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk> 
 <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl> 
 <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl>
In-Reply-To: <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl>
From: "Fabio Estevam" 
Date: Thu, 25 Feb 2021 10:01:53 -0300
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Bas Mevissen 
Cc: Andrey Zhizhikin , Otavio Salvador , 
	Terry Barnaby , meta-freescale@lists.yoctoproject.org
Content-Type: text/plain; charset="UTF-8"

Hi Bas,

On Thu, Feb 25, 2021 at 9:55 AM Bas Mevissen  wrote:

> Fabio said "mainline". I'm not sure whether meant linux-fslc (as Otavio
> used it) or kernel.org.
> So I wanted to check that.

imx6 has decent graphics support in the mainline kernel via the
Etnaviv driver. Userspace is standard Mesa, with no binary blobs
involved.
VPU is supported by the coda driver and the standard Gstreamer packages.

By mainline, I do mean a "kernel.org" based kernel.

linux-fslc uses the stable tree from "kernel.org" as the base and add
additional patch on top.

Hope that clarifies things.

Cheers

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.51])
 by mx.groups.io with SMTP id smtpd.web10.10904.1614258260994383586
 for ;
 Thu, 25 Feb 2021 05:04:21 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=s/d+oZEi;
 spf=pass (domain: gmail.com, ip: 209.85.167.51, mailfrom: andrey.z@gmail.com)
Received: by mail-lf1-f51.google.com with SMTP id e7so8481255lft.2
        for ; Thu, 25 Feb 2021 05:04:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc:content-transfer-encoding;
        bh=5VsdEDKXpg2NIo+84TiPBUvtyV9T1Xfu2F+QVw+c8Ss=;
        b=s/d+oZEibO6dPvuQKRV6Z3bmK/WKU9/rz9JaCnQHUXA2aCil33WgOUfl7y/fWz1v9a
         gtWFtq7AAkD1/cKqCl+dmZURPFQskAVpygg8O6QL1fkADopECv/GdLVO/Lwm+6mrlEpx
         XaKA2mQv5vZI+AD410PgzyYB9jPKLVybJQtq001EB8oHlt5rIFD6hTumV/d/J3867PYW
         GMJ6oI2usTv6aZGLC//99OHNXyG73C9VmxHu2gwrXhZ9BDZYqDDU37aQtJgCh9MNZV8G
         7e60qXztVGlbTQ9QVqCy0zSE84AHqzz7sk1JbFGkZqIky0v+wpkETY50s5d5/7sowAs3
         8ThA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc:content-transfer-encoding;
        bh=5VsdEDKXpg2NIo+84TiPBUvtyV9T1Xfu2F+QVw+c8Ss=;
        b=H0qewKdGGZTn7uOhU8xzqSiMbtQxKnGi8r1BvCNe1Wa5XS0FyFmCPaP/Oh2TryglIj
         zbXy2Dpz2QcHDzKVzT2NdCX6Gc5+lMD9JQpuAvRJbk20u/doCxqms536CesvOcZi33xb
         y4DVHlIzpNbaTQLH6kf9J2MCjpZ2zd5WdfhPHmTfuKI9D7HW+7jHf/pJhh7uZ6UopvJ7
         C0GSkv3FK76pM7FW015Sj7eLgSCc6Xy9jM0LQDBE4Ged6jl49TQwQMgUrpGoLLHQpjMM
         0Jhf0Ph3HAe5Y8hxz2m5djpkgJ8s5YgDClRio503Cn5tdRdn2/bMP33AlmON6vPXi3qc
         Iueg==
X-Gm-Message-State: AOAM532jPxYx7v7mTdAIpneYIOP+kS0pJoZXatVII4MRQoxPN9NCulEJ
	IhuGXK0Vqdyn9/zLzLRCWMd1wJOMxNtKrWGFiL8=
X-Google-Smtp-Source: ABdhPJyd+mrleGQecXbNyEgufvrkXrUcADexNufLDyEjvT8wq58CmI7kjf8FIaZja+qQao0Cxw/1oEK0qQnHyG3TSDc=
X-Received: by 2002:a05:6512:33c2:: with SMTP id d2mr1924449lfg.429.1614258259240;
 Thu, 25 Feb 2021 05:04:19 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk> 
 <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl> 
 <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl>
In-Reply-To: <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl>
From: "Andrey Zhizhikin" 
Date: Thu, 25 Feb 2021 14:04:07 +0100
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Bas Mevissen 
Cc: Otavio Salvador , Terry Barnaby , 
	meta-freescale@lists.yoctoproject.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 25, 2021 at 1:55 PM Bas Mevissen  wrote:
>
> On 2021-02-25 13:32, Andrey Zhizhikin wrote:
> > Hello Bas,
> >
> > On Thu, Feb 25, 2021 at 1:18 PM Bas Mevissen 
> > wrote:
> >>
> >> On 2021-02-25 12:21, Otavio Salvador wrote:
> >> > Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
> >> >  escreveu:
> >> >>  From what I am seeing I will have to use a NXP fsl-* based
> >> >> distribution
> >> >> to support the imx hardware video processing features. I have built
> >> >> such
> >> >> a distro with both linux-fslc-imx and limux-imx kernels (I think!) =
for
> >> >> the Wandboard, which boots and runs but the HDMI display was not
> >> >> functional. I will persevere looking at that.
> >> >
> >> > No, you don't. You can use linux-fslc (mainline) and fslc-* distros =
as
> >> > i.MX6 has full mainline support. At O.S. Systems we have been using
> >> > Linux mainline with many customers with great success.
> >> >
> >>
> >> Wouldn't make sense to first evaluate the performance of the platform
> >> (as Terry plans to do) first on an NXP fsl-* distro? In that case one
> >> can get direct support from NXP if required. After that, derive your
> >> own
> >> distro from fslc-*.
> >
> > This might not be quite indicative, as the NXP kernel might have some
> > "shortcuts" to boost performance in certain areas, sacrificing
> > conformance of the source code.
> >
>
> At least you get an idea of what the HW platform can do.
>
> > You might experience the situation that video performs quite well, but
> > then after opting for NXP kernel - you might find that some other
> > areas are not working as expected (some other domains). This would put
> > you in a situation that you've already committed to choose and deploy
> > the NXP-based BSP and would leave you to solve the issues in those
> > domains on your own efforts.
> >
> > This is my pure speculation here, so take it with a grain of salt
> > though. :)
> >
> IMHO, you should never base your *product* on FSL. It is (at least, that
> is what was told me by (then) Freescale field engineers) only there to
> demonstrate the platform. Maybe that has changed over time.

That is exactly what I implied, below statement is about that.

>
> When there is a huge performance difference between fsl and fslc, it
> needs to be resolved.

By whom? This would lead to a situation that community does not take
responsibility for NXP and visa-versa. In this case - I have a bad
feeling that the engineering team in the company that decided to use
one flavor or another would be dealing with this fact. And this is
what I've also described as potential outcome.

>
> > IMHO, this should be considered and before the final product receives
> > commitment to use either of BSP flavors - all areas should be
> > validated, not only the performance aspects of Multimedia domain.
> >
>
> Yes, when you have decided on the hardware to use. If you are evaluating
> the hardware to see whether it meets your requirements, you might want
> to take the option that gives you the best impression of the performance
> that can be achieved without too much of a hassle.
> (it is an important step to do, at a stage of the development where time
> is usually very limited, so you want a quick but reliable result).

Correct, fully agree here.

>
> >>
> >> BTW Would kernel.org stable kernel work as well on i.MX6 if you need
> >> graphics and video? I used it successfully for headless IOT
> >> applications.
> >
> > As Fabio already indicated - this is possible.
> >
>
> Fabio said "mainline". I'm not sure whether meant linux-fslc (as Otavio
> used it) or kernel.org.

In this sense, linux-fslc *is* de-facto the kernel provided from
kernel.org. It has a handful of patched that are not in upstream:

$ git log --no-merges --oneline stable-git/linux-5.10.y..5.10.x+fslc
2b929f3dcf6c media: coda: Change firmware probing order
dacfb877023a ARM: imx: add smp support for imx7d
10c7ebc67e34 drivers, misc: add U-Boot bootcount driver
67ea92db430f fec: Add disable_giga parameter to force 10/100 operation
bc552ba32d60 MA-7633-2 [Android-Reboot]reboot to fastboot\recovery mode
695186a85a0d ARM: imx: add cpu_is_imx6() routine

> So I wanted to check that.
>
> >>
> >> Bas.
> >>
> >
> > --
> > Regards,
> > Andrey.
> >
> >

--
Regards,
Andrey.

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from hosting.emcodev.net (hosting.emcodev.net [178.18.92.162])
 by mx.groups.io with SMTP id smtpd.web11.10858.1614258727470609629
 for ;
 Thu, 25 Feb 2021 05:12:08 -0800
Authentication-Results: mx.groups.io;
 dkim=fail reason="signature has expired" header.i=@basmevissen.nl header.s=default header.b=oDP70FG6;
 spf=pass (domain: basmevissen.nl, ip: 178.18.92.162, mailfrom: abuse@basmevissen.nl)
Received: from localhost (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id 6293D212011;
	Thu, 25 Feb 2021 14:12:04 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=basmevissen.nl;
	 h=message-id:user-agent:references:in-reply-to:subject:subject
	:from:from:date:date:content-transfer-encoding:content-type
	:content-type:mime-version; s=default; t=1614258721; x=
	1616073122; bh=XpypMqlrBN0mb4CMq0IKsJC5m/QxkbJvDAqM5KN2jjg=; b=o
	DP70FG6PAfrHE+oB4leFpWw4QXfqLvAur/1buQO93eoHsUzWlw6pjl7Z0NNm1a6B
	YMO1gNlHjiYtDd7UMEWMBnmUrLAXabmtYQbJxnQCsalu+0hnEPL+0HbUP+p9Zjay
	5zD5dOgwdX2n9wABe8OSILJ3bmmFZJESnZqKWn4vOsugHGJK+Y/pHhQuTbGvx4De
	IiZ5oacao/ttWgfuf9AC7IDhz5ezzcLsN2CniqEc/gA6cO3TqRDZ9MwoE3B/AooH
	+POOARI3hnBzjGq/jNuf6SRSvYTUB1Z1X5F/yXqrAgnH4PD81R/QNiaEOouHO60g
	UR4awdns1owDFddoWzstQKBm8GvAM5zxG7dkdBmizg6tJZNYSUbL2s7fY+XplB05
	4n7rEeH8lHaafFdUTCTR+6qfF1Hy/d5fCXpmyhc2AffRINys1KvFJ2qdYu09Jn4+
	CeqlrMHoaZZ7okPQ7gi8C5f9ZdqDTwu6NrZGv5+a1XI2Zjq3FDS3zC599htz6fnu
	fqoUjalYZfntzPtGNwQ/ibEfJZzemjQifYoKYRCddgszbo7ClmmPg4IhhnHCugKm
	3PSKcbZC4WN5szaQGD9dGKAqofrGPcgLmXeJRY2xYhqEP3Az/MLXhL8zzc/WNQM7
	eBlJbsNHdGkbFWVmwycRGSsj3VU6klRehFJuzq+LxA=
Received: from hosting.emcodev.net ([127.0.0.1])
	by localhost (hosting.emcodev.net [127.0.0.1]) (amavisd-new, port 10026)
	with LMTP id XqmrZ8n5JgMb; Thu, 25 Feb 2021 14:12:01 +0100 (CET)
Received: from emcodev.nl (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id CDEC121200B;
	Thu, 25 Feb 2021 14:12:01 +0100 (CET)
MIME-Version: 1.0
Date: Thu, 25 Feb 2021 14:12:01 +0100
From: "Bas Mevissen" 
To: Fabio Estevam 
Cc: Andrey Zhizhikin , Otavio Salvador
 , Terry Barnaby ,
 meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
In-Reply-To: 
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk>
 
 <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl>
 
 <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl>
 
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <4264cb03bfe5f821e5052b4753658372@basmevissen.nl>
X-Sender: abuse@basmevissen.nl
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit

On 2021-02-25 14:01, Fabio Estevam wrote:
> Hi Bas,
> 
> On Thu, Feb 25, 2021 at 9:55 AM Bas Mevissen  
> wrote:
> 
>> Fabio said "mainline". I'm not sure whether meant linux-fslc (as 
>> Otavio
>> used it) or kernel.org.
>> So I wanted to check that.
> 
> imx6 has decent graphics support in the mainline kernel via the
> Etnaviv driver. Userspace is standard Mesa, with no binary blobs
> involved.
> VPU is supported by the coda driver and the standard Gstreamer 
> packages.
> 
> By mainline, I do mean a "kernel.org" based kernel.
> 
> linux-fslc uses the stable tree from "kernel.org" as the base and add
> additional patch on top.
> 

Ah yes, I see. Linux-fslc is now really up to date with kernel.org. I 
recall (from 2017 era) that that was different. Maybe I'm wrong about 
that.

> Hope that clarifies things.
> 
Yes, thanks for the explanation.

Bas.

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from hosting.emcodev.net (hosting.emcodev.net [178.18.92.162])
 by mx.groups.io with SMTP id smtpd.web12.11206.1614259351007308493
 for ;
 Thu, 25 Feb 2021 05:22:32 -0800
Authentication-Results: mx.groups.io;
 dkim=fail reason="signature has expired" header.i=@basmevissen.nl header.s=default header.b=PceLYPkT;
 spf=pass (domain: basmevissen.nl, ip: 178.18.92.162, mailfrom: abuse@basmevissen.nl)
Received: from localhost (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id 2EE5F212011;
	Thu, 25 Feb 2021 14:22:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=basmevissen.nl;
	 h=message-id:user-agent:references:in-reply-to:subject:subject
	:from:from:date:date:content-transfer-encoding:content-type
	:content-type:mime-version; s=default; t=1614259339; x=
	1616073740; bh=UsSNimSQerma+bnoqNXRT1Dw2gmxBjEN4Lx9B3Sz/4M=; b=P
	ceLYPkTe6slVhsIgXArGFTRMNk/gezDEeh2yC7/1DaBBqK+Btdk3EQrXSIfr03dx
	SZudGU/zdnRl7uh5Bu5nPA89K/35G2yirM7Kk4i8jl6YtiubJG7UpgNcX0DSZobI
	VRUx+s2NhvbD6S9JsovS6XuYXjs9pwJruH00EVyYVGkjy6iukBrMbjFnFALUeo2X
	Ne4iDJJKQR4+lgbvmRI2TBToj2/MTpzN9Ih7sxE/YaVmkny46CGZuRjPZ9NGJCo0
	3Wp4dAeFMv1auzf+czqEYxhyUax8ebB06VojBz9R6mEshY7Sf7BPbivSgTWXoWQl
	VyVL2pUGpvf8EThds0fTECnCzfESeX4ZZREtUNxrtma92sYyLgH3ljZD2WrqFKjt
	5do8sYPRYrSxmNKPZ6rLswUF6Zte20+BD4bzfI94/pOIxVFV1wu1jviVDOxoo6I0
	jfPuJ1k2O+oXc9w51Zx5DKwpBeEfZaLtz7TyImCSCvO+szIGuWXojeUPjSKSP9O8
	5HM1ziGj5qJkIxyFXJprfRylAuHyRu2bw85L9Df8jqIqxXxYomo9m05uaoG2wgpk
	BmDfUQm7hdhZzQCi1/31fiD2hHjQ9KeRggk7TBpW3+c/F0nm4DMNcRQoF2MRm0ML
	YzyoO5aGEAHM9040iZiyDa4pJJ1fW5PrJEx8KVz57M=
Received: from hosting.emcodev.net ([127.0.0.1])
	by localhost (hosting.emcodev.net [127.0.0.1]) (amavisd-new, port 10026)
	with LMTP id SvSX4xjDPqLU; Thu, 25 Feb 2021 14:22:19 +0100 (CET)
Received: from emcodev.nl (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id 18C4321200B;
	Thu, 25 Feb 2021 14:22:19 +0100 (CET)
MIME-Version: 1.0
Date: Thu, 25 Feb 2021 14:22:19 +0100
From: "Bas Mevissen" 
To: Andrey Zhizhikin 
Cc: Otavio Salvador , Terry Barnaby
 , meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
In-Reply-To: 
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk>
 
 <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl>
 
 <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl>
 
User-Agent: Roundcube Webmail/1.4.11
Message-ID: 
X-Sender: abuse@basmevissen.nl
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: quoted-printable

On 2021-02-25 14:04, Andrey Zhizhikin wrote:
> On Thu, Feb 25, 2021 at 1:55 PM Bas Mevissen =20
> wrote:
>>=20
>> On 2021-02-25 13:32, Andrey Zhizhikin wrote:
>> > Hello Bas,
>> >
>> > On Thu, Feb 25, 2021 at 1:18 PM Bas Mevissen 
>> > wrote:
>> >>
>> >> On 2021-02-25 12:21, Otavio Salvador wrote:
>> >> > Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
>> >> >  escreveu:
>> >> >>  From what I am seeing I will have to use a NXP fsl-* based
>> >> >> distribution
>> >> >> to support the imx hardware video processing features. I have bu=
ilt
>> >> >> such
>> >> >> a distro with both linux-fslc-imx and limux-imx kernels (I think=
!) for
>> >> >> the Wandboard, which boots and runs but the HDMI display was not
>> >> >> functional. I will persevere looking at that.
>> >> >
>> >> > No, you don't. You can use linux-fslc (mainline) and fslc-* distr=
os as
>> >> > i.MX6 has full mainline support. At O.S. Systems we have been usi=
ng
>> >> > Linux mainline with many customers with great success.
>> >> >
>> >>
>> >> Wouldn't make sense to first evaluate the performance of the platfo=
rm
>> >> (as Terry plans to do) first on an NXP fsl-* distro? In that case o=
ne
>> >> can get direct support from NXP if required. After that, derive you=
r
>> >> own
>> >> distro from fslc-*.
>> >
>> > This might not be quite indicative, as the NXP kernel might have som=
e
>> > "shortcuts" to boost performance in certain areas, sacrificing
>> > conformance of the source code.
>> >
>>=20
>> At least you get an idea of what the HW platform can do.
>>=20
>> > You might experience the situation that video performs quite well, b=
ut
>> > then after opting for NXP kernel - you might find that some other
>> > areas are not working as expected (some other domains). This would p=
ut
>> > you in a situation that you've already committed to choose and deplo=
y
>> > the NXP-based BSP and would leave you to solve the issues in those
>> > domains on your own efforts.
>> >
>> > This is my pure speculation here, so take it with a grain of salt
>> > though. :)
>> >
>> IMHO, you should never base your *product* on FSL. It is (at least,=20
>> that
>> is what was told me by (then) Freescale field engineers) only there to
>> demonstrate the platform. Maybe that has changed over time.
>=20
> That is exactly what I implied, below statement is about that.
>=20
Ok, I missed that obviously.

>>=20
>> When there is a huge performance difference between fsl and fslc, it
>> needs to be resolved.
>=20
> By whom? This would lead to a situation that community does not take
> responsibility for NXP and visa-versa. In this case - I have a bad
> feeling that the engineering team in the company that decided to use
> one flavor or another would be dealing with this fact. And this is
> what I've also described as potential outcome.
>=20

It is actually that interaction between the community and NXP that has=20
brought i.MX support at the level it has. So if a performance problem=20
might pop up, it is that same combination that can and will work=20
together to get it resolved. It is to the company/person who found the=20
issue to bring it up (here) and not to resolve it as that requires=20
capabilities that are not so widespread.

>>=20
>> > IMHO, this should be considered and before the final product receive=
s
>> > commitment to use either of BSP flavors - all areas should be
>> > validated, not only the performance aspects of Multimedia domain.
>> >
>>=20
>> Yes, when you have decided on the hardware to use. If you are=20
>> evaluating
>> the hardware to see whether it meets your requirements, you might want
>> to take the option that gives you the best impression of the=20
>> performance
>> that can be achieved without too much of a hassle.
>> (it is an important step to do, at a stage of the development where=20
>> time
>> is usually very limited, so you want a quick but reliable result).
>=20
> Correct, fully agree here.
>=20
>>=20
>> >>
>> >> BTW Would kernel.org stable kernel work as well on i.MX6 if you nee=
d
>> >> graphics and video? I used it successfully for headless IOT
>> >> applications.
>> >
>> > As Fabio already indicated - this is possible.
>> >
>>=20
>> Fabio said "mainline". I'm not sure whether meant linux-fslc (as=20
>> Otavio
>> used it) or kernel.org.
>=20
> In this sense, linux-fslc *is* de-facto the kernel provided from
> kernel.org. It has a handful of patched that are not in upstream:
>=20
> $ git log --no-merges --oneline stable-git/linux-5.10.y..5.10.x+fslc
> 2b929f3dcf6c media: coda: Change firmware probing order
> dacfb877023a ARM: imx: add smp support for imx7d
> 10c7ebc67e34 drivers, misc: add U-Boot bootcount driver
> 67ea92db430f fec: Add disable_giga parameter to force 10/100 operation
> bc552ba32d60 MA-7633-2 [Android-Reboot]reboot to fastboot\recovery mode
> 695186a85a0d ARM: imx: add cpu_is_imx6() routine
>=20
>> So I wanted to check that.
>>=20
And that worked out brilliantly :-)
(thanks, see my response to Fabio on the same subject as well)

>> >>
>> >> Bas.
>> >>
>> >
>> > --
>> > Regards,
>> > Andrey.
>> >
>> >
>=20
> --
> Regards,
> Andrey.

Regards,

Bas.

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-lf1-f43.google.com (mail-lf1-f43.google.com [209.85.167.43])
 by mx.groups.io with SMTP id smtpd.web09.11466.1614261649355884554
 for ;
 Thu, 25 Feb 2021 06:00:49 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=OEd9ENsR;
 spf=pass (domain: gmail.com, ip: 209.85.167.43, mailfrom: andrey.z@gmail.com)
Received: by mail-lf1-f43.google.com with SMTP id h125so8677766lfd.7
        for ; Thu, 25 Feb 2021 06:00:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc:content-transfer-encoding;
        bh=8Iss20er/GVqpWxQOm7fztYKp3kTu0+/WX9CKpaQJEo=;
        b=OEd9ENsRlNm8UznCmjcCYa3PNBwk+mYo5tm91rdDXG4l7eC1827X/6Bz7I2jxfbeCd
         MXlGmqNXhuhrEUlqe/2fNTH0pXtka0ZTyZh/mVrBGOxZS6Uk7uxJFmIMUvCYSQgnMKfL
         41DeCxAS/8Q3WB14TuaW+nhQYW6WqIYDVwU60+6G/J3NqtLPcUE1rfoGoi0aARLb1+yi
         ePjZl/utNokKayP+u5Rolv+mkhEhakLic9jH0bjdiZDcxqQq9o4JmvWfmpIa1X4HG17k
         hAyjUvsJQjCkDzseQmgrv4Pm6LERv0wfSBoG3bm4kTC5oEg8fTcuLCaroPVfKG4zwBZQ
         4nvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc:content-transfer-encoding;
        bh=8Iss20er/GVqpWxQOm7fztYKp3kTu0+/WX9CKpaQJEo=;
        b=XxcNB7SMvFjCYHMjGDMDi2nyZLdP4IdEgluuLD7hzFfmrCitoHgMMpm8xeoEX+ZNM6
         eEv5NPfyxMv5Ru/hArQ/kyWlaZQYkKlSE/bM20yoGdEIFekbFXmgp5ueSQi+23t9YL88
         17n5anRwhGR9HqIDMLDGm482BYYHKMRwi6z7pRbq1n0edatEeahw3iuATm6KbgIoCjBE
         x9cg3U1fVDH1CDvYM6JYpAAQjQHrnKOhwrzrdGdZhmKRVUIGaGA8m/OijqXgArxm1hzO
         dY1xFVtwIwjzFotEPHovKqwdyMWfKMpPsMIkyLo9HAVY/tdCuG1/maPnY2bxyW9RSniW
         lrLA==
X-Gm-Message-State: AOAM5330ZRGykUw1tjhM6wfxb606pAVkc3zlqNK5hkdwlQixj6+N4+YZ
	FWnuR4Qx36LBUQseuCWUNnS6cbW1K8ZnuVWFl6M=
X-Google-Smtp-Source: ABdhPJyqOE7U2kra9UYsWam8AclefDmn8jiifVg7rNuYj+x1pFECvfipRXxvNk6eAZuPdqdwHUUF0m6IH5FEnzKh8U8=
X-Received: by 2002:a19:f713:: with SMTP id z19mr2065393lfe.50.1614261647277;
 Thu, 25 Feb 2021 06:00:47 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk> 
 <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl> 
 <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl> 
 
In-Reply-To: 
From: "Andrey Zhizhikin" 
Date: Thu, 25 Feb 2021 15:00:35 +0100
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Bas Mevissen 
Cc: Otavio Salvador , Terry Barnaby , 
	meta-freescale@lists.yoctoproject.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 25, 2021 at 2:22 PM Bas Mevissen  wrote:
>
> On 2021-02-25 14:04, Andrey Zhizhikin wrote:
> > On Thu, Feb 25, 2021 at 1:55 PM Bas Mevissen 
> > wrote:
> >>
> >> On 2021-02-25 13:32, Andrey Zhizhikin wrote:
> >> > Hello Bas,
> >> >
> >> > On Thu, Feb 25, 2021 at 1:18 PM Bas Mevissen 
> >> > wrote:
> >> >>
> >> >> On 2021-02-25 12:21, Otavio Salvador wrote:
> >> >> > Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
> >> >> >  escreveu:
> >> >> >>  From what I am seeing I will have to use a NXP fsl-* based
> >> >> >> distribution
> >> >> >> to support the imx hardware video processing features. I have bu=
ilt
> >> >> >> such
> >> >> >> a distro with both linux-fslc-imx and limux-imx kernels (I think=
!) for
> >> >> >> the Wandboard, which boots and runs but the HDMI display was not
> >> >> >> functional. I will persevere looking at that.
> >> >> >
> >> >> > No, you don't. You can use linux-fslc (mainline) and fslc-* distr=
os as
> >> >> > i.MX6 has full mainline support. At O.S. Systems we have been usi=
ng
> >> >> > Linux mainline with many customers with great success.
> >> >> >
> >> >>
> >> >> Wouldn't make sense to first evaluate the performance of the platfo=
rm
> >> >> (as Terry plans to do) first on an NXP fsl-* distro? In that case o=
ne
> >> >> can get direct support from NXP if required. After that, derive you=
r
> >> >> own
> >> >> distro from fslc-*.
> >> >
> >> > This might not be quite indicative, as the NXP kernel might have som=
e
> >> > "shortcuts" to boost performance in certain areas, sacrificing
> >> > conformance of the source code.
> >> >
> >>
> >> At least you get an idea of what the HW platform can do.
> >>
> >> > You might experience the situation that video performs quite well, b=
ut
> >> > then after opting for NXP kernel - you might find that some other
> >> > areas are not working as expected (some other domains). This would p=
ut
> >> > you in a situation that you've already committed to choose and deplo=
y
> >> > the NXP-based BSP and would leave you to solve the issues in those
> >> > domains on your own efforts.
> >> >
> >> > This is my pure speculation here, so take it with a grain of salt
> >> > though. :)
> >> >
> >> IMHO, you should never base your *product* on FSL. It is (at least,
> >> that
> >> is what was told me by (then) Freescale field engineers) only there to
> >> demonstrate the platform. Maybe that has changed over time.
> >
> > That is exactly what I implied, below statement is about that.
> >
> Ok, I missed that obviously.
>
> >>
> >> When there is a huge performance difference between fsl and fslc, it
> >> needs to be resolved.
> >
> > By whom? This would lead to a situation that community does not take
> > responsibility for NXP and visa-versa. In this case - I have a bad
> > feeling that the engineering team in the company that decided to use
> > one flavor or another would be dealing with this fact. And this is
> > what I've also described as potential outcome.
> >
>
> It is actually that interaction between the community and NXP that has
> brought i.MX support at the level it has. So if a performance problem
> might pop up, it is that same combination that can and will work
> together to get it resolved. It is to the company/person who found the
> issue to bring it up (here) and not to resolve it as that requires
> capabilities that are not so widespread.

In ideal situation - that would be a way to go. But in this case I
would expect that all patches that are present in NXP kernel tree are
posted upstream, so there would be no deviation and hence - no
performance differences between NXP and upstream kernels.

Of course, the problem when found - can be reported, but (a) I do not
believe that this list is a proper destination for such issues, as it
discuss the OE and not kernel-specific performance issues; and (b)
regressions can come from any side (NXP or upstream), which makes it
harder to bisect which side to be looked at.

I'm not saying that this is an impossible thing to solve, but in
reality the vast majority of efforts to solve those issues are landing
up at the side of those persons who've discovered them in the first
place.

This is all my point of view on the subject, and might deviate on a
case-by-case basis.

>
> >>
> >> > IMHO, this should be considered and before the final product receive=
s
> >> > commitment to use either of BSP flavors - all areas should be
> >> > validated, not only the performance aspects of Multimedia domain.
> >> >
> >>
> >> Yes, when you have decided on the hardware to use. If you are
> >> evaluating
> >> the hardware to see whether it meets your requirements, you might want
> >> to take the option that gives you the best impression of the
> >> performance
> >> that can be achieved without too much of a hassle.
> >> (it is an important step to do, at a stage of the development where
> >> time
> >> is usually very limited, so you want a quick but reliable result).
> >
> > Correct, fully agree here.
> >
> >>
> >> >>
> >> >> BTW Would kernel.org stable kernel work as well on i.MX6 if you nee=
d
> >> >> graphics and video? I used it successfully for headless IOT
> >> >> applications.
> >> >
> >> > As Fabio already indicated - this is possible.
> >> >
> >>
> >> Fabio said "mainline". I'm not sure whether meant linux-fslc (as
> >> Otavio
> >> used it) or kernel.org.
> >
> > In this sense, linux-fslc *is* de-facto the kernel provided from
> > kernel.org. It has a handful of patched that are not in upstream:
> >
> > $ git log --no-merges --oneline stable-git/linux-5.10.y..5.10.x+fslc
> > 2b929f3dcf6c media: coda: Change firmware probing order
> > dacfb877023a ARM: imx: add smp support for imx7d
> > 10c7ebc67e34 drivers, misc: add U-Boot bootcount driver
> > 67ea92db430f fec: Add disable_giga parameter to force 10/100 operation
> > bc552ba32d60 MA-7633-2 [Android-Reboot]reboot to fastboot\recovery mode
> > 695186a85a0d ARM: imx: add cpu_is_imx6() routine
> >
> >> So I wanted to check that.
> >>
> And that worked out brilliantly :-)
> (thanks, see my response to Fabio on the same subject as well)
>
> >> >>
> >> >> Bas.
> >> >>
> >> >
> >> > --
> >> > Regards,
> >> > Andrey.
> >> >
> >> >
> >
> > --
> > Regards,
> > Andrey.
>
> Regards,
>
> Bas.



--=20
Regards,
Andrey.

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42])
 by mx.groups.io with SMTP id smtpd.web12.7085.1614332209897957701
 for ;
 Fri, 26 Feb 2021 01:36:50 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=OANUAvsr;
 spf=pass (domain: gmail.com, ip: 209.85.167.42, mailfrom: eremenok.k.by@gmail.com)
Received: by mail-lf1-f42.google.com with SMTP id d3so12874963lfg.10
        for ; Fri, 26 Feb 2021 01:36:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=KSHg9SCXBpD1JcxarZAybJaddNEsEWMZ1Fhp0Xp0YgI=;
        b=OANUAvsrqDoLqFU2R1PXD1p2cOsaK8h3ZZX4QJee++p18oifxtxxZvoGZv+/pmwQSj
         Gu1dxDdWLBg/VzDaLDL5GF0qvjXulkcvnmVn0RGawAKGmM4eBfsJT1rYoBQnL14eLc+z
         FkQi7btgohDcwR4FmdxSx7bx2jJuTCxbiN1+0pELujF/2971zQT24Zmq6m7pYvs6l5Nr
         SEGKpOhXK5vlZrhyqmlZG08gD6bWBm2+fM4qbTQwQeSZp5zPvEuuOOSCb6MFQDaM2b8h
         vF1zJMbYYsjxM1lRDkA5jCgkHkWqTJUSRfFb4WriA+DsYrrU9sDj5YBPgimxt0+TMRgD
         YVGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=KSHg9SCXBpD1JcxarZAybJaddNEsEWMZ1Fhp0Xp0YgI=;
        b=DDqinkpapHr01XlnBYmB966K7Kbm+f/caz9RpjTGwWYRATcCaPlsN/end/UfZIvDH0
         WWpxC8h6ewkqbVAPZT5EGxJIG0NEwQssmZUc7VMN1iN+vAVh4olvVhqUddW+Z8U5ZLc/
         j/ENZ77nhjJ2RUwK1PWnuTHZwHPZ2tpJkhoKhWFKb/LvvNYwWRERKwy2lLR9FOJOxNiR
         wfFgDDnTQktZz/wkzHlBZ2raEHYxShVXVpVVfLqDn5gysVV6Plm7NvXIBZ8eYl2uzYE8
         RkuUFgdlxMSbamfmu5nKCk+MmJp6uxuLH6ERIBlITzafy+q59C5Nns2Mq/oJ30va1dLY
         ZCWg==
X-Gm-Message-State: AOAM532BePLcNjVjxRsAaQGuK4gC7825pFEEGZdtcTn/HtbaX6256kLD
	9eal9H91xSd7jqZL3P0UgEly5aD5vTzXgHZbCoE=
X-Google-Smtp-Source: ABdhPJxM3Desq3icLDjODQ4HmY9qz/+WIGWGiMt9CsF2euKACTEtxVDrEP3Kw1wtqd3xAvlm+CwdfYguu5QAFZmIfwM=
X-Received: by 2002:ac2:42d1:: with SMTP id n17mr1275211lfl.76.1614332207896;
 Fri, 26 Feb 2021 01:36:47 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk> 
 <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl> 
 <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl> 
  
In-Reply-To: 
From: eremenok.k.by@gmail.com
Date: Fri, 26 Feb 2021 12:36:37 +0300
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Andrey Zhizhikin 
Cc: Bas Mevissen , 
	Otavio Salvador , Terry Barnaby , 
	meta-freescale@lists.yoctoproject.org
Content-Type: multipart/alternative; boundary="000000000000cd1ce405bc3a01ca"

--000000000000cd1ce405bc3a01ca
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, there.
I see here a lot of specialists. Some qestions.
1. What kernel (community or non-community) would you take for your own
board (not NXP, not O.S.)?
2. I took the branch origin/imx_4.14.98_2.0.0_ga. Is it a
community supported branch?

=D1=87=D1=82, 25 =D1=84=D0=B5=D0=B2=D1=80. 2021 =D0=B3. =D0=B2 17:00, Andr=
ey Zhizhikin :

> On Thu, Feb 25, 2021 at 2:22 PM Bas Mevissen  wrot=
e:
> >
> > On 2021-02-25 14:04, Andrey Zhizhikin wrote:
> > > On Thu, Feb 25, 2021 at 1:55 PM Bas Mevissen 
> > > wrote:
> > >>
> > >> On 2021-02-25 13:32, Andrey Zhizhikin wrote:
> > >> > Hello Bas,
> > >> >
> > >> > On Thu, Feb 25, 2021 at 1:18 PM Bas Mevissen 
> > >> > wrote:
> > >> >>
> > >> >> On 2021-02-25 12:21, Otavio Salvador wrote:
> > >> >> > Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
> > >> >> >  escreveu:
> > >> >> >>  From what I am seeing I will have to use a NXP fsl-* based
> > >> >> >> distribution
> > >> >> >> to support the imx hardware video processing features. I have
> built
> > >> >> >> such
> > >> >> >> a distro with both linux-fslc-imx and limux-imx kernels (I
> think!) for
> > >> >> >> the Wandboard, which boots and runs but the HDMI display was =
not
> > >> >> >> functional. I will persevere looking at that.
> > >> >> >
> > >> >> > No, you don't. You can use linux-fslc (mainline) and fslc-*
> distros as
> > >> >> > i.MX6 has full mainline support. At O.S. Systems we have been
> using
> > >> >> > Linux mainline with many customers with great success.
> > >> >> >
> > >> >>
> > >> >> Wouldn't make sense to first evaluate the performance of the
> platform
> > >> >> (as Terry plans to do) first on an NXP fsl-* distro? In that cas=
e
> one
> > >> >> can get direct support from NXP if required. After that, derive
> your
> > >> >> own
> > >> >> distro from fslc-*.
> > >> >
> > >> > This might not be quite indicative, as the NXP kernel might have
> some
> > >> > "shortcuts" to boost performance in certain areas, sacrificing
> > >> > conformance of the source code.
> > >> >
> > >>
> > >> At least you get an idea of what the HW platform can do.
> > >>
> > >> > You might experience the situation that video performs quite well=
,
> but
> > >> > then after opting for NXP kernel - you might find that some other
> > >> > areas are not working as expected (some other domains). This woul=
d
> put
> > >> > you in a situation that you've already committed to choose and
> deploy
> > >> > the NXP-based BSP and would leave you to solve the issues in thos=
e
> > >> > domains on your own efforts.
> > >> >
> > >> > This is my pure speculation here, so take it with a grain of salt
> > >> > though. :)
> > >> >
> > >> IMHO, you should never base your *product* on FSL. It is (at least,
> > >> that
> > >> is what was told me by (then) Freescale field engineers) only there=
 to
> > >> demonstrate the platform. Maybe that has changed over time.
> > >
> > > That is exactly what I implied, below statement is about that.
> > >
> > Ok, I missed that obviously.
> >
> > >>
> > >> When there is a huge performance difference between fsl and fslc, i=
t
> > >> needs to be resolved.
> > >
> > > By whom? This would lead to a situation that community does not take
> > > responsibility for NXP and visa-versa. In this case - I have a bad
> > > feeling that the engineering team in the company that decided to use
> > > one flavor or another would be dealing with this fact. And this is
> > > what I've also described as potential outcome.
> > >
> >
> > It is actually that interaction between the community and NXP that has
> > brought i.MX support at the level it has. So if a performance problem
> > might pop up, it is that same combination that can and will work
> > together to get it resolved. It is to the company/person who found the
> > issue to bring it up (here) and not to resolve it as that requires
> > capabilities that are not so widespread.
>
> In ideal situation - that would be a way to go. But in this case I
> would expect that all patches that are present in NXP kernel tree are
> posted upstream, so there would be no deviation and hence - no
> performance differences between NXP and upstream kernels.
>
> Of course, the problem when found - can be reported, but (a) I do not
> believe that this list is a proper destination for such issues, as it
> discuss the OE and not kernel-specific performance issues; and (b)
> regressions can come from any side (NXP or upstream), which makes it
> harder to bisect which side to be looked at.
>
> I'm not saying that this is an impossible thing to solve, but in
> reality the vast majority of efforts to solve those issues are landing
> up at the side of those persons who've discovered them in the first
> place.
>
> This is all my point of view on the subject, and might deviate on a
> case-by-case basis.
>
> >
> > >>
> > >> > IMHO, this should be considered and before the final product
> receives
> > >> > commitment to use either of BSP flavors - all areas should be
> > >> > validated, not only the performance aspects of Multimedia domain.
> > >> >
> > >>
> > >> Yes, when you have decided on the hardware to use. If you are
> > >> evaluating
> > >> the hardware to see whether it meets your requirements, you might w=
ant
> > >> to take the option that gives you the best impression of the
> > >> performance
> > >> that can be achieved without too much of a hassle.
> > >> (it is an important step to do, at a stage of the development where
> > >> time
> > >> is usually very limited, so you want a quick but reliable result).
> > >
> > > Correct, fully agree here.
> > >
> > >>
> > >> >>
> > >> >> BTW Would kernel.org stable kernel work as well on i.MX6 if you
> need
> > >> >> graphics and video? I used it successfully for headless IOT
> > >> >> applications.
> > >> >
> > >> > As Fabio already indicated - this is possible.
> > >> >
> > >>
> > >> Fabio said "mainline". I'm not sure whether meant linux-fslc (as
> > >> Otavio
> > >> used it) or kernel.org.
> > >
> > > In this sense, linux-fslc *is* de-facto the kernel provided from
> > > kernel.org. It has a handful of patched that are not in upstream:
> > >
> > > $ git log --no-merges --oneline stable-git/linux-5.10.y..5.10.x+fslc
> > > 2b929f3dcf6c media: coda: Change firmware probing order
> > > dacfb877023a ARM: imx: add smp support for imx7d
> > > 10c7ebc67e34 drivers, misc: add U-Boot bootcount driver
> > > 67ea92db430f fec: Add disable_giga parameter to force 10/100 operati=
on
> > > bc552ba32d60 MA-7633-2 [Android-Reboot]reboot to fastboot\recovery m=
ode
> > > 695186a85a0d ARM: imx: add cpu_is_imx6() routine
> > >
> > >> So I wanted to check that.
> > >>
> > And that worked out brilliantly :-)
> > (thanks, see my response to Fabio on the same subject as well)
> >
> > >> >>
> > >> >> Bas.
> > >> >>
> > >> >
> > >> > --
> > >> > Regards,
> > >> > Andrey.
> > >> >
> > >> >
> > >
> > > --
> > > Regards,
> > > Andrey.
> >
> > Regards,
> >
> > Bas.
>
>
>
> --
> Regards,
> Andrey.
>
>=20
>
>

--000000000000cd1ce405bc3a01ca
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Hi,=
 there.
I see h=
ere a lot of specialists. Some qestions.=C2=A0
1. What kernel (community=C2=A0or non-commu=
nity) would=C2=A0you take for your own board (not NXP, not O.S.)?
2. I took the branch=C2=
=A0origin/imx_4.14.98_2.0.0_ga. Is it a community=C2=A0supported branch?=
=C2=A0

=D1=87=D1=82, 25 =D1=84=D0=B5=D0=B2=D1=80. 2021 =D0=B3. =D0=B2=
 17:00, Andrey Zhizhikin <andrey.z=
@gmail.com>:
On Thu, Feb 25, 2021 at 2:22 PM Bas Mevissen <abuse@basmevissen.nl> wrote:

>

> On 2021-02-25 14:04, Andrey Zhizhikin wrote:

> > On Thu, Feb 25, 2021 at 1:55 PM Bas Mevissen <abuse@basmevissen.nl>

> > wrote:

> >>

> >> On 2021-02-25 13:32, Andrey Zhizhikin wrote:

> >> > Hello Bas,

> >> >

> >> > On Thu, Feb 25, 2021 at 1:18 PM Bas Mevissen <abuse@basmevissen.nl>

> >> > wrote:

> >> >>

> >> >> On 2021-02-25 12:21, Otavio Salvador wrote:

> >> >> > Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Ter=
ry Barnaby

> >> >> > <terry@beam.ltd.uk> escreveu:

> >> >> >>=C2=A0 From what I am seeing I will have to=
 use a NXP fsl-* based

> >> >> >> distribution

> >> >> >> to support the imx hardware video processi=
ng features. I have built

> >> >> >> such

> >> >> >> a distro with both linux-fslc-imx and limu=
x-imx kernels (I think!) for

> >> >> >> the Wandboard, which boots and runs but th=
e HDMI display was not

> >> >> >> functional. I will persevere looking at th=
at.

> >> >> >

> >> >> > No, you don't. You can use linux-fslc (mai=
nline) and fslc-* distros as

> >> >> > i.MX6 has full mainline support. At O.S. Syste=
ms we have been using

> >> >> > Linux mainline with many customers with great =
success.

> >> >> >

> >> >>

> >> >> Wouldn't make sense to first evaluate the perfo=
rmance of the platform

> >> >> (as Terry plans to do) first on an NXP fsl-* distro=
? In that case one

> >> >> can get direct support from NXP if required. After =
that, derive your

> >> >> own

> >> >> distro from fslc-*.

> >> >

> >> > This might not be quite indicative, as the NXP kernel m=
ight have some

> >> > "shortcuts" to boost performance in certain a=
reas, sacrificing

> >> > conformance of the source code.

> >> >

> >>

> >> At least you get an idea of what the HW platform can do.

> >>

> >> > You might experience the situation that video performs =
quite well, but

> >> > then after opting for NXP kernel - you might find that =
some other

> >> > areas are not working as expected (some other domains).=
 This would put

> >> > you in a situation that you've already committed to=
 choose and deploy

> >> > the NXP-based BSP and would leave you to solve the issu=
es in those

> >> > domains on your own efforts.

> >> >

> >> > This is my pure speculation here, so take it with a gra=
in of salt

> >> > though. :)

> >> >

> >> IMHO, you should never base your *product* on FSL. It is (at=
 least,

> >> that

> >> is what was told me by (then) Freescale field engineers) onl=
y there to

> >> demonstrate the platform. Maybe that has changed over time.<=
br>
> >

> > That is exactly what I implied, below statement is about that.
> >

> Ok, I missed that obviously.

>

> >>

> >> When there is a huge performance difference between fsl and =
fslc, it

> >> needs to be resolved.

> >

> > By whom? This would lead to a situation that community does not =
take

> > responsibility for NXP and visa-versa. In this case - I have a b=
ad

> > feeling that the engineering team in the company that decided to=
 use

> > one flavor or another would be dealing with this fact. And this =
is

> > what I've also described as potential outcome.

> >

>

> It is actually that interaction between the community and NXP that ha=
s

> brought i.MX support at the level it has. So if a performance problem=


> might pop up, it is that same combination that can and will work

> together to get it resolved. It is to the company/person who found th=
e

> issue to bring it up (here) and not to resolve it as that requires
> capabilities that are not so widespread.



In ideal situation - that would be a way to go. But in this case I

would expect that all patches that are present in NXP kernel tree are

posted upstream, so there would be no deviation and hence - no

performance differences between NXP and upstream kernels.



Of course, the problem when found - can be reported, but (a) I do not

believe that this list is a proper destination for such issues, as it

discuss the OE and not kernel-specific performance issues; and (b)

regressions can come from any side (NXP or upstream), which makes it

harder to bisect which side to be looked at.



I'm not saying that this is an impossible thing to solve, but in

reality the vast majority of efforts to solve those issues are landing

up at the side of those persons who've discovered them in the first
place.



This is all my point of view on the subject, and might deviate on a

case-by-case basis.



>

> >>

> >> > IMHO, this should be considered and before the final pr=
oduct receives

> >> > commitment to use either of BSP flavors - all areas sho=
uld be

> >> > validated, not only the performance aspects of Multimed=
ia domain.

> >> >

> >>

> >> Yes, when you have decided on the hardware to use. If you ar=
e

> >> evaluating

> >> the hardware to see whether it meets your requirements, you =
might want

> >> to take the option that gives you the best impression of the=


> >> performance

> >> that can be achieved without too much of a hassle.

> >> (it is an important step to do, at a stage of the developmen=
t where

> >> time

> >> is usually very limited, so you want a quick but reliable re=
sult).

> >

> > Correct, fully agree here.

> >

> >>

> >> >>

> >> >> BTW Would kernel.org stable kernel work as well on i.MX=
6 if you need

> >> >> graphics and video? I used it successfully for head=
less IOT

> >> >> applications.

> >> >

> >> > As Fabio already indicated - this is possible.

> >> >

> >>

> >> Fabio said "mainline". I'm not sure whether me=
ant linux-fslc (as

> >> Otavio

> >> used it) or kernel.org.

> >

> > In this sense, linux-fslc *is* de-facto the kernel provided from=


> > kernel.org. It has a handful of patched that are not in upstream:
> >

> > $ git log --no-merges --oneline stable-git/linux-5.10.y..5.10.x+=
fslc

> > 2b929f3dcf6c media: coda: Change firmware probing order

> > dacfb877023a ARM: imx: add smp support for imx7d

> > 10c7ebc67e34 drivers, misc: add U-Boot bootcount driver

> > 67ea92db430f fec: Add disable_giga parameter to force 10/100 ope=
ration

> > bc552ba32d60 MA-7633-2 [Android-Reboot]reboot to fastboot\recove=
ry mode

> > 695186a85a0d ARM: imx: add cpu_is_imx6() routine

> >

> >> So I wanted to check that.

> >>

> And that worked out brilliantly :-)

> (thanks, see my response to Fabio on the same subject as well)

>

> >> >>

> >> >> Bas.

> >> >>

> >> >

> >> > --

> >> > Regards,

> >> > Andrey.

> >> >

> >> >

> >

> > --

> > Regards,

> > Andrey.

>

> Regards,

>

> Bas.







-- 

Regards,

Andrey.










--000000000000cd1ce405bc3a01ca--

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from hosting.emcodev.net (hosting.emcodev.net [178.18.92.162])
 by mx.groups.io with SMTP id smtpd.web12.7244.1614333820905925516
 for ;
 Fri, 26 Feb 2021 02:03:42 -0800
Authentication-Results: mx.groups.io;
 dkim=fail reason="signature has expired" header.i=@basmevissen.nl header.s=default header.b=ZxhCL+VV;
 spf=pass (domain: basmevissen.nl, ip: 178.18.92.162, mailfrom: abuse@basmevissen.nl)
Received: from localhost (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id D4597212011;
	Fri, 26 Feb 2021 11:03:32 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=basmevissen.nl;
	 h=message-id:user-agent:references:in-reply-to:subject:subject
	:from:from:date:date:content-transfer-encoding:content-type
	:content-type:mime-version; s=default; t=1614333809; x=
	1616148210; bh=GMLGi+4AWUypXXBFaiL8blStg8m7xTFAn+t2/1SdLFw=; b=Z
	xhCL+VVZ4V/QZbqDyFsW1svKSGBL/4fULOgrEAPkbtm7TW8cw3HabDt55O7sN+Gm
	bNQH8f52QxOV6w/937LCSaR1J+iE0z55UcQnPf9grCgJXzw5gW+MBx4dfN1GTeUA
	5Sv2/3MSgWTjwAiDRfSueQNVC7e+Flb/18Z7oQROg9g19tPMy9EkwOUOizE1+yDV
	IpLjOKzUPqHPeDca2Lmyji6lRQ7eOjIysR8uV6haQj26SLZsnsRUicHsuoY3YXBA
	2nL20UYYhzhY0swH+T76xgLJm0YJFa8l4nnGxKtgZ/L+QMtIhBntY9BL3l18FkbY
	IOFQtExBdWNoFsg54vDQjbrm7UyzC5VqtXRjVFrETmSvChsrwqc1sY/xeEB6n9td
	QJz4jNEzT5FmIxlty/kHGJCYcFHe0kc0xI9ZxySQneijr7r/CyEpjCeM7M/Tdkqt
	cbf6KHn61fVHvu3knxrcuxEsui0stMtZeCkuOEFSvNVBctW39+4CLT6/01+HyZqw
	cCm+I0Y6sFhjXPZaI0C5R/Z0JEUKTnIfsLy0qppVdoFQdrCSU1+B9nA/4y3W5z7a
	CC67x/5G90oBjQxTytDeNCYkSuU7PU4SicCJHIu8oGpOX+dpbU6gJ1UkjQhPlncW
	EvWdNu8XXLjr5eGKAr1rRXzZXEOayPjSLjKov5XQ4Y=
Received: from hosting.emcodev.net ([127.0.0.1])
	by localhost (hosting.emcodev.net [127.0.0.1]) (amavisd-new, port 10026)
	with LMTP id LmY7egvSvOof; Fri, 26 Feb 2021 11:03:29 +0100 (CET)
Received: from emcodev.nl (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id BD31821200B;
	Fri, 26 Feb 2021 11:03:29 +0100 (CET)
MIME-Version: 1.0
Date: Fri, 26 Feb 2021 11:03:29 +0100
From: "Bas Mevissen" 
To: =?UTF-8?Q?=D0=9A=D0=BE=D0=BD=D1=81=D1=82=D0=B0=D0=BD=D1=82=D0=B8?=
 =?UTF-8?Q?=D0=BD_=D0=95=D1=80=D0=B5=D0=BC=D0=B5=D0=BD=D0=BE=D0=BA?=
 
Cc: Andrey Zhizhikin , Otavio Salvador
 , Terry Barnaby ,
 meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
In-Reply-To: 
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk>
 
 <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl>
 
 <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl>
 
 
 
 
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <4b1f1b85217b1428f0f88c2aeaee2d87@basmevissen.nl>
X-Sender: abuse@basmevissen.nl
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: quoted-printable

On 2021-02-26 10:36, =D0=9A=D0=BE=D0=BD=D1=81=D1=82=D0=B0=D0=BD=D1=82=D0=B8=
=
=D0=BD =D0=95=D1=80=D0=B5=D0=BC=D0=B5=D0=BD=D0=BE=D0=BA wrote:

> Hi, there.
> I see here a lot of specialists. Some qestions.

You are welcome, however:
1) Start a new topic for a new question
2) Do not top post to keep discussion threads readable

I'm not a specialist, but I think I can answer your questions.

> 1. What kernel (community or non-community) would you take for your own=
=20
> board (not NXP, not O.S.)?

IMHO, community unless quickly testing out something or when the=20
community kernel is not sufficient (performance, specific hw=20
support,...).

> 2. I took the branch origin/imx_4.14.98_2.0.0_ga. Is it a community=20
> supported branch?
>=20
 From=20
https://source.codeaurora.org/external/imx/linux-imx/log/?h=3Dimx_4.14.98_=
2.0.0_ga?=20
That is not community, but NXP.

Regards,

Bas.


> =D1=87=D1=82, 25 =D1=84=D0=B5=D0=B2=D1=80. 2021 =D0=B3. =D0=B2 17:00, An=
drey Zhizhikin :
>=20
>> On Thu, Feb 25, 2021 at 2:22 PM Bas Mevissen =20
>> wrote:
>>>=20
>>> On 2021-02-25 14:04, Andrey Zhizhikin wrote:
>>>> On Thu, Feb 25, 2021 at 1:55 PM Bas Mevissen 
>>>> wrote:
>>>>>=20
>>>>> On 2021-02-25 13:32, Andrey Zhizhikin wrote:
>>>>>> Hello Bas,
>>>>>>=20
>>>>>> On Thu, Feb 25, 2021 at 1:18 PM Bas Mevissen=20
>>>>>> 
>>>>>> wrote:
>>>>>>>=20
>>>>>>> On 2021-02-25 12:21, Otavio Salvador wrote:
>>>>>>> > Em qui., 25 de fev. de 2021 =C3=A0s 06:53, Terry Barnaby
>>>>>>> >  escreveu:
>>>>>>> >>  From what I am seeing I will have to use a NXP fsl-* based
>>>>>>> >> distribution
>>>>>>> >> to support the imx hardware video processing features. I have b=
uilt
>>>>>>> >> such
>>>>>>> >> a distro with both linux-fslc-imx and limux-imx kernels (I thin=
k!) for
>>>>>>> >> the Wandboard, which boots and runs but the HDMI display was no=
t
>>>>>>> >> functional. I will persevere looking at that.
>>>>>>> >
>>>>>>> > No, you don't. You can use linux-fslc (mainline) and fslc-* dist=
ros as
>>>>>>> > i.MX6 has full mainline support. At O.S. Systems we have been us=
ing
>>>>>>> > Linux mainline with many customers with great success.
>>>>>>> >
>>>>>>>=20
>>>>>>> Wouldn't make sense to first evaluate the performance of the=20
>>>>>>> platform
>>>>>>> (as Terry plans to do) first on an NXP fsl-* distro? In that case=
=20
>>>>>>> one
>>>>>>> can get direct support from NXP if required. After that, derive=20
>>>>>>> your
>>>>>>> own
>>>>>>> distro from fslc-*.
>>>>>>=20
>>>>>> This might not be quite indicative, as the NXP kernel might have=20
>>>>>> some
>>>>>> "shortcuts" to boost performance in certain areas, sacrificing
>>>>>> conformance of the source code.
>>>>>>=20
>>>>>=20
>>>>> At least you get an idea of what the HW platform can do.
>>>>>=20
>>>>>> You might experience the situation that video performs quite well,=
=20
>>>>>> but
>>>>>> then after opting for NXP kernel - you might find that some other
>>>>>> areas are not working as expected (some other domains). This would=
=20
>>>>>> put
>>>>>> you in a situation that you've already committed to choose and=20
>>>>>> deploy
>>>>>> the NXP-based BSP and would leave you to solve the issues in those
>>>>>> domains on your own efforts.
>>>>>>=20
>>>>>> This is my pure speculation here, so take it with a grain of salt
>>>>>> though. :)
>>>>>>=20
>>>>> IMHO, you should never base your *product* on FSL. It is (at least,
>>>>> that
>>>>> is what was told me by (then) Freescale field engineers) only there=
=20
>>>>> to
>>>>> demonstrate the platform. Maybe that has changed over time.
>>>>=20
>>>> That is exactly what I implied, below statement is about that.
>>>>=20
>>> Ok, I missed that obviously.
>>>=20
>>>>>=20
>>>>> When there is a huge performance difference between fsl and fslc,=20
>>>>> it
>>>>> needs to be resolved.
>>>>=20
>>>> By whom? This would lead to a situation that community does not take
>>>> responsibility for NXP and visa-versa. In this case - I have a bad
>>>> feeling that the engineering team in the company that decided to use
>>>> one flavor or another would be dealing with this fact. And this is
>>>> what I've also described as potential outcome.
>>>>=20
>>>=20
>>> It is actually that interaction between the community and NXP that=20
>>> has
>>> brought i.MX support at the level it has. So if a performance problem
>>> might pop up, it is that same combination that can and will work
>>> together to get it resolved. It is to the company/person who found=20
>>> the
>>> issue to bring it up (here) and not to resolve it as that requires
>>> capabilities that are not so widespread.
>>=20
>> In ideal situation - that would be a way to go. But in this case I
>> would expect that all patches that are present in NXP kernel tree are
>> posted upstream, so there would be no deviation and hence - no
>> performance differences between NXP and upstream kernels.
>>=20
>> Of course, the problem when found - can be reported, but (a) I do not
>> believe that this list is a proper destination for such issues, as it
>> discuss the OE and not kernel-specific performance issues; and (b)
>> regressions can come from any side (NXP or upstream), which makes it
>> harder to bisect which side to be looked at.
>>=20
>> I'm not saying that this is an impossible thing to solve, but in
>> reality the vast majority of efforts to solve those issues are landing
>> up at the side of those persons who've discovered them in the first
>> place.
>>=20
>> This is all my point of view on the subject, and might deviate on a
>> case-by-case basis.
>>=20
>>>=20
>>>>>=20
>>>>>> IMHO, this should be considered and before the final product=20
>>>>>> receives
>>>>>> commitment to use either of BSP flavors - all areas should be
>>>>>> validated, not only the performance aspects of Multimedia domain.
>>>>>>=20
>>>>>=20
>>>>> Yes, when you have decided on the hardware to use. If you are
>>>>> evaluating
>>>>> the hardware to see whether it meets your requirements, you might=20
>>>>> want
>>>>> to take the option that gives you the best impression of the
>>>>> performance
>>>>> that can be achieved without too much of a hassle.
>>>>> (it is an important step to do, at a stage of the development where
>>>>> time
>>>>> is usually very limited, so you want a quick but reliable result).
>>>>=20
>>>> Correct, fully agree here.
>>>>=20
>>>>>=20
>>>>>>>=20
>>>>>>> BTW Would kernel.org stable kernel work as well on i.MX6 if you=20
>>>>>>> need
>>>>>>> graphics and video? I used it successfully for headless IOT
>>>>>>> applications.
>>>>>>=20
>>>>>> As Fabio already indicated - this is possible.
>>>>>>=20
>>>>>=20
>>>>> Fabio said "mainline". I'm not sure whether meant linux-fslc (as
>>>>> Otavio
>>>>> used it) or kernel.org.
>>>>=20
>>>> In this sense, linux-fslc *is* de-facto the kernel provided from
>>>> kernel.org. It has a handful of patched that are not in upstream:
>>>>=20
>>>> $ git log --no-merges --oneline stable-git/linux-5.10.y..5.10.x+fslc
>>>> 2b929f3dcf6c media: coda: Change firmware probing order
>>>> dacfb877023a ARM: imx: add smp support for imx7d
>>>> 10c7ebc67e34 drivers, misc: add U-Boot bootcount driver
>>>> 67ea92db430f fec: Add disable_giga parameter to force 10/100=20
>>>> operation
>>>> bc552ba32d60 MA-7633-2 [Android-Reboot]reboot to fastboot\recovery=20
>>>> mode
>>>> 695186a85a0d ARM: imx: add cpu_is_imx6() routine
>>>>=20
>>>>> So I wanted to check that.
>>>>>=20
>>> And that worked out brilliantly :-)
>>> (thanks, see my response to Fabio on the same subject as well)
>>>=20
>>>>>>>=20
>>>>>>> Bas.
>>>>>>>=20
>>>>>>=20
>>>>>> --
>>>>>> Regards,
>>>>>> Andrey.
>>>>>>=20
>>>>>>=20
>>>>=20
>>>> --
>>>> Regards,
>>>> Andrey.
>>>=20
>>> Regards,
>>>=20
>>> Bas.
>>=20
>> --
>> Regards,
>> Andrey.
>>=20
>>=20

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176])
 by mx.groups.io with SMTP id smtpd.web11.7306.1614334584527945627
 for ;
 Fri, 26 Feb 2021 02:16:24 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=ERXPA23o;
 spf=pass (domain: gmail.com, ip: 209.85.208.176, mailfrom: eremenok.k.by@gmail.com)
Received: by mail-lj1-f176.google.com with SMTP id q14so10009245ljp.4
        for ; Fri, 26 Feb 2021 02:16:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=WCxROekdksmSUtRod8Xthw6Cq2ocwXRXvg/1TJs194g=;
        b=ERXPA23ojoDJBB8hWMaTw32ElbTib4fFjoNmDGDiKWMAWmoW/J0M8mJVnWgxJaXoXK
         ksKlKMwnh0ldIZ52pboqfdMLfoBZ7j88hT0cBNMoemeJ3vfcPIeVwPR1V91BEaUNMtLY
         0tF2nSAU1PzWvTrncv8nWg7ISYOgKyrJ7+ExAOj8P2l88LEba59B9xa1HO5nZlGTF9JO
         MDiBx6cKavy6x9G2t/R2I9ljWNCWFF+Je1SncC9BFqeiuOnX026KI9MhhnoxFOewvV3z
         yu+bUddir93GlxKkqCq3DKKPP8psbEcVdkVjW6NhFI+hT3TGJtMDdDpm5yZmAe7QMn1q
         eTMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=WCxROekdksmSUtRod8Xthw6Cq2ocwXRXvg/1TJs194g=;
        b=C/PUT9FW8BEcJwXOqCjNxwm/mWg0kaU/fc00PB065zqwvcn+jf7uU8eqbNuayUUYcw
         iE8HPTcrmn7yM18JvJ4TQIXpRXxnzd87LopEsEDl0yG+48tkDgX1i/kz8O1Yr7/ls5tD
         uzlg4o7quLVUpiXxdefGM+1emNTMh74N6GA2KV6bk2s0CSgc9HDwRj5gAdiYHTHaSWhN
         orC+jcq5NV0B5kr4yEYx2CTowksVb5wLR9y2yo7L4Rkqt3bGas7DQfOvcRnFVxPXmCJY
         I4q7aYkDrCjxqdSwr909H9RxtY1oAscL67d8DgzfdaCW/E24uCca8hPR+zzUd14KVP/Z
         0ezA==
X-Gm-Message-State: AOAM533VUc+AYGYZS9YNpVywXBlED4Mor0MFqJOlKQP4RVAsjHdnI8FO
	dJAwN/f5z0C1XzRgdL+pNoBhYnN95PnnkfYaQRI=
X-Google-Smtp-Source: ABdhPJwHVHCStFAQzrqfn69W9tCnVXYf0XMzpBi46uBBPp2TIwfcN0k4Y9Xr8wkOZRlmv9Ls4LKAjmHI0oLyK6VUUdI=
X-Received: by 2002:a2e:9118:: with SMTP id m24mr1287720ljg.415.1614334582331;
 Fri, 26 Feb 2021 02:16:22 -0800 (PST)
MIME-Version: 1.0
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk> 
 <9d621536-e38e-c8ee-4d5e-dc3f24fb09f1@beam.ltd.uk> 
 <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl> 
 <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl> 
  
  <4b1f1b85217b1428f0f88c2aeaee2d87@basmevissen.nl>
In-Reply-To: <4b1f1b85217b1428f0f88c2aeaee2d87@basmevissen.nl>
From: =?UTF-8?B?0JrQvtC90YHRgtCw0L3RgtC40L0g0JXRgNC10LzQtdC90L7Qug==?= 
Date: Fri, 26 Feb 2021 13:16:11 +0300
Message-ID: 
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Bas Mevissen 
Cc: meta-freescale@lists.yoctoproject.org, Terry Barnaby , 
	Otavio Salvador , Andrey Zhizhikin 
Content-Type: multipart/alternative; boundary="000000000000541b9605bc3a8f05"

--000000000000541b9605bc3a8f05
Content-Type: text/plain; charset="UTF-8"

Thanks. Sorry for a spam.

--000000000000541b9605bc3a8f05
Content-Type: text/html; charset="UTF-8"


Thanks. Sorry for a spam.



--000000000000541b9605bc3a8f05--

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailgate1.beam.ltd.uk (mailgate1.beam.ltd.uk [88.96.138.49])
 by mx.groups.io with SMTP id smtpd.web11.7403.1614335222909218412
 for ;
 Fri, 26 Feb 2021 02:27:03 -0800
Authentication-Results: mx.groups.io;
 dkim=missing; spf=pass (domain: beam.ltd.uk, ip: 88.96.138.49, mailfrom: terry@beam.ltd.uk)
Received: by mailgate1.beam.ltd.uk (Postfix, from userid 900)
	id BB3D76A6B6E; Fri, 26 Feb 2021 10:26:57 +0000 (GMT)
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on portal.beamnet
X-Spam-Level: 
X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,BAYES_00,
	NICE_REPLY_A autolearn=unavailable autolearn_force=no version=3.4.4
Received: from study.kingnet (king.kingnet [82.69.10.222])
	by mailgate1.beam.ltd.uk (Postfix) with ESMTPSA id 489686A1BAE;
	Fri, 26 Feb 2021 10:26:55 +0000 (GMT)
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
To: Fabio Estevam 
Cc: Andrey Zhizhikin ,
 meta-freescale@lists.yoctoproject.org
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
 
 
 
 
From: "Terry Barnaby" 
Message-ID: <7b61dfc2-f8f4-637d-ccd8-6e59e22996a3@beam.ltd.uk>
Date: Fri, 26 Feb 2021 10:26:54 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: 
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB

On 25/02/2021 12:02, Fabio Estevam wrote:
> On Thu, Feb 25, 2021 at 8:58 AM Terry Barnaby  wrote:
>
>> Many thanks for that info, from Internet info it looked like the
>> gstreamer-imx package and associated lower libraries/drivers were
>> needed, I will try another build, the gstreamer video hardware support
>> wasn't there (as reported by gst-inspect-1.0) when I tried, maybe I got
>> lost in a tangle of distro, kernel and bitbake targets.
> The v4l2dec/enc plugins only show up if the VPU driver were successfully loaded.
>
> Make sure that the VPU (coda) driver is being loaded correctly with
> the associated firmware.
>
> After that, these v4l2dec/enc plugins should be reported by gst-inspect.

I discovered where I was going wrong. My Yocto/Freecale build for the 
Wandboard with standard fslc-x11 distro and linux-fslc kernel did have 
iMX8 video hardware supported and working!

I was originally using a Wandboard supplied binary distro for testing 
that was quite old that used gstreamer modules such as imxv4l2sink, 
vpuenc_h264, overlaysync etc and most of the Internet documentation for 
iMX6's was the same. However the latest dunfell level gstreamer uses the 
more generally standard v4l2h264enc gstreamer module that ends up by 
using the iMX6 VPU's H264 encoder.

Now I just need to work out if the current iMX6 video hardware API's 
allows me to do the video processing pipeline I want/need with suitably 
low enough CPU and memory bandwidth usage. Also how to get an efficient 
gstreamer video source for performance testing while I await a working 
physical camera as videotestsrc uses a lot of CPU for some reason 
masking the performance testing.

Note I am using Fedora33 as a build platform now, and that seems fine 
with dunfell although not yet marked as a known working platform for 
building.

Many thanks for everyone's help.

Terry


From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from hosting.emcodev.net (hosting.emcodev.net [178.18.92.162])
 by mx.groups.io with SMTP id smtpd.web08.7803.1614338850331289636
 for ;
 Fri, 26 Feb 2021 03:27:31 -0800
Authentication-Results: mx.groups.io;
 dkim=fail reason="signature has expired" header.i=@basmevissen.nl header.s=default header.b=FjPrJqD1;
 spf=pass (domain: basmevissen.nl, ip: 178.18.92.162, mailfrom: abuse@basmevissen.nl)
Received: from localhost (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id 5EDBA212011;
	Fri, 26 Feb 2021 12:27:18 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=basmevissen.nl;
	 h=message-id:user-agent:references:in-reply-to:subject:subject
	:from:from:date:date:content-transfer-encoding:content-type
	:content-type:mime-version; s=default; t=1614338836; x=
	1616153237; bh=+1/tk04nZwd2CBbuFelo9/nuRR/iH5SI/YCZLUrPEDo=; b=F
	jPrJqD1XGjgUszEjwLqbd+Br5gs3EJcITZY+f2VHKw9hpeIfO1GeRRWXc4bUgBwV
	brGaUUFMf9at+e2C5VicL0GlyujjnySGv0A69OWZ4N+ibvzuifA4n9Kix+uJZiej
	tCSY1eH/utUoYpYfASvTTyUnTO6vu2K+x7h/34o9+IYgYTf1kdfMqSb91UmpU4ZG
	++Abgrm0I7Axb5W1ZQxMfpuvnI8tPijdaKXhjcWCbCf05xdKRHr23jkMm025mX9V
	rLn+f4KeBtbIzvC98HwnjLfDsx7rS+iuRZvznknF1JYEfSa0QXMXvybP70Y4Ziky
	8kAe6kMSp+zcwrzboSPRzuOjaDI2EuUlj808iQNFv6MArOgPZF+gnzZyMQQ5oeZP
	EOx3J4/9aynjEFctjOANs7RWUjQ/nKMpA/RdRxCJ5sQBmlZRyu3O7kDjNmPknoF6
	poR0YC7XG1ALWyiJxk8r+OR3QoN+qk21BrGLcGlqYvbo4Z7XgtsiA1PGeMCuVab7
	aZ00hlHDJAICS4475+kfIJHaQCZ4TvAhYI1iBwjp0gpUr9dAh9L5iO2LCgNeNaaq
	I4nvw79fYn2BX5L2+0h3+Q2Z0SLxQ49kNl4g9iONC5x7/t3cVbUkW96oIU/444hi
	ZBRME1GUOtM/wQXRtxIHdnZclrR17CniyEGwZyp+rA=
Received: from hosting.emcodev.net ([127.0.0.1])
	by localhost (hosting.emcodev.net [127.0.0.1]) (amavisd-new, port 10026)
	with LMTP id pOX7_sTgGtRc; Fri, 26 Feb 2021 12:27:16 +0100 (CET)
Received: from emcodev.nl (localhost [127.0.0.1])
	by hosting.emcodev.net (Postfix) with ESMTP id 3EBA921200B;
	Fri, 26 Feb 2021 12:27:16 +0100 (CET)
MIME-Version: 1.0
Date: Fri, 26 Feb 2021 12:27:16 +0100
From: "Bas Mevissen" 
To: Terry Barnaby 
Cc: Fabio Estevam , Andrey Zhizhikin
 , meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
In-Reply-To: <7b61dfc2-f8f4-637d-ccd8-6e59e22996a3@beam.ltd.uk>
References: <12bb83d9-625a-f967-ed15-9602fc4cd46b@faresoftware.it>
 
 <910eca81-bcb4-c4b2-d591-9a853026f184@beam.ltd.uk>
 
 
 
 
 <7b61dfc2-f8f4-637d-ccd8-6e59e22996a3@beam.ltd.uk>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: 
X-Sender: abuse@basmevissen.nl
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit

On 2021-02-26 11:26, Terry Barnaby wrote:
> On 25/02/2021 12:02, Fabio Estevam wrote:
>> On Thu, Feb 25, 2021 at 8:58 AM Terry Barnaby  
>> wrote:
>> 
>>> Many thanks for that info, from Internet info it looked like the
>>> gstreamer-imx package and associated lower libraries/drivers were
>>> needed, I will try another build, the gstreamer video hardware 
>>> support
>>> wasn't there (as reported by gst-inspect-1.0) when I tried, maybe I 
>>> got
>>> lost in a tangle of distro, kernel and bitbake targets.
>> The v4l2dec/enc plugins only show up if the VPU driver were 
>> successfully loaded.
>> 
>> Make sure that the VPU (coda) driver is being loaded correctly with
>> the associated firmware.
>> 
>> After that, these v4l2dec/enc plugins should be reported by 
>> gst-inspect.
> 
> I discovered where I was going wrong. My Yocto/Freecale build for the
> Wandboard with standard fslc-x11 distro and linux-fslc kernel did have
> iMX8 video hardware supported and working!
> 
> I was originally using a Wandboard supplied binary distro for testing
> that was quite old that used gstreamer modules such as imxv4l2sink,
> vpuenc_h264, overlaysync etc and most of the Internet documentation
> for iMX6's was the same. However the latest dunfell level gstreamer
> uses the more generally standard v4l2h264enc gstreamer module that
> ends up by using the iMX6 VPU's H264 encoder.
> 
> Now I just need to work out if the current iMX6 video hardware API's
> allows me to do the video processing pipeline I want/need with
> suitably low enough CPU and memory bandwidth usage. Also how to get an
> efficient gstreamer video source for performance testing while I await
> a working physical camera as videotestsrc uses a lot of CPU for some
> reason masking the performance testing.
> 

Good to hear you make progress!

> Note I am using Fedora33 as a build platform now, and that seems fine
> with dunfell although not yet marked as a known working platform for
> building.
> 

I also always use the latest Fedora as my development platform. It 
usually works without a problem (except for the warning). Only the 
uninative cannot always keep up with the latet glibc used in Fedora. But 
that is usually picked up very quickly.

For older Yocto versions, I use systemd containers with a matching OS, 
like CentOS 7 or Debian. Toradex has a nice write-up on how to set that 
up.

> Many thanks for everyone's help.
> 
> Terry
> 
> 
> 
>