From: "Bas Mevissen" <abuse@basmevissen.nl>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Terry Barnaby <terry@beam.ltd.uk>,
Andrey Zhizhikin <andrey.z@gmail.com>,
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:18:06 +0100 [thread overview]
Message-ID: <30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl> (raw)
In-Reply-To: <CAP9ODKrmr5phjLnbT+2h3HQYkme_LfJkQY5RbgO-GZeiDK64QA@mail.gmail.com>
On 2021-02-25 12: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.
>
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-*.
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.
Bas.
>
>
next prev parent reply other threads:[~2021-02-25 12:18 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
2021-02-25 12:18 ` Bas Mevissen [this message]
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=30d6ff10b73bd117198a8e2dd3e47388@basmevissen.nl \
--to=abuse@basmevissen.nl \
--cc=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).