All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio Estevam" <festevam@gmail.com>
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: "meta-freescale@lists.yoctoproject.org"
	<meta-freescale@lists.yoctoproject.org>
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?
Date: Thu, 10 Jun 2021 17:14:06 -0300	[thread overview]
Message-ID: <CAOMZO5AAduJ-_0vpAEmbJcJNSjVQK55E59hFE3gYM8fdnYkHQQ@mail.gmail.com> (raw)
In-Reply-To: <BN6P132MB00688A0D80B2A3104A98F0F3E1359@BN6P132MB0068.NAMP132.PROD.OUTLOOK.COM>

Hi Val,

On Thu, Jun 10, 2021 at 9:34 AM Val Kondratenko
<valeriy.kondratenko@jci.com> wrote:
> I recently got tasked with upgrading linux kernel (which we get from freescale), to fix some vulnerabilities.
>
> I am new to this, with all engineers with previous experience in this area no longer with company.
>
> To fix the vulnerabilities, will need to upgrade to kernel rev 5.12.
>
> Noticed that only a community branch of this (5.12.x+fslc) is available.   Latest freescale (imx) releases/branches are still at 5.4.
>
> I do so, my organization has previously used on freescale/imx releases.
>
> Is it generally safe to use the community releases?  Have their problems with bugs/instabilities with them?

Yes, it is a good approach to move to a mainline kernel.

One important aspect to consider is what is the i.MX SoC that you are using.

imx28/imx5/imx6/imx7 have decent support in the upstream kernel.
imx8m/imx8mm are getting better.

imx8qxp has a minimum support upstream in 5.12.

  parent reply	other threads:[~2021-06-10 20:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 12:34 Safe to upgrade to a Community BSP? Val Kondratenko
2021-06-10 19:43 ` [meta-freescale] " Otavio Salvador
2021-06-10 20:18   ` Val Kondratenko
2021-06-10 21:11     ` Fabio Estevam
2021-06-11 15:12       ` Val Kondratenko
2021-06-11 16:19         ` Fabio Estevam
2021-06-11 16:42           ` Val Kondratenko
2021-07-09 19:22           ` Val Kondratenko
2021-06-23 17:48       ` Val Kondratenko
2021-06-23 20:05         ` Fabio Estevam
     [not found]       ` <16878FD7EE6FE05F.27948@lists.yoctoproject.org>
2021-06-25 17:53         ` Val Kondratenko
2021-06-25 18:11           ` Fabio Estevam
2021-06-29 20:03             ` Val Kondratenko
2021-07-06 14:29               ` Val Kondratenko
     [not found]         ` <168BE6901ABD95ED.20408@lists.yoctoproject.org>
2021-06-25 18:28           ` Val Kondratenko
2021-07-09 19:08   ` Val Kondratenko
2021-06-10 20:14 ` Fabio Estevam [this message]
2021-06-10 20:21   ` Val Kondratenko
2021-07-07 11:48 ` Val Kondratenko

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=CAOMZO5AAduJ-_0vpAEmbJcJNSjVQK55E59hFE3gYM8fdnYkHQQ@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=meta-freescale@lists.yoctoproject.org \
    --cc=valeriy.kondratenko@jci.com \
    /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.