Safe to upgrade to a Community BSP?

Safe to upgrade to a Community BSP?

[Val Kondratenko]

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


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?

Thanks in advance,
Val

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

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Otavio Salvador]

Hello Val,

The 5.12.x is based on mainline. It is totally safe and include very
small set of changes on top of upstream.

Em qui., 10 de jun. de 2021 às 09:34, Val Kondratenko
<valeriy.kondratenko@jci.com> escreveu:
>
>
>
> 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?
>
>
>
> Thanks in advance,
>
> Val
>
>
> 
>


-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Fabio Estevam]

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.

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

OK thanks.

Next question - does it have full support for imx7d?

I noticed (as I am attempting to apply patches we use), that /arch/arm/mach-imx/cpuidle-imx7d.c exists in the 5.4.X.imx version we are currently using, but is not present in 5.12.  But mach-imx7d.c is.
 Will I have to add files (via patches) to fully support imx7d?

Thanks a ton,
  Val

-----Original Message-----
From: Otavio Salvador <otavio.salvador@ossystems.com.br> 
Sent: Thursday, June 10, 2021 3:43 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

Hello Val,

The 5.12.x is based on mainline. It is totally safe and include very small set of changes on top of upstream.

Em qui., 10 de jun. de 2021 às 09:34, Val Kondratenko <valeriy.kondratenko@jci.com> escreveu:
>
>
>
> 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?
>
>
>
> Thanks in advance,
>
> Val
>
>
> 
>


-- 
Otavio Salvador                             O.S. Systems
https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ossystems.com.br%2F&amp;data=04%7C01%7Cvaleriy.kondratenko%40jci.com%7C68fa10fc4c794bcb2ac108d92c480a8b%7Ca1f1e2147ded45b681a19e8ae3459641%7C0%7C1%7C637589510191097105%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=r%2FuFSFBqT%2B1WdIyGGgW5bwH%2B1gFJQnGtJq5fyKkvYb0%3D&amp;reserved=0        https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcode.ossystems.com.br%2F&amp;data=04%7C01%7Cvaleriy.kondratenko%40jci.com%7C68fa10fc4c794bcb2ac108d92c480a8b%7Ca1f1e2147ded45b681a19e8ae3459641%7C0%7C1%7C637589510191097105%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=4CwmeXWH%2BWzfjD8%2FH1AvuU8zPQ%2BCdIdR2DpR7vIRTa4%3D&amp;reserved=0
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

Just, also sent an e-mail in response to Otavio on this.
Thanks for quick responses!!!


Using imx7d:

I noticed (as I am attempting to apply patches we use), that /arch/arm/mach-imx/cpuidle-imx7d.c exists in the 5.4.X.imx version we are currently using, but is not present in 5.12.  But mach-imx7d.c is.
 Will I have to add files (via patches) to fully support imx7d vs. what we had in the freescale 5.4.X.imx release?

Thanks a ton,
  Val

-----Original Message-----
From: Fabio Estevam <festevam@gmail.com> 
Sent: Thursday, June 10, 2021 4:14 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

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.

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Fabio Estevam]

On Thu, Jun 10, 2021 at 5:19 PM Val Kondratenko
<valeriy.kondratenko@jci.com> wrote:
>
> OK thanks.
>
> Next question - does it have full support for imx7d?

Yes, imx7d is well supported in the mainline kernel.

> I noticed (as I am attempting to apply patches we use), that /arch/arm/mach-imx/cpuidle-imx7d.c exists in the 5.4.X.imx version we are currently using, but is not present in 5.12.  But mach-imx7d.c is.
>  Will I have to add files (via patches) to fully support imx7d?

cpuidle is supported via PSCI implementation in U-Boot.

I suggest you to use U-Boot mainline too.

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

One other thing I see missing in 5.12, that was in freeescale 5.4, is the rpmsg (Remote Processor Messaging) functionality.

Thanks again!!!
 Val

-----Original Message-----
From: Fabio Estevam <festevam@gmail.com> 
Sent: Thursday, June 10, 2021 5:12 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

On Thu, Jun 10, 2021 at 5:19 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> OK thanks.
>
> Next question - does it have full support for imx7d?

Yes, imx7d is well supported in the mainline kernel.

> I noticed (as I am attempting to apply patches we use), that /arch/arm/mach-imx/cpuidle-imx7d.c exists in the 5.4.X.imx version we are currently using, but is not present in 5.12.  But mach-imx7d.c is.
>  Will I have to add files (via patches) to fully support imx7d?

cpuidle is supported via PSCI implementation in U-Boot.

I suggest you to use U-Boot mainline too.

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Fabio Estevam]

Hi Val,

On Fri, Jun 11, 2021 at 12:12 PM Val Kondratenko
<valeriy.kondratenko@jci.com> wrote:
>
> One other thing I see missing in 5.12, that was in freeescale 5.4, is the rpmsg (Remote Processor Messaging) functionality.

In mainline, this is handled by the drivers/remoteproc/imx_rproc.c driver.

Regards,

Fabio Estevam

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

Thanks!!!

-----Original Message-----
From: Fabio Estevam <festevam@gmail.com> 
Sent: Friday, June 11, 2021 12:19 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

Hi Val,

On Fri, Jun 11, 2021 at 12:12 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> One other thing I see missing in 5.12, that was in freeescale 5.4, is the rpmsg (Remote Processor Messaging) functionality.

In mainline, this is handled by the drivers/remoteproc/imx_rproc.c driver.

Regards,

Fabio Estevam

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

.. will probably be going to mainline uboot as well.

Are there any similar things (like cpuidle moving from kernel to uboot), that I would have to worry about?

Thanks in advance,
 Val

-----Original Message-----
From: Fabio Estevam <festevam@gmail.com> 
Sent: Thursday, June 10, 2021 5:12 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

On Thu, Jun 10, 2021 at 5:19 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> OK thanks.
>
> Next question - does it have full support for imx7d?

Yes, imx7d is well supported in the mainline kernel.

> I noticed (as I am attempting to apply patches we use), that /arch/arm/mach-imx/cpuidle-imx7d.c exists in the 5.4.X.imx version we are currently using, but is not present in 5.12.  But mach-imx7d.c is.
>  Will I have to add files (via patches) to fully support imx7d?

cpuidle is supported via PSCI implementation in U-Boot.

I suggest you to use U-Boot mainline too.

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Fabio Estevam]

On Wed, Jun 23, 2021 at 2:48 PM Val Kondratenko
<valeriy.kondratenko@jci.com> wrote:
>
> .. will probably be going to mainline uboot as well.
>
> Are there any similar things (like cpuidle moving from kernel to uboot), that I would have to worry about?

No, you should be good with tha mainline U-Boot and kernel combination.

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

Is the following a recommended upstream u-boot?

u-boot-v2021.04 from
https://source.denx.de/u-boot/u-boot/

The cpuidle functionality would be in?

arch/arm/mach-imx/mx7/psci-mx7.c

From when/which release U-boot started support cpuidle?

Is there any documentation on how to move the cpuidle functionality from kernel to u-boot?
What is involved there?

Thanks in advance,
 Val

-----Original Message-----
From: meta-freescale@lists.yoctoproject.org <meta-freescale@lists.yoctoproject.org> On Behalf Of Val Kondratenko via lists.yoctoproject.org
Sent: Friday, June 11, 2021 11:12 AM
To: Fabio Estevam <festevam@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

One other thing I see missing in 5.12, that was in freeescale 5.4, is the rpmsg (Remote Processor Messaging) functionality.

Thanks again!!!
 Val

-----Original Message-----
From: Fabio Estevam <festevam@gmail.com> 
Sent: Thursday, June 10, 2021 5:12 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

On Thu, Jun 10, 2021 at 5:19 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> OK thanks.
>
> Next question - does it have full support for imx7d?

Yes, imx7d is well supported in the mainline kernel.

> I noticed (as I am attempting to apply patches we use), that /arch/arm/mach-imx/cpuidle-imx7d.c exists in the 5.4.X.imx version we are currently using, but is not present in 5.12.  But mach-imx7d.c is.
>  Will I have to add files (via patches) to fully support imx7d?

cpuidle is supported via PSCI implementation in U-Boot.

I suggest you to use U-Boot mainline too.

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Fabio Estevam]

On Fri, Jun 25, 2021 at 2:53 PM Val Kondratenko
<valeriy.kondratenko@jci.com> wrote:
>
> Is the following a recommended upstream u-boot?
>
> u-boot-v2021.04 from
> https://source.denx.de/u-boot/u-boot/

Yes, that's a good one.

U-Boot 2021.07 should be available on July, 5th.

> The cpuidle functionality would be in?
>
> arch/arm/mach-imx/mx7/psci-mx7.c
>
> From when/which release U-boot started support cpuidle?
>
> Is there any documentation on how to move the cpuidle functionality from kernel to u-boot?
> What is involved there?

The PSCI mechanism in U-Boot will take care of it. No extra action is required.

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

Oops, sorry for duplicate (ignore), meant to send to someone else.

And thanks (again) for quick response,

 Val

-----Original Message-----
From: meta-freescale@lists.yoctoproject.org <meta-freescale@lists.yoctoproject.org> On Behalf Of Val Kondratenko via lists.yoctoproject.org
Sent: Friday, June 25, 2021 1:54 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>; Fabio Estevam <festevam@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

Is the following a recommended upstream u-boot?

u-boot-v2021.04 from
https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsource.denx.de%2Fu-boot%2Fu-boot%2F&amp;data=04%7C01%7Cvaleriy.kondratenko%40jci.com%7C9d81ccfd81c14c0c3f5c08d93806c619%7Ca1f1e2147ded45b681a19e8ae3459641%7C0%7C0%7C637602424008919863%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=W7VRDmOAXNwxGNXX4kRgOvSij%2BOFq6k5I%2Fy%2FaBVnpiA%3D&amp;reserved=0

The cpuidle functionality would be in?

arch/arm/mach-imx/mx7/psci-mx7.c

From when/which release U-boot started support cpuidle?

Is there any documentation on how to move the cpuidle functionality from kernel to u-boot?
What is involved there?

Thanks in advance,
 Val

-----Original Message-----
From: meta-freescale@lists.yoctoproject.org <meta-freescale@lists.yoctoproject.org> On Behalf Of Val Kondratenko via lists.yoctoproject.org
Sent: Friday, June 11, 2021 11:12 AM
To: Fabio Estevam <festevam@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

One other thing I see missing in 5.12, that was in freeescale 5.4, is the rpmsg (Remote Processor Messaging) functionality.

Thanks again!!!
 Val

-----Original Message-----
From: Fabio Estevam <festevam@gmail.com> 
Sent: Thursday, June 10, 2021 5:12 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

On Thu, Jun 10, 2021 at 5:19 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> OK thanks.
>
> Next question - does it have full support for imx7d?

Yes, imx7d is well supported in the mainline kernel.

> I noticed (as I am attempting to apply patches we use), that /arch/arm/mach-imx/cpuidle-imx7d.c exists in the 5.4.X.imx version we are currently using, but is not present in 5.12.  But mach-imx7d.c is.
>  Will I have to add files (via patches) to fully support imx7d?

cpuidle is supported via PSCI implementation in U-Boot.

I suggest you to use U-Boot mainline too.

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

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


Trying to compile the new kernel (and applying our patches from 5.4/modified).
Getting this error:

DEBUG: Executing shell function do_shared_workdir
cp: cannot stat 'Module.symvers': No such file or directory
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_shared_workdir

That is coming from attached patch file in:
  ./meta-freescale/recipes-kernel/kernel-modules/kernel-module-imx-gpu-viv

Does anyone know what that could be (looks like some type of symbol file)?
Will the meta-freescale area be something that has to be modified for kernel 5.12?

Thanks in advance,
 Val


-----Original Message-----
From: Fabio Estevam <festevam@gmail.com> 
Sent: Friday, June 25, 2021 2:11 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

On Fri, Jun 25, 2021 at 2:53 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> Is the following a recommended upstream u-boot?
>
> u-boot-v2021.04 from
> https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsour
> ce.denx.de%2Fu-boot%2Fu-boot%2F&amp;data=04%7C01%7Cvaleriy.kondratenko
> %40jci.com%7Cae9a307ad535470174e808d93804a3b9%7Ca1f1e2147ded45b681a19e
> 8ae3459641%7C0%7C1%7C637602414841277553%7CUnknown%7CTWFpbGZsb3d8eyJWIj
> oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&am
> p;sdata=u7VdtzbmyNsIyJAk5wMd%2BM%2FohubZx6qe6fwKmUEWvjA%3D&amp;reserve
> d=0

Yes, that's a good one.

U-Boot 2021.07 should be available on July, 5th.

> The cpuidle functionality would be in?
>
> arch/arm/mach-imx/mx7/psci-mx7.c
>
> From when/which release U-boot started support cpuidle?
>
> Is there any documentation on how to move the cpuidle functionality from kernel to u-boot?
> What is involved there?

The PSCI mechanism in U-Boot will take care of it. No extra action is required.

[-- Attachment #2: Add-makefile.patch --]
[-- Type: application/octet-stream, Size: 13254 bytes --]

Index: git/Makefile
===================================================================
--- /dev/null	1970-01-01 00:00:00.000000000 +0000
+++ git/Makefile	2017-06-27 12:07:11.931698672 -0500
@@ -0,0 +1,17 @@
+obj-m := galcore.o
+
+SRC := $(shell pwd)
+
+all:
+	$(MAKE) -C $(KERNEL_SRC) M=$(SRC)/src AQROOT=${PWD}/src
+	cp $(SRC)/src/Module.symvers $(PWD)
+	cp $(SRC)/src/modules.order $(PWD)
+
+modules_install:
+	$(MAKE) -C $(KERNEL_SRC) M=$(SRC)/src modules_install
+
+clean:
+	find . -name '*.o' -delete
+	rm -f *.o *~ core .depend .*.cmd *.ko *.mod.c
+	rm -f Module.markers Module.symvers modules.order
+	rm -rf .tmp_versions Modules.symvers
Index: git/src/hal/kernel/arch/makefile.linux
===================================================================
--- /dev/null	1970-01-01 00:00:00.000000000 +0000
+++ git/src/hal/kernel/arch/makefile.linux	2017-06-27 11:44:06.004826232 -0500
@@ -0,0 +1,91 @@
+##############################################################################
+#
+#    The MIT License (MIT)
+#
+#    Copyright (c) 2014 - 2017 Vivante Corporation
+#
+#    Permission is hereby granted, free of charge, to any person obtaining a
+#    copy of this software and associated documentation files (the "Software"),
+#    to deal in the Software without restriction, including without limitation
+#    the rights to use, copy, modify, merge, publish, distribute, sublicense,
+#    and/or sell copies of the Software, and to permit persons to whom the
+#    Software is furnished to do so, subject to the following conditions:
+#
+#    The above copyright notice and this permission notice shall be included in
+#    all copies or substantial portions of the Software.
+#
+#    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+#    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+#    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+#    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+#    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+#    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+#    DEALINGS IN THE SOFTWARE.
+#
+##############################################################################
+#
+#    The GPL License (GPL)
+#
+#    Copyright (C) 2014 - 2017 Vivante Corporation
+#
+#    This program is free software; you can redistribute it and/or
+#    modify it under the terms of the GNU General Public License
+#    as published by the Free Software Foundation; either version 2
+#    of the License, or (at your option) any later version.
+#
+#    This program is distributed in the hope that it will be useful,
+#    but WITHOUT ANY WARRANTY; without even the implied warranty of
+#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+#    GNU General Public License for more details.
+#
+#    You should have received a copy of the GNU General Public License
+#    along with this program; if not, write to the Free Software Foundation,
+#    Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+#
+##############################################################################
+#
+#    Note: This software is released under dual MIT and GPL licenses. A
+#    recipient may use this file under the terms of either the MIT license or
+#    GPL License. If you wish to use only one license not the other, you can
+#    indicate your decision by deleting one of the above license notices in your
+#    version of this file.
+#
+##############################################################################
+
+
+#
+# Linux build file for architecture dependent kernel HAL layer.
+#
+
+################################################################################
+# Include common definitions.
+
+include $(AQROOT)/makefile.linux.def
+
+################################################################################
+# Define a shortcut for the main target.
+
+STATIC = 1
+TARGET_NAME = libhalarchkernel.a
+
+################################################################################
+# Supply additional include directories.
+
+INCLUDE += -I$(AQROOT)/hal/kernel/inc
+INCLUDE += -I$(AQROOT)/hal/kernel/inc
+INCLUDE += -I$(AQROOT)/hal/kernel
+INCLUDE += -I$(AQROOT)/hal/kernel/arch
+ifeq ($(VIVANTE_ENABLE_VG),1)
+INCLUDE += -I$(AQROOT)/hal/kernel/archvg
+endif
+
+CFLAGS += $(INCLUDE) -Werror -ansi
+
+
+################################################################################
+# Describe object files.
+
+OBJECTS = $(OBJ_DIR)/gc_hal_kernel_context.o \
+          $(OBJ_DIR)/gc_hal_kernel_hardware.o
+
+include $(AQROOT)/common.target
Index: git/src/hal/kernel/archvg/makefile.linux
===================================================================
--- /dev/null	1970-01-01 00:00:00.000000000 +0000
+++ git/src/hal/kernel/archvg/makefile.linux	2017-06-27 11:44:06.004826232 -0500
@@ -0,0 +1,91 @@
+##############################################################################
+#
+#    The MIT License (MIT)
+#
+#    Copyright (c) 2014 - 2017 Vivante Corporation
+#
+#    Permission is hereby granted, free of charge, to any person obtaining a
+#    copy of this software and associated documentation files (the "Software"),
+#    to deal in the Software without restriction, including without limitation
+#    the rights to use, copy, modify, merge, publish, distribute, sublicense,
+#    and/or sell copies of the Software, and to permit persons to whom the
+#    Software is furnished to do so, subject to the following conditions:
+#
+#    The above copyright notice and this permission notice shall be included in
+#    all copies or substantial portions of the Software.
+#
+#    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+#    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+#    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+#    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+#    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+#    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+#    DEALINGS IN THE SOFTWARE.
+#
+##############################################################################
+#
+#    The GPL License (GPL)
+#
+#    Copyright (C) 2014 - 2017 Vivante Corporation
+#
+#    This program is free software; you can redistribute it and/or
+#    modify it under the terms of the GNU General Public License
+#    as published by the Free Software Foundation; either version 2
+#    of the License, or (at your option) any later version.
+#
+#    This program is distributed in the hope that it will be useful,
+#    but WITHOUT ANY WARRANTY; without even the implied warranty of
+#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+#    GNU General Public License for more details.
+#
+#    You should have received a copy of the GNU General Public License
+#    along with this program; if not, write to the Free Software Foundation,
+#    Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+#
+##############################################################################
+#
+#    Note: This software is released under dual MIT and GPL licenses. A
+#    recipient may use this file under the terms of either the MIT license or
+#    GPL License. If you wish to use only one license not the other, you can
+#    indicate your decision by deleting one of the above license notices in your
+#    version of this file.
+#
+##############################################################################
+
+
+#
+# Linux build file for architecture dependent kernel HAL layer.
+#
+
+################################################################################
+# Include common definitions.
+
+include $(AQROOT)/makefile.linux.def
+
+################################################################################
+# Define a shortcut for the main target.
+
+STATIC = 1
+
+TARGET_NAME = libhalarchkernelvg.a
+
+################################################################################
+# Supply additional include directories.
+
+INCLUDE += -I$(AQROOT)/hal/inc
+INCLUDE += -I$(AQROOT)/hal/user
+INCLUDE += -I$(AQROOT)/hal/kernel
+INCLUDE += -I$(AQROOT)/hal/kernel/arch
+ifeq ($(VIVANTE_ENABLE_VG), 1)
+INCLUDE += -I$(AQROOT)/hal/kernel/archvg
+endif
+
+CFLAGS += $(INCLUDE) -Werror -ansi
+
+################################################################################
+# Describe object files.
+
+OBJECTS = $(OBJ_DIR)/gc_hal_kernel_hardware_vg.o \
+          $(OBJ_DIR)/gc_hal_kernel_hardware_command_vg.o
+
+include $(AQROOT)/common.target
Index: git/src/hal/kernel/makefile.linux
===================================================================
--- /dev/null	1970-01-01 00:00:00.000000000 +0000
+++ git/src/hal/kernel/makefile.linux	2017-06-27 11:44:06.004826232 -0500
@@ -0,0 +1,107 @@
+##############################################################################
+#
+#    The MIT License (MIT)
+#
+#    Copyright (c) 2014 - 2017 Vivante Corporation
+#
+#    Permission is hereby granted, free of charge, to any person obtaining a
+#    copy of this software and associated documentation files (the "Software"),
+#    to deal in the Software without restriction, including without limitation
+#    the rights to use, copy, modify, merge, publish, distribute, sublicense,
+#    and/or sell copies of the Software, and to permit persons to whom the
+#    Software is furnished to do so, subject to the following conditions:
+#
+#    The above copyright notice and this permission notice shall be included in
+#    all copies or substantial portions of the Software.
+#
+#    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+#    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+#    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+#    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+#    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+#    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+#    DEALINGS IN THE SOFTWARE.
+#
+##############################################################################
+#
+#    The GPL License (GPL)
+#
+#    Copyright (C) 2014 - 2017 Vivante Corporation
+#
+#    This program is free software; you can redistribute it and/or
+#    modify it under the terms of the GNU General Public License
+#    as published by the Free Software Foundation; either version 2
+#    of the License, or (at your option) any later version.
+#
+#    This program is distributed in the hope that it will be useful,
+#    but WITHOUT ANY WARRANTY; without even the implied warranty of
+#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+#    GNU General Public License for more details.
+#
+#    You should have received a copy of the GNU General Public License
+#    along with this program; if not, write to the Free Software Foundation,
+#    Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+#
+##############################################################################
+#
+#    Note: This software is released under dual MIT and GPL licenses. A
+#    recipient may use this file under the terms of either the MIT license or
+#    GPL License. If you wish to use only one license not the other, you can
+#    indicate your decision by deleting one of the above license notices in your
+#    version of this file.
+#
+##############################################################################
+
+
+#
+# Linux build file for architecture dependent kernel HAL layer.
+#
+#
+
+
+################################################################################
+# Include common definitions.
+
+include $(AQROOT)/makefile.linux.def
+
+################################################################################
+# Define a shortcut for the main target.
+
+STATIC = 1
+TARGET_NAME = libhalkernel.a
+
+################################################################################
+# Supply additional include directories.
+
+INCLUDE += -I$(AQROOT)/hal/kernel/inc
+INCLUDE += -I$(AQROOT)/hal/kernel/inc
+INCLUDE += -I$(AQROOT)/hal/kernel/arch
+INCLUDE += -I$(AQROOT)/hal/kernel
+ifeq ($(VIVANTE_ENABLE_VG),1)
+INCLUDE += -I$(AQROOT)/hal/kernel/archvg
+endif
+INCLUDE += -I$(AQROOT)/hal/os/linux/kernel
+CFLAGS += $(INCLUDE) -Werror -ansi
+
+
+################################################################################
+# Describe object files.
+
+OBJECTS = $(OBJ_DIR)/gc_hal_kernel_command.o \
+          $(OBJ_DIR)/gc_hal_kernel_db.o \
+          $(OBJ_DIR)/gc_hal_kernel_debug.o \
+          $(OBJ_DIR)/gc_hal_kernel_event.o \
+          $(OBJ_DIR)/gc_hal_kernel_heap.o \
+          $(OBJ_DIR)/gc_hal_kernel.o \
+          $(OBJ_DIR)/gc_hal_kernel_mmu.o \
+          $(OBJ_DIR)/gc_hal_kernel_video_memory.o
+
+ifeq ($(VIVANTE_ENABLE_VG),1)
+OBJECTS += \
+		  $(OBJ_DIR)/gc_hal_kernel_command_vg.o \
+		  $(OBJ_DIR)/gc_hal_kernel_interrupt_vg.o \
+		  $(OBJ_DIR)/gc_hal_kernel_mmu_vg.o \
+		  $(OBJ_DIR)/gc_hal_kernel_vg.o
+endif
+
+include $(AQROOT)/common.target

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

.. resending, back to this, still seeing the error below.
Does anyone have any ideas of why "Module.symvers" would not be present in my 5.12 build, and how to get it there (or at least avoid the error).

Thanks,
 Val

-----Original Message-----
From: Val Kondratenko 
Sent: Tuesday, June 29, 2021 4:03 PM
To: Fabio Estevam <festevam@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: RE: [meta-freescale] Safe to upgrade to a Community BSP?


Trying to compile the new kernel (and applying our patches from 5.4/modified).
Getting this error:

DEBUG: Executing shell function do_shared_workdir
cp: cannot stat 'Module.symvers': No such file or directory
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_shared_workdir

That is coming from attached patch file in:
  ./meta-freescale/recipes-kernel/kernel-modules/kernel-module-imx-gpu-viv

Does anyone know what that could be (looks like some type of symbol file)?
Will the meta-freescale area be something that has to be modified for kernel 5.12?

Thanks in advance,
 Val


-----Original Message-----
From: Fabio Estevam <festevam@gmail.com> 
Sent: Friday, June 25, 2021 2:11 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

On Fri, Jun 25, 2021 at 2:53 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> Is the following a recommended upstream u-boot?
>
> u-boot-v2021.04 from
> https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsour
> ce.denx.de%2Fu-boot%2Fu-boot%2F&amp;data=04%7C01%7Cvaleriy.kondratenko
> %40jci.com%7Cae9a307ad535470174e808d93804a3b9%7Ca1f1e2147ded45b681a19e
> 8ae3459641%7C0%7C1%7C637602414841277553%7CUnknown%7CTWFpbGZsb3d8eyJWIj
> oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&am
> p;sdata=u7VdtzbmyNsIyJAk5wMd%2BM%2FohubZx6qe6fwKmUEWvjA%3D&amp;reserve
> d=0

Yes, that's a good one.

U-Boot 2021.07 should be available on July, 5th.

> The cpuidle functionality would be in?
>
> arch/arm/mach-imx/mx7/psci-mx7.c
>
> From when/which release U-boot started support cpuidle?
>
> Is there any documentation on how to move the cpuidle functionality from kernel to u-boot?
> What is involved there?

The PSCI mechanism in U-Boot will take care of it. No extra action is required.

Re: Safe to upgrade to a Community BSP?

[Val Kondratenko]

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

Is there any need to update to a newer meta-freescale version with upgrade from 5.4 to 5.12 kernel.

Thanks,
Val

From: Val Kondratenko
Sent: Thursday, June 10, 2021 8:34 AM
To: meta-freescale@lists.yoctoproject.org
Subject: Safe to upgrade to a Community BSP?


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?

Thanks in advance,
Val

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

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

Does anyone know when meta-freescale plans on releasing a new version of their kernel (i.e.-imx)?
Or where that information could be available?

Thanks, 
 Val

-----Original Message-----
From: Otavio Salvador <otavio.salvador@ossystems.com.br> 
Sent: Thursday, June 10, 2021 3:43 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

Hello Val,

The 5.12.x is based on mainline. It is totally safe and include very small set of changes on top of upstream.

Em qui., 10 de jun. de 2021 às 09:34, Val Kondratenko <valeriy.kondratenko@jci.com> escreveu:
>
>
>
> 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?
>
>
>
> Thanks in advance,
>
> Val
>
>
> 
>


-- 
Otavio Salvador                             O.S. Systems
https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ossystems.com.br%2F&amp;data=04%7C01%7Cvaleriy.kondratenko%40jci.com%7C68fa10fc4c794bcb2ac108d92c480a8b%7Ca1f1e2147ded45b681a19e8ae3459641%7C0%7C1%7C637589510191097105%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=r%2FuFSFBqT%2B1WdIyGGgW5bwH%2B1gFJQnGtJq5fyKkvYb0%3D&amp;reserved=0        https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcode.ossystems.com.br%2F&amp;data=04%7C01%7Cvaleriy.kondratenko%40jci.com%7C68fa10fc4c794bcb2ac108d92c480a8b%7Ca1f1e2147ded45b681a19e8ae3459641%7C0%7C1%7C637589510191097105%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=4CwmeXWH%2BWzfjD8%2FH1AvuU8zPQ%2BCdIdR2DpR7vIRTa4%3D&amp;reserved=0
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

Re: [meta-freescale] Safe to upgrade to a Community BSP?

[Val Kondratenko]

As is, in the 5.12 upstream branch, RPM (specifically imx7D to M4) should just work?
Amount of code in this area seems minimal compared to meta-freescale 5.4 releases.
With most of the functionality that used to be in /drivers/rpmsg/imx_rpmsg.c no longer present.

Thanks in advance,
  Val

-----Original Message-----
From: Fabio Estevam <festevam@gmail.com> 
Sent: Friday, June 11, 2021 12:19 PM
To: Val Kondratenko <valeriy.kondratenko@jci.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Safe to upgrade to a Community BSP?

Hi Val,

On Fri, Jun 11, 2021 at 12:12 PM Val Kondratenko <valeriy.kondratenko@jci.com> wrote:
>
> One other thing I see missing in 5.12, that was in freeescale 5.4, is the rpmsg (Remote Processor Messaging) functionality.

In mainline, this is handled by the drivers/remoteproc/imx_rproc.c driver.

Regards,

Fabio Estevam