All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Clay Montgomery" <clay@montgomery1.com>
To: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Kernel support for i.MX6UL and 4.9 LTS updates
Date: Fri, 3 Jan 2020 16:21:48 -0600	[thread overview]
Message-ID: <9027e187-0fa0-ea01-44a4-64874d6df403@montgomery1.com> (raw)
In-Reply-To: <CAAdZ0qcC53c4KkL6Difp_LjQRoFhkDspYemOu8tHS3NZiwH0hQ@mail.gmail.com>

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

Jesse,

     1. The best answer is probably to take a look at NXP's notes and 
defconfigs here:

     repo init -u 
https://source.codeaurora.org/external/imx/imx-manifest -b 
imx-linux-sumo -m imx-4.14.98-2.0.0_ga.xml

~/Yocto/imx-yocto-bsp/sources/meta-freescale/recipes-kernel/linux/

     2. There were a lot of changes made to the DRM in the 4.9 kernels 
that had a major impact on NXP's IPU and V4L2 support drivers. Some 
fundamental stuff (like /dev/fb, X11 and Wayland) were broken and NXP 
seems unlikely to ever fix that for newer kernels on the i.MX6.

     3. Certainly not NXP.

Most developers still on the i.MX6 seem to either stick with 4.1.15 or 
move to a mainline kernel.

Regards, Clay


On 1/3/2020 1:40 PM, Jesse Gilles wrote:
> Hi Fabio,
>
> On Sat, Dec 21, 2019 at 6:11 AM Fabio Estevam <festevam@gmail.com 
> <mailto:festevam@gmail.com>> wrote:
>
>
>     I suggest you to move to kernel 5.4.x instead.
>
>
> Can you explain why you recommend the 5.4 kernel?  I don't see a 
> recipe for it in meta-freescale.
>
> Can anyone else answer some of my other questions?
>
> 1. For i.MX6UL support and functionality, is there a significant 
> difference between linux-fslc and linux-imx-fslc?
> 2. 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?
> 3. Is anyone maintaining the 4.9 branch and planning to keep it up to 
> date with upstream LTS updates?
>
> Thanks,
> Jesse
>
> On Sat, Dec 21, 2019 at 6:11 AM Fabio Estevam <festevam@gmail.com 
> <mailto:festevam@gmail.com>> wrote:
>
>     Hi Jesse,
>
>     On Thu, Dec 19, 2019 at 7:33 PM Jesse Gilles
>     <jesse.gilles@gmail.com <mailto:jesse.gilles@gmail.com>> wrote:
>     >
>     > 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.
>
>     I suggest you to move to kernel 5.4.x instead.
>
>     Regards,
>
>     Fabio Estevam
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#24209): https://lists.yoctoproject.org/g/meta-freescale/message/24209
> Mute This Topic: https://lists.yoctoproject.org/mt/68840298/3617246
> Group Owner: meta-freescale+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-freescale/unsub  [clay@montgomery1.com]
> -=-=-=-=-=-=-=-=-=-=-=-

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

  reply	other threads:[~2020-01-03 22:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 22:33 Kernel support for i.MX6UL and 4.9 LTS updates jesse.gilles
2019-12-21 12:11 ` [meta-freescale] " Fabio Estevam
2020-01-03 19:40   ` Jesse Gilles
2020-01-03 22:21     ` Clay Montgomery [this message]
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=9027e187-0fa0-ea01-44a4-64874d6df403@montgomery1.com \
    --to=clay@montgomery1.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.