From: "Andrey Zhizhikin" <andrey.z@gmail.com>
To: Terry Barnaby <terry@beam.ltd.uk>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
Date: Thu, 25 Feb 2021 13:24:52 +0100 [thread overview]
Message-ID: <CAHtQpK6X+mv-uoE7LNu1zwmWYNaASVp=H4JdOhcjqwzZgVafhA@mail.gmail.com> (raw)
In-Reply-To: <66670eb7-6ade-bf48-7a88-b2dc56944f10@beam.ltd.uk>
On Thu, Feb 25, 2021 at 12:50 PM Terry Barnaby <terry@beam.ltd.uk> wrote:
>
> On 25/02/2021 11:21, Otavio Salvador wrote:
> > Em qui., 25 de fev. de 2021 às 06:53, Terry Barnaby
> > <terry@beam.ltd.uk> 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.
> >
> 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 ??= 'wandboard'", "DISTRO ?= 'fslc-x11'" and add
> IMAGE_INSTALL_append=" 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-freescale-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="mainline").
As Fabio already indicated, gstreamer1.0-plugins-imx should be used
**only** with NXP-based BSP (selected by setting
IMX_DEFAULT_BSP="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="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.
--
Regards,
Andrey.
next prev parent reply other threads:[~2021-02-25 12:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 8:40 imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx? Mauro Ziliani
2021-02-25 8:47 ` [meta-freescale] " Andrey Zhizhikin
2021-02-25 9:00 ` Terry Barnaby
2021-02-25 9:29 ` Andrey Zhizhikin
2021-02-25 9:53 ` Terry Barnaby
2021-02-25 11:21 ` Otavio Salvador
2021-02-25 11:50 ` Terry Barnaby
2021-02-25 12:24 ` Andrey Zhizhikin [this message]
2021-02-25 12:18 ` Bas Mevissen
2021-02-25 12:32 ` Andrey Zhizhikin
2021-02-25 12:55 ` Bas Mevissen
2021-02-25 13:01 ` Fabio Estevam
2021-02-25 13:12 ` Bas Mevissen
2021-02-25 13:04 ` Andrey Zhizhikin
2021-02-25 13:22 ` Bas Mevissen
2021-02-25 14:00 ` Andrey Zhizhikin
2021-02-26 9:36 ` eremenok.k.by
2021-02-26 10:03 ` Bas Mevissen
2021-02-26 10:16 ` Константин Еременок
2021-02-25 11:47 ` Fabio Estevam
2021-02-25 11:57 ` Terry Barnaby
2021-02-25 12:02 ` Fabio Estevam
2021-02-26 10:26 ` Terry Barnaby
2021-02-26 11:27 ` Bas Mevissen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHtQpK6X+mv-uoE7LNu1zwmWYNaASVp=H4JdOhcjqwzZgVafhA@mail.gmail.com' \
--to=andrey.z@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=terry@beam.ltd.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).