All of lore.kernel.org
 help / color / mirror / Atom feed
From: jesse.gilles@gmail.com
To: meta-freescale@lists.yoctoproject.org
Subject: Kernel support for i.MX6UL and 4.9 LTS updates
Date: Thu, 19 Dec 2019 16:33:24 -0600	[thread overview]
Message-ID: <CAAdZ0qeOVesz_ROsfbjqy2Hy4opqnJAVu1i1SQKEKKWqp2oGoA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

Hello,

I am working on a project using the i.MX6UL and I am curious about the
state of Linux kernel support in various different kernel recipes in
meta-freescale.

After reading documentation and various posts, this is my understanding of
the different kernels in the layer:

linux-fslc: purely community maintained kernel, kept pretty up to date with
upstream
linux-imx-fslc: community maintained kernel, based off NXP official BSP
release kernel
linux-imx: NXP official BSP release kernel

For i.MX6UL support and functionality, is there a significant difference
between linux-fslc and linux-imx-fslc?

For linux-imx-fslc, is there a specific reason it is still using
4.9-1.0.x-imx and not the newer 4.9-2.3.x-imx branch?

If linux-imx-fslc is the best option, is anyone maintaining the 4.9 branch
and planning to keep it up to date with upstream LTS updates?  I see that
4.9-2.3.x-imx has been updated to 4.9.166.

In short, I am looking for the best maintained and updated kernel with
support for the i.MX6UL, including security fixes into the future.  My
existing project uses a customized linux-imx 4.9 kernel.

Any help would be greatly appreciated.

Thanks,
Jesse

[-- Attachment #2: Type: text/html, Size: 1479 bytes --]

             reply	other threads:[~2019-12-19 22:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 22:33 jesse.gilles [this message]
2019-12-21 12:11 ` [meta-freescale] Kernel support for i.MX6UL and 4.9 LTS updates Fabio Estevam
2020-01-03 19:40   ` Jesse Gilles
2020-01-03 22:21     ` Clay Montgomery
2020-01-09 15:13       ` Jesse Gilles
2020-01-09 15:28         ` Richard Leitner
2020-01-09 20:14           ` Jesse Gilles
2020-01-10  7:46             ` Richard Leitner
2020-01-09 17:18         ` Clay Montgomery
2020-01-09 20:08           ` Jesse Gilles
2020-01-09 20:14             ` Otavio Salvador
2020-01-09 21:26               ` Clay Montgomery
2020-01-04 15:31     ` Fabio Estevam

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=CAAdZ0qeOVesz_ROsfbjqy2Hy4opqnJAVu1i1SQKEKKWqp2oGoA@mail.gmail.com \
    --to=jesse.gilles@gmail.com \
    --cc=meta-freescale@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

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

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