meta-freescale.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Fabio Estevam" <festevam@gmail.com>
To: Bas Mevissen <abuse@basmevissen.nl>
Cc: Andrey Zhizhikin <andrey.z@gmail.com>,
	Otavio Salvador <otavio.salvador@ossystems.com.br>,
	 Terry Barnaby <terry@beam.ltd.uk>,
	meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
Date: Thu, 25 Feb 2021 10:01:53 -0300	[thread overview]
Message-ID: <CAOMZO5CPcofoVVYVo4RpOFVwcARNoFb7dNbiX5Z+T+a2wQWmxg@mail.gmail.com> (raw)
In-Reply-To: <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl>

Hi Bas,

On Thu, Feb 25, 2021 at 9:55 AM Bas Mevissen <abuse@basmevissen.nl> 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

  reply	other threads:[~2021-02-25 13:02 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
2021-02-25 12:32             ` Andrey Zhizhikin
2021-02-25 12:55               ` Bas Mevissen
2021-02-25 13:01                 ` Fabio Estevam [this message]
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=CAOMZO5CPcofoVVYVo4RpOFVwcARNoFb7dNbiX5Z+T+a2wQWmxg@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=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).