Want to use linux-fslc 5.10 with Dunfell

Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

Hi,

I'm wanting to pull in 5.10 kernel into my Dunfell build that's currently
using 5.4.x.

I see there is a recipe for 5.10 kernel on master:

https://layers.openembedded.org/layerindex/recipe/58685/

However this link doesn't work
recipes-kernel/linux/recipes-kernel/linux/linux-imx.inc
<http://git.yoctoproject.org/cgit/cgit.cgi/meta-freescale/tree/recipes-kernel/linux/recipes-kernel/linux/linux-imx.inc?h=master>

I was hoping I could add this recipe and change my local.conf to:
PREFERRED_PROVIDER_virtual/kernel = "linux-fslc-imx"
PREFERRED_VERSION_linux-fslc-imx = "5.10%"

... and pull in 5.10 kernel but when I do a build it looks like I'm missing
linux-fslc-imx_5.10.bb maybe?  I pulled over the linux-fslc_5.10.bb from
above but looking at last build that worked I see linux-fslc_5.4.bb and
linux-fslc-imx_5.4.bb ... so I don't know all the info to make a
linux-fslc-imx_5_10.bb.

What is best way to pull in 5.10 kernel?

Thanks,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Otavio Salvador]

Hello Brian,

Em seg., 1 de mar. de 2021 às 14:07, Brian Hutchinson
<b.hutchman@gmail.com> escreveu:
> I'm wanting to pull in 5.10 kernel into my Dunfell build that's currently using 5.4.x.
>
> I see there is a recipe for 5.10 kernel on master:
>
> https://layers.openembedded.org/layerindex/recipe/58685/
>
> However this link doesn't work
> recipes-kernel/linux/recipes-kernel/linux/linux-imx.inc
>
> I was hoping I could add this recipe and change my local.conf to:
> PREFERRED_PROVIDER_virtual/kernel = "linux-fslc-imx"
> PREFERRED_VERSION_linux-fslc-imx = "5.10%"

linux-fslc-imx just has 5.4 Linux kernels. We have linux-fslc for 5.10.

> What is best way to pull in 5.10 kernel?

You should add it to your product layer and maintain it yourself.

-- 
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] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Mon, Mar 1, 2021, 12:17 PM Otavio Salvador <
otavio.salvador@ossystems.com.br> wrote:

> Hello Brian,
>
> Em seg., 1 de mar. de 2021 às 14:07, Brian Hutchinson
> <b.hutchman@gmail.com> escreveu:
> > I'm wanting to pull in 5.10 kernel into my Dunfell build that's
> currently using 5.4.x.
> >
> > I see there is a recipe for 5.10 kernel on master:
> >
> > https://layers.openembedded.org/layerindex/recipe/58685/
> >
> > However this link doesn't work
> > recipes-kernel/linux/recipes-kernel/linux/linux-imx.inc
> >
> > I was hoping I could add this recipe and change my local.conf to:
> > PREFERRED_PROVIDER_virtual/kernel = "linux-fslc-imx"
> > PREFERRED_VERSION_linux-fslc-imx = "5.10%"
>
> linux-fslc-imx just has 5.4 Linux kernels. We have linux-fslc for 5.10.
>
> > What is best way to pull in 5.10 kernel?
>
> You should add it to your product layer and maintain it yourself.
>
> --
> 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
>

Ok, don't quite know how to do that yet but will try to figure it out.

I thought something was readily available since I saw the 5.10 recipe.

Thanks,

Brian

>

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Otavio Salvador]

Em seg., 1 de mar. de 2021 às 15:29, Brian Hutchinson
<b.hutchman@gmail.com> escreveu:
> Ok, don't quite know how to do that yet but will try to figure it out.
>
> I thought something was readily available since I saw the 5.10 recipe.

It is ready for use in gatesgarth and master.

-- 
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] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Mon, Mar 1, 2021 at 2:35 PM Brian Hutchinson <b.hutchman@gmail.com>
wrote:

>
>
> On Mon, Mar 1, 2021 at 1:31 PM Otavio Salvador <
> otavio.salvador@ossystems.com.br> wrote:
>
>> Em seg., 1 de mar. de 2021 às 15:29, Brian Hutchinson
>> <b.hutchman@gmail.com> escreveu:
>> > Ok, don't quite know how to do that yet but will try to figure it out.
>> >
>> > I thought something was readily available since I saw the 5.10 recipe.
>>
>> It is ready for use in gatesgarth and master.
>>
>> --
>> 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
>>
>
> I looked using web git this morning before I tried anything and I didn't
> see 5.10 in meta-freescale/recipes-kernel/linux for Gatesgarth.  Only the
> one recipe I mentioned above in master is there.
>
> Regards,
>
> Brian
>
>
Can someone school me on how this works?  I guess I don't know or
understand the relationship between linux-fslc and linux-fslc-imx recipies
in meta-freescale/recipies-kernel/linux

Looking at the linux-fslc-imx_5.4.bb I've been using, it looks like 5.4.98
that i've been using really comes from nxp 5.4.24-1.1.0, kernel.org and
some patches???  And a note to "upgraders" that recipe shouldn't collect
patches but be applied to linux-fslc kernel tree.

Regards,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Peter Bergin]

Hi Brian,

On 2021-03-01 20:59, Brian Hutchinson wrote:
> Can someone school me on how this works?  I guess I don't know or 
> understand the relationship between linux-fslc and linux-fslc-imx 
> recipies in meta-freescale/recipies-kernel/linux

you have a bit more info in this thread 
https://lists.yoctoproject.org/g/meta-freescale/topic/80897983.

And you can also read the information in the recipes about different 
kernels their sources and how they are composed.

linux-fslc-imx: 
https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc-imx_5.4.bb#L12

linux-fslc: 
https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc_5.10.bb#L7

My view on this is that linux-fslc is mainline based and linux-fslc-imx 
is NXP based.

Best regards,
/Peter

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Tue, Mar 2, 2021 at 2:45 AM Peter Bergin <peter@berginkonsult.se> wrote:

> Hi Brian,
>
> On 2021-03-01 20:59, Brian Hutchinson wrote:
> > Can someone school me on how this works?  I guess I don't know or
> > understand the relationship between linux-fslc and linux-fslc-imx
> > recipies in meta-freescale/recipies-kernel/linux
>
> you have a bit more info in this thread
> https://lists.yoctoproject.org/g/meta-freescale/topic/80897983.
>
> And you can also read the information in the recipes about different
> kernels their sources and how they are composed.
>
> linux-fslc-imx:
>
> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc-imx_5.4.bb#L12
>
> linux-fslc:
>
> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc_5.10.bb#L7
>
> My view on this is that linux-fslc is mainline based and linux-fslc-imx
> is NXP based.
>
> Best regards,
> /Peter
>
>
Thanks Peter,

That helps a lot.  It was my intent to be using FSL kernel and turns out
I've been using linux-fslc-imx thus far.  When I first started working on
NXP SoC (switched from TI about a year ago) I was using NXP releases and
discovered the hard way their new releases were mainly geared at new boards
so that's when I switched to fslc.

Regards,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Tue, Mar 2, 2021 at 8:28 AM Brian Hutchinson via lists.yoctoproject.org
<b.hutchman=gmail.com@lists.yoctoproject.org> wrote:

>
> On Tue, Mar 2, 2021 at 2:45 AM Peter Bergin <peter@berginkonsult.se>
> wrote:
>
>> Hi Brian,
>>
>> On 2021-03-01 20:59, Brian Hutchinson wrote:
>> > Can someone school me on how this works?  I guess I don't know or
>> > understand the relationship between linux-fslc and linux-fslc-imx
>> > recipies in meta-freescale/recipies-kernel/linux
>>
>> you have a bit more info in this thread
>> https://lists.yoctoproject.org/g/meta-freescale/topic/80897983.
>>
>> And you can also read the information in the recipes about different
>> kernels their sources and how they are composed.
>>
>> linux-fslc-imx:
>>
>> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc-imx_5.4.bb#L12
>>
>> linux-fslc:
>>
>> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc_5.10.bb#L7
>>
>> My view on this is that linux-fslc is mainline based and linux-fslc-imx
>> is NXP based.
>>
>> Best regards,
>> /Peter
>>
>>
> Thanks Peter,
>
> That helps a lot.  It was my intent to be using FSL kernel and turns out
> I've been using linux-fslc-imx thus far.  When I first started working on
> NXP SoC (switched from TI about a year ago) I was using NXP releases and
> discovered the hard way their new releases were mainly geared at new boards
> so that's when I switched to fslc.
>
> Regards,
>
> Brian
>
>
Ok, forgive me but I'm obviously still in the weeds.  Still trying to pull
in linux 5.10 from master.  If linux-fslc is basically community kernel
with NXP fixes and patches mainlined ... why is there no COMPATIBLE_MACHINE
for imx8mmevk?

I did a clean checkout of gatesgarth, then pulled in the recipes for
linux-fslc_5.10 from master into sources/meta-freescale/recipes-kernel/linux
In my local.conf I set:

PREFERRED_PROVIDER_virtual/kernel = "linux-fslc" because it defaults to
"linux-fslc-imx" if I don't.

... then when I try to build I get COMPATIBLE_MACHINE errors.

Here's my local.conf for full disclosure:

PREFERRED_PROVIDER_virtual/kernel = "linux-fslc"
PREFERRED_VERSION_linux-fslc = "5.10%"
MACHINE ??= 'imx8mmevk'
DISTRO ?= 'poky'
PACKAGE_CLASSES ?= 'package_rpm'
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS ??= "\
   STOPTASKS,${TMPDIR},1G,100K \
   STOPTASKS,${DL_DIR},1G,100K \
   STOPTASKS,${SSTATE_DIR},1G,100K \
   STOPTASKS,/tmp,100M,100K \
   ABORT,${TMPDIR},100M,1K \
   ABORT,${DL_DIR},100M,1K \
   ABORT,${SSTATE_DIR},100M,1K \
   ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
CONF_VERSION = "1"

DL_DIR ?= "${BSPDIR}/downloads/"
ACCEPT_FSL_EULA = "1"

hutch@Gondor:~/yocto/imx8/fsl-community-bsp_gatesgarth/build$ bitbake
core-image-base
Loading cache: 100% |



                        |
ETA:  --:--:--
Loaded 0 entries from dependency cache.
Parsing recipes: 100%
|#############################################################################################################################################################################################################################################|
Time: 0:00:10
Parsing of 2286 .bb files complete (0 cached, 2286 parsed). 3492 targets,
234 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'virtual/kernel'
linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-dummy PROVIDES virtual/kernel but was skipped:
PREFERRED_PROVIDER_virtual/kernel set to linux-fslc, not linux-dummy


linux-qoriq PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-fslc-lts-4.19 PROVIDES virtual/kernel but was skipped: incompatible
with machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-gateworks-imx PROVIDES virtual/kernel but was skipped: incompatible
with machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-yocto-dev PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-advantech PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-fslc PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-kontron PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-fslc-qoriq PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-fslc-imx PROVIDES virtual/kernel but was skipped:
PREFERRED_PROVIDER_virtual/kernel set to linux-fslc, not linux-fslc-imx


linux-toradex PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-imx PROVIDES virtual/kernel but was skipped:
PREFERRED_PROVIDER_virtual/kernel set to linux-fslc, not linux-imx


linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-variscite PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-fslc PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-boundary PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-toradex PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


linux-congatec PROVIDES virtual/kernel but was skipped: incompatible with
machine imx8mmevk (not in COMPATIBLE_MACHINE)


ERROR: Required build target 'core-image-base' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-base',
'virtual/kernel']

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

Hello Brian,

On Tue, Mar 2, 2021 at 4:34 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> On Tue, Mar 2, 2021 at 8:28 AM Brian Hutchinson via lists.yoctoproject.org <b.hutchman=gmail.com@lists.yoctoproject.org> wrote:
>>
>>
>> On Tue, Mar 2, 2021 at 2:45 AM Peter Bergin <peter@berginkonsult.se> wrote:
>>>
>>> Hi Brian,
>>>
>>> On 2021-03-01 20:59, Brian Hutchinson wrote:
>>> > Can someone school me on how this works?  I guess I don't know or
>>> > understand the relationship between linux-fslc and linux-fslc-imx
>>> > recipies in meta-freescale/recipies-kernel/linux
>>>
>>> you have a bit more info in this thread
>>> https://lists.yoctoproject.org/g/meta-freescale/topic/80897983.
>>>
>>> And you can also read the information in the recipes about different
>>> kernels their sources and how they are composed.
>>>
>>> linux-fslc-imx:
>>> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc-imx_5.4.bb#L12
>>>
>>> linux-fslc:
>>> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc_5.10.bb#L7
>>>
>>> My view on this is that linux-fslc is mainline based and linux-fslc-imx
>>> is NXP based.
>>>
>>> Best regards,
>>> /Peter
>>>
>>
>> Thanks Peter,
>>
>> That helps a lot.  It was my intent to be using FSL kernel and turns out I've been using linux-fslc-imx thus far.  When I first started working on NXP SoC (switched from TI about a year ago) I was using NXP releases and discovered the hard way their new releases were mainly geared at new boards so that's when I switched to fslc.
>>
>> Regards,
>>
>> Brian
>>
>
> Ok, forgive me but I'm obviously still in the weeds.  Still trying to pull in linux 5.10 from master.  If linux-fslc is basically community kernel with NXP fixes and patches mainlined ... why is there no COMPATIBLE_MACHINE for imx8mmevk?

I've tried to touch this part in
https://lists.yoctoproject.org/g/meta-freescale/message/24551

Bottom line is: to use linux-fslc as a provider for virtual/kernel -
you need to change IMX_DEFAULT_BSP from "nxp" to "mainline" in the
conf/machine/imx8mmevk.conf, effectively changing from NXP BSP to
Community one.

This would have a lot of consequences though, as the support of mx8m
machines is not quite there yet.

>
> I did a clean checkout of gatesgarth, then pulled in the recipes for linux-fslc_5.10 from master into sources/meta-freescale/recipes-kernel/linux
> In my local.conf I set:
>
> PREFERRED_PROVIDER_virtual/kernel = "linux-fslc" because it defaults to "linux-fslc-imx" if I don't.
>
> ... then when I try to build I get COMPATIBLE_MACHINE errors.
>
> Here's my local.conf for full disclosure:
>
> PREFERRED_PROVIDER_virtual/kernel = "linux-fslc"
> PREFERRED_VERSION_linux-fslc = "5.10%"
> MACHINE ??= 'imx8mmevk'
> DISTRO ?= 'poky'
> PACKAGE_CLASSES ?= 'package_rpm'
> EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
> USER_CLASSES ?= "buildstats image-mklibs image-prelink"
> PATCHRESOLVE = "noop"
> BB_DISKMON_DIRS ??= "\
>    STOPTASKS,${TMPDIR},1G,100K \
>    STOPTASKS,${DL_DIR},1G,100K \
>    STOPTASKS,${SSTATE_DIR},1G,100K \
>    STOPTASKS,/tmp,100M,100K \
>    ABORT,${TMPDIR},100M,1K \
>    ABORT,${DL_DIR},100M,1K \
>    ABORT,${SSTATE_DIR},100M,1K \
>    ABORT,/tmp,10M,1K"
> PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
> CONF_VERSION = "1"
>
> DL_DIR ?= "${BSPDIR}/downloads/"
> ACCEPT_FSL_EULA = "1"
>
> hutch@Gondor:~/yocto/imx8/fsl-community-bsp_gatesgarth/build$ bitbake core-image-base
> Loading cache: 100% |                                                                                                                                                                                                                                              | ETA:  --:--:--
> Loaded 0 entries from dependency cache.
> Parsing recipes: 100% |#############################################################################################################################################################################################################################################| Time: 0:00:10
> Parsing of 2286 .bb files complete (0 cached, 2286 parsed). 3492 targets, 234 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing PROVIDES 'virtual/kernel'
> linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-dummy PROVIDES virtual/kernel but was skipped: PREFERRED_PROVIDER_virtual/kernel set to linux-fslc, not linux-dummy
> linux-qoriq PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-fslc-lts-4.19 PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-gateworks-imx PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-yocto-dev PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-advantech PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-fslc PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-kontron PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-fslc-qoriq PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-fslc-imx PROVIDES virtual/kernel but was skipped: PREFERRED_PROVIDER_virtual/kernel set to linux-fslc, not linux-fslc-imx
> linux-toradex PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-imx PROVIDES virtual/kernel but was skipped: PREFERRED_PROVIDER_virtual/kernel set to linux-fslc, not linux-imx
> linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-variscite PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-fslc PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-boundary PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-toradex PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> linux-congatec PROVIDES virtual/kernel but was skipped: incompatible with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> ERROR: Required build target 'core-image-base' has no buildable providers.
> Missing or unbuildable dependency chain was: ['core-image-base', 'virtual/kernel']
>
> 
>


-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Tue, Mar 2, 2021 at 1:23 PM Andrey Zhizhikin <andrey.z@gmail.com> wrote:

> Hello Brian,
>
> On Tue, Mar 2, 2021 at 4:34 PM Brian Hutchinson <b.hutchman@gmail.com>
> wrote:
> >
> > On Tue, Mar 2, 2021 at 8:28 AM Brian Hutchinson via
> lists.yoctoproject.org <b.hutchman=gmail.com@lists.yoctoproject.org>
> wrote:
> >>
> >>
> >> On Tue, Mar 2, 2021 at 2:45 AM Peter Bergin <peter@berginkonsult.se>
> wrote:
> >>>
> >>> Hi Brian,
> >>>
> >>> On 2021-03-01 20:59, Brian Hutchinson wrote:
> >>> > Can someone school me on how this works?  I guess I don't know or
> >>> > understand the relationship between linux-fslc and linux-fslc-imx
> >>> > recipies in meta-freescale/recipies-kernel/linux
> >>>
> >>> you have a bit more info in this thread
> >>> https://lists.yoctoproject.org/g/meta-freescale/topic/80897983.
> >>>
> >>> And you can also read the information in the recipes about different
> >>> kernels their sources and how they are composed.
> >>>
> >>> linux-fslc-imx:
> >>>
> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc-imx_5.4.bb#L12
> >>>
> >>> linux-fslc:
> >>>
> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc_5.10.bb#L7
> >>>
> >>> My view on this is that linux-fslc is mainline based and linux-fslc-imx
> >>> is NXP based.
> >>>
> >>> Best regards,
> >>> /Peter
> >>>
> >>
> >> Thanks Peter,
> >>
> >> That helps a lot.  It was my intent to be using FSL kernel and turns
> out I've been using linux-fslc-imx thus far.  When I first started working
> on NXP SoC (switched from TI about a year ago) I was using NXP releases and
> discovered the hard way their new releases were mainly geared at new boards
> so that's when I switched to fslc.
> >>
> >> Regards,
> >>
> >> Brian
> >>
> >
> > Ok, forgive me but I'm obviously still in the weeds.  Still trying to
> pull in linux 5.10 from master.  If linux-fslc is basically community
> kernel with NXP fixes and patches mainlined ... why is there no
> COMPATIBLE_MACHINE for imx8mmevk?
>
> I've tried to touch this part in
> https://lists.yoctoproject.org/g/meta-freescale/message/24551
>
> Bottom line is: to use linux-fslc as a provider for virtual/kernel -
> you need to change IMX_DEFAULT_BSP from "nxp" to "mainline" in the
> conf/machine/imx8mmevk.conf, effectively changing from NXP BSP to
> Community one.
>
> This would have a lot of consequences though, as the support of mx8m
> machines is not quite there yet.
>
> --
> Regards,
> Andrey.
>

Thanks Andrey,

"Consequences" is an understatement.  My heart sank as I started digging
into this and saw things like:

# Handle default kernel
IMX_DEFAULT_KERNEL = "linux-fslc-imx"
IMX_DEFAULT_KERNEL_mxs = "linux-fslc"
IMX_DEFAULT_KERNEL_mx5 = "linux-fslc"
IMX_DEFAULT_KERNEL_mx6 = "linux-fslc-imx"
IMX_DEFAULT_KERNEL_mx7 = "linux-fslc-imx"
IMX_DEFAULT_KERNEL_mx8 = "linux-fslc-imx"
IMX_DEFAULT_KERNEL_mx7ulp = "linux-fslc-imx"
IMX_DEFAULT_KERNEL_mx6sll = "linux-fslc-imx"
IMX_DEFAULT_KERNEL_mx6ul = "linux-fslc-imx"
IMX_DEFAULT_KERNEL_mx6ull = "linux-fslc-imx"
IMX_DEFAULT_KERNEL_use-mainline-bsp = "linux-fslc"

... in sources/meta-freescale/conf/machine/include/imx-base.inc

I really need at least Linux 5.10 for imx8 for some net-next features I
need.  I was hopeful when I was poking around and saw a 5.10 recipe but now
my hopes are dashed! :(

Regards,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Tue, Mar 2, 2021 at 2:34 PM Brian Hutchinson via lists.yoctoproject.org
<b.hutchman=gmail.com@lists.yoctoproject.org> wrote:

>
> On Tue, Mar 2, 2021 at 1:23 PM Andrey Zhizhikin <andrey.z@gmail.com>
> wrote:
>
>> Hello Brian,
>>
>> On Tue, Mar 2, 2021 at 4:34 PM Brian Hutchinson <b.hutchman@gmail.com>
>> wrote:
>> >
>> > On Tue, Mar 2, 2021 at 8:28 AM Brian Hutchinson via
>> lists.yoctoproject.org <b.hutchman=gmail.com@lists.yoctoproject.org>
>> wrote:
>> >>
>> >>
>> >> On Tue, Mar 2, 2021 at 2:45 AM Peter Bergin <peter@berginkonsult.se>
>> wrote:
>> >>>
>> >>> Hi Brian,
>> >>>
>> >>> On 2021-03-01 20:59, Brian Hutchinson wrote:
>> >>> > Can someone school me on how this works?  I guess I don't know or
>> >>> > understand the relationship between linux-fslc and linux-fslc-imx
>> >>> > recipies in meta-freescale/recipies-kernel/linux
>> >>>
>> >>> you have a bit more info in this thread
>> >>> https://lists.yoctoproject.org/g/meta-freescale/topic/80897983.
>> >>>
>> >>> And you can also read the information in the recipes about different
>> >>> kernels their sources and how they are composed.
>> >>>
>> >>> linux-fslc-imx:
>> >>>
>> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc-imx_5.4.bb#L12
>> >>>
>> >>> linux-fslc:
>> >>>
>> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc_5.10.bb#L7
>> >>>
>> >>> My view on this is that linux-fslc is mainline based and
>> linux-fslc-imx
>> >>> is NXP based.
>> >>>
>> >>> Best regards,
>> >>> /Peter
>> >>>
>> >>
>> >> Thanks Peter,
>> >>
>> >> That helps a lot.  It was my intent to be using FSL kernel and turns
>> out I've been using linux-fslc-imx thus far.  When I first started working
>> on NXP SoC (switched from TI about a year ago) I was using NXP releases and
>> discovered the hard way their new releases were mainly geared at new boards
>> so that's when I switched to fslc.
>> >>
>> >> Regards,
>> >>
>> >> Brian
>> >>
>> >
>> > Ok, forgive me but I'm obviously still in the weeds.  Still trying to
>> pull in linux 5.10 from master.  If linux-fslc is basically community
>> kernel with NXP fixes and patches mainlined ... why is there no
>> COMPATIBLE_MACHINE for imx8mmevk?
>>
>> I've tried to touch this part in
>> https://lists.yoctoproject.org/g/meta-freescale/message/24551
>>
>> Bottom line is: to use linux-fslc as a provider for virtual/kernel -
>> you need to change IMX_DEFAULT_BSP from "nxp" to "mainline" in the
>> conf/machine/imx8mmevk.conf, effectively changing from NXP BSP to
>> Community one.
>>
>> This would have a lot of consequences though, as the support of mx8m
>> machines is not quite there yet.
>>
>> --
>> Regards,
>> Andrey.
>>
>
> Thanks Andrey,
>
> "Consequences" is an understatement.  My heart sank as I started digging
> into this and saw things like:
>
> # Handle default kernel
> IMX_DEFAULT_KERNEL = "linux-fslc-imx"
> IMX_DEFAULT_KERNEL_mxs = "linux-fslc"
> IMX_DEFAULT_KERNEL_mx5 = "linux-fslc"
> IMX_DEFAULT_KERNEL_mx6 = "linux-fslc-imx"
> IMX_DEFAULT_KERNEL_mx7 = "linux-fslc-imx"
> IMX_DEFAULT_KERNEL_mx8 = "linux-fslc-imx"
> IMX_DEFAULT_KERNEL_mx7ulp = "linux-fslc-imx"
> IMX_DEFAULT_KERNEL_mx6sll = "linux-fslc-imx"
> IMX_DEFAULT_KERNEL_mx6ul = "linux-fslc-imx"
> IMX_DEFAULT_KERNEL_mx6ull = "linux-fslc-imx"
> IMX_DEFAULT_KERNEL_use-mainline-bsp = "linux-fslc"
>
> ... in sources/meta-freescale/conf/machine/include/imx-base.inc
>
> I really need at least Linux 5.10 for imx8 for some net-next features I
> need.  I was hopeful when I was poking around and saw a 5.10 recipe but now
> my hopes are dashed! :(
>
> Regards,
>
> Brian
>
>
Update.  So I messed around and changed the things Andrey mentioned and
tried another build just for kicks.  If completed with only one kernel
error:

|   OBJCOPY arch/arm64/boot/Image
|   DTC     arch/arm64/boot/dts/freescale/imx8mm-ddr4-evk.dtb
| make[2]: *** No rule to make target
'arch/arm64/boot/dts/freescale/imx8mm-ddr4-evk-revb.dtb'.  Stop.
| make[1]: ***
[/home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/build/tmp/work-shared/imx8mmevk/kernel-source/Makefile:1334:
freescale/imx8mm-ddr4-evk-revb.dtb] Error 2
| make: ***
[/home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/build/tmp/work-shared/imx8mmevk/kernel-source/Makefile:185:
__sub-make] Error 2
| WARNING: exit code 1 from a shell command.
|
ERROR: Task
(/home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/sources/meta-freescale/recipes-kernel/linux/linux-fslc_5.10.bb:do_compile)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 4575 tasks of which 1 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:
 /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/sources/meta-freescale/recipes-kernel/linux/linux-fslc_5.10.bb:do_compile

Summary: There were 3 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

... which is legit as it looks like the freescale .dts files of 5.10 are
different than before (no surprise) so I'll try to get past this and see
what happens.  I don't need all the NXP EVK stuff (video, touch screen,
wifi, bluetooth etc.) which is why I picked Yocto for distro to make a
smaller image than all those wayland options ... so just maybe it might
work???

Will report back soon ...

Regards,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Tue, Mar 2, 2021 at 6:01 PM Brian Hutchinson via lists.yoctoproject.org
<b.hutchman=gmail.com@lists.yoctoproject.org> wrote:

>
>
> On Tue, Mar 2, 2021 at 2:34 PM Brian Hutchinson via lists.yoctoproject.org
> <b.hutchman=gmail.com@lists.yoctoproject.org> wrote:
>
>>
>> On Tue, Mar 2, 2021 at 1:23 PM Andrey Zhizhikin <andrey.z@gmail.com>
>> wrote:
>>
>>> Hello Brian,
>>>
>>> On Tue, Mar 2, 2021 at 4:34 PM Brian Hutchinson <b.hutchman@gmail.com>
>>> wrote:
>>> >
>>> > On Tue, Mar 2, 2021 at 8:28 AM Brian Hutchinson via
>>> lists.yoctoproject.org <b.hutchman=gmail.com@lists.yoctoproject.org>
>>> wrote:
>>> >>
>>> >>
>>> >> On Tue, Mar 2, 2021 at 2:45 AM Peter Bergin <peter@berginkonsult.se>
>>> wrote:
>>> >>>
>>> >>> Hi Brian,
>>> >>>
>>> >>> On 2021-03-01 20:59, Brian Hutchinson wrote:
>>> >>> > Can someone school me on how this works?  I guess I don't know or
>>> >>> > understand the relationship between linux-fslc and linux-fslc-imx
>>> >>> > recipies in meta-freescale/recipies-kernel/linux
>>> >>>
>>> >>> you have a bit more info in this thread
>>> >>> https://lists.yoctoproject.org/g/meta-freescale/topic/80897983.
>>> >>>
>>> >>> And you can also read the information in the recipes about different
>>> >>> kernels their sources and how they are composed.
>>> >>>
>>> >>> linux-fslc-imx:
>>> >>>
>>> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc-imx_5.4.bb#L12
>>> >>>
>>> >>> linux-fslc:
>>> >>>
>>> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc_5.10.bb#L7
>>> >>>
>>> >>> My view on this is that linux-fslc is mainline based and
>>> linux-fslc-imx
>>> >>> is NXP based.
>>> >>>
>>> >>> Best regards,
>>> >>> /Peter
>>> >>>
>>> >>
>>> >> Thanks Peter,
>>> >>
>>> >> That helps a lot.  It was my intent to be using FSL kernel and turns
>>> out I've been using linux-fslc-imx thus far.  When I first started working
>>> on NXP SoC (switched from TI about a year ago) I was using NXP releases and
>>> discovered the hard way their new releases were mainly geared at new boards
>>> so that's when I switched to fslc.
>>> >>
>>> >> Regards,
>>> >>
>>> >> Brian
>>> >>
>>> >
>>> > Ok, forgive me but I'm obviously still in the weeds.  Still trying to
>>> pull in linux 5.10 from master.  If linux-fslc is basically community
>>> kernel with NXP fixes and patches mainlined ... why is there no
>>> COMPATIBLE_MACHINE for imx8mmevk?
>>>
>>> I've tried to touch this part in
>>> https://lists.yoctoproject.org/g/meta-freescale/message/24551
>>>
>>> Bottom line is: to use linux-fslc as a provider for virtual/kernel -
>>> you need to change IMX_DEFAULT_BSP from "nxp" to "mainline" in the
>>> conf/machine/imx8mmevk.conf, effectively changing from NXP BSP to
>>> Community one.
>>>
>>> This would have a lot of consequences though, as the support of mx8m
>>> machines is not quite there yet.
>>>
>>> --
>>> Regards,
>>> Andrey.
>>>
>>
>> Thanks Andrey,
>>
>> "Consequences" is an understatement.  My heart sank as I started digging
>> into this and saw things like:
>>
>> # Handle default kernel
>> IMX_DEFAULT_KERNEL = "linux-fslc-imx"
>> IMX_DEFAULT_KERNEL_mxs = "linux-fslc"
>> IMX_DEFAULT_KERNEL_mx5 = "linux-fslc"
>> IMX_DEFAULT_KERNEL_mx6 = "linux-fslc-imx"
>> IMX_DEFAULT_KERNEL_mx7 = "linux-fslc-imx"
>> IMX_DEFAULT_KERNEL_mx8 = "linux-fslc-imx"
>> IMX_DEFAULT_KERNEL_mx7ulp = "linux-fslc-imx"
>> IMX_DEFAULT_KERNEL_mx6sll = "linux-fslc-imx"
>> IMX_DEFAULT_KERNEL_mx6ul = "linux-fslc-imx"
>> IMX_DEFAULT_KERNEL_mx6ull = "linux-fslc-imx"
>> IMX_DEFAULT_KERNEL_use-mainline-bsp = "linux-fslc"
>>
>> ... in sources/meta-freescale/conf/machine/include/imx-base.inc
>>
>> I really need at least Linux 5.10 for imx8 for some net-next features I
>> need.  I was hopeful when I was poking around and saw a 5.10 recipe but now
>> my hopes are dashed! :(
>>
>> Regards,
>>
>> Brian
>>
>>
> Update.  So I messed around and changed the things Andrey mentioned and
> tried another build just for kicks.  If completed with only one kernel
> error:
>
> |   OBJCOPY arch/arm64/boot/Image
> |   DTC     arch/arm64/boot/dts/freescale/imx8mm-ddr4-evk.dtb
> | make[2]: *** No rule to make target
> 'arch/arm64/boot/dts/freescale/imx8mm-ddr4-evk-revb.dtb'.  Stop.
> | make[1]: ***
> [/home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/build/tmp/work-shared/imx8mmevk/kernel-source/Makefile:1334:
> freescale/imx8mm-ddr4-evk-revb.dtb] Error 2
> | make: ***
> [/home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/build/tmp/work-shared/imx8mmevk/kernel-source/Makefile:185:
> __sub-make] Error 2
> | WARNING: exit code 1 from a shell command.
> |
> ERROR: Task
> (/home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/sources/meta-freescale/recipes-kernel/linux/linux-fslc_5.10.bb:do_compile)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 4575 tasks of which 1 didn't need to be
> rerun and 1 failed.
>
> Summary: 1 task failed:
>
>  /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/sources/meta-freescale/recipes-kernel/linux/linux-fslc_5.10.bb:do_compile
>
> Summary: There were 3 WARNING messages shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>
> ... which is legit as it looks like the freescale .dts files of 5.10 are
> different than before (no surprise) so I'll try to get past this and see
> what happens.  I don't need all the NXP EVK stuff (video, touch screen,
> wifi, bluetooth etc.) which is why I picked Yocto for distro to make a
> smaller image than all those wayland options ... so just maybe it might
> work???
>
> Will report back soon ...
>
> Regards,
>
> Brian
>
>
Yet another update.  I further modified my  machine .conf to remove .dtb's
and features I didn't need and finally got the board booting 5.10.18!  When
I dd the wic image to sdcard it wouldn't boot so I've got a u-boot issue
somewhere but I wrote previous version of u-boot with dd and was able to
get it to boot.

Thank you all for putting up with me once again and keeping me out of the
weeds.

Now the work begins trying to get some net-next stuff working.

Regards,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

Otavio,  tell me again why I'm still getting this:

[    1.853583] imx-sdma 302c0000.dma-controller: Direct firmware load for
imx/sdma/sdma-imx7d.bin failed with error -2
[    1.861409] imx-sdma 302c0000.dma-controller: Falling back to sysfs
fallback for: imx/sdma/sdma-imx7d.bin

It needs to be a loadable module or something?

Anyway ... for the curious ... here's the boot messages:

Booting from mmc ...
27692 bytes read in 7 ms (3.8 MiB/s)
## Flattened Device Tree blob at 43000000
  Booting using the fdt blob at 0x43000000
  Using Device Tree in place at 0000000043000000, end 0000000043009c2b

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.10.18+ge96f454f9d4b (oe-user@oe-host)
(aarch64-poky-linux-gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35.1) #1 SMP
Tue Feb 23 21:32:29 UTC 2021
[    0.000000] Machine model: FSL i.MX8MM EVK board
[    0.000000] earlycon: ec_imx6q0 at MMIO 0x0000000030890000 (options
'115200')
[    0.000000] printk: bootconsole [ec_imx6q0] enabled
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Reserved 64 MiB at 0x00000000ba000000
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000040000000-0x000000007fffffff]
[    0.000000]   DMA32    [mem 0x0000000080000000-0x00000000bdffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000] Initmem setup node 0 [mem
0x0000000040000000-0x00000000bdffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 31 pages/cpu s88016 r8192 d30768 u126976
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages:
508032
[    0.000000] Kernel command line: console=ttymxc1,115200
earlycon=ec_imx6q,0x30890000,115200 root=/dev/mmcblk1p2 rootwait rw
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152
bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576
bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] software IO TLB: mapped [mem
0x000000007bfff000-0x000000007ffff000] (64MB)
[    0.000000] Memory: 1857628K/2064384K available (12992K kernel code,
2688K rwdata, 4752K rodata, 2944K init, 11217K bss, 141220K reserved,
65536K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Running RCU self tests
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU lockdep checking is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to
nr_cpu_ids=4.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is
25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 128 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: CPU0: found redistributor 0 region
0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] random: get_random_bytes called from
start_kernel+0x3b8/0x5bc with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff
max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[    0.000004] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every
2199023255500ns
[    0.008595] Console: colour dummy device 80x25
[    0.012528] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc.,
Ingo Molnar
[    0.020311] ... MAX_LOCKDEP_SUBCLASSES:  8
[    0.024423] ... MAX_LOCK_DEPTH:          48
[    0.028623] ... MAX_LOCKDEP_KEYS:        8192
[    0.032998] ... CLASSHASH_SIZE:          4096
[    0.037373] ... MAX_LOCKDEP_ENTRIES:     32768
[    0.041836] ... MAX_LOCKDEP_CHAINS:      65536
[    0.046298] ... CHAINHASH_SIZE:          32768
[    0.050761]  memory used by lock dependency info: 6365 kB
[    0.056186]  memory used for stack traces: 4224 kB
[    0.060998]  per task-struct memory footprint: 1920 bytes
[    0.066458] Calibrating delay loop (skipped), value calculated using
timer frequency.. 16.00 BogoMIPS (lpj=32000)
[    0.076753] pid_max: default: 32768 minimum: 301
[    0.081649] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes,
linear)
[    0.088836] Mountpoint-cache hash table entries: 4096 (order: 3, 32768
bytes, linear)
[    0.100799] rcu: Hierarchical SRCU implementation.
[    0.103620] EFI services will not be available.
[    0.108064] smp: Bringing up secondary CPUs ...
[    0.113688] Detected VIPT I-cache on CPU1
[    0.113719] GICv3: CPU1: found redistributor 1 region
0:0x00000000388a0000
[    0.113787] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.116193] Detected VIPT I-cache on CPU2
[    0.116222] GICv3: CPU2: found redistributor 2 region
0:0x00000000388c0000
[    0.116269] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.118347] Detected VIPT I-cache on CPU3
[    0.118374] GICv3: CPU3: found redistributor 3 region
0:0x00000000388e0000
[    0.118417] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.118923] smp: Brought up 1 node, 4 CPUs
[    0.172714] SMP: Total of 4 processors activated.
[    0.177440] CPU features: detected: 32-bit EL0 Support
[    0.182604] CPU features: detected: CRC32 instructions
[    0.187977] CPU: All CPU(s) started at EL2
[    0.191983] alternatives: patching kernel code
[    0.198267] devtmpfs: initialized
[    0.223820] clocksource: jiffies: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.230838] futex hash table entries: 1024 (order: 5, 131072 bytes,
linear)
[    0.241943] DMI not present or invalid.
[    0.243645] NET: Registered protocol family 16
[    0.253716] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic
allocations
[    0.258057] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic
allocations
[    0.266463] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for
atomic allocations
[    0.275665] thermal_sys: Registered thermal governor 'step_wise'
[    0.276504] cpuidle: using governor menu
[    0.283990] hw-breakpoint: found 6 breakpoint and 4 watchpoint
registers.
[    0.290817] ASID allocator initialised with 65536 entries
[    0.404616] mxs-dma 33000000.dma-controller: probe deferral not
supported
[    0.411921] iommu: Default domain type: Translated
[    0.414682] vgaarb: loaded
[    0.418433] SCSI subsystem initialized
[    0.421709] usbcore: registered new interface driver usbfs
[    0.426158] usbcore: registered new interface driver hub
[    0.431667] usbcore: registered new device driver usb
[    0.438737] mc: Linux media interface: v0.10
[    0.440784] videodev: Linux video capture interface: v2.00
[    0.447877] Advanced Linux Sound Architecture Driver Initialized.
[    0.454468] Bluetooth: Core ver 2.22
[    0.455963] NET: Registered protocol family 31
[    0.460375] Bluetooth: HCI device and connection manager initialized
[    0.466799] Bluetooth: HCI socket layer initialized
[    0.471674] Bluetooth: L2CAP socket layer initialized
[    0.476810] Bluetooth: SCO socket layer initialized
[    0.482998] clocksource: Switched to clocksource arch_sys_counter
[    1.592654] VFS: Disk quotas dquot_6.6.0
[    1.593873] VFS: Dquot-cache hash table entries: 512 (order 0, 4096
bytes)
[    1.627505] NET: Registered protocol family 2
[    1.630537] tcp_listen_portaddr_hash hash table entries: 1024 (order: 4,
81920 bytes, linear)
[    1.638030] TCP established hash table entries: 16384 (order: 5, 131072
bytes, linear)
[    1.646127] TCP bind hash table entries: 16384 (order: 8, 1179648 bytes,
linear)
[    1.654916] TCP: Hash tables configured (established 16384 bind 16384)
[    1.660219] UDP hash table entries: 1024 (order: 5, 163840 bytes,
linear)
[    1.666851] UDP-Lite hash table entries: 1024 (order: 5, 163840 bytes,
linear)
[    1.674412] NET: Registered protocol family 1
[    1.679881] RPC: Registered named UNIX socket transport module.
[    1.684045] RPC: Registered udp transport module.
[    1.688747] RPC: Registered tcp transport module.
[    1.693471] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.701290] PCI: CLS 0 bytes, default 64
[    1.706353] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7
counters available
[    1.715759] Initialise system trusted keyrings
[    1.717922] workingset: timestamp_bits=62 max_order=19 bucket_order=0
[    1.748642] NFS: Registering the id_resolver key type
[    1.750938] Key type id_resolver registered
[    1.755135] Key type id_legacy registered
[    1.759398] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.765990] jffs2: version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
[    1.773635] fuse: init (API version 7.32)
[    1.814005] Key type asymmetric registered
[    1.815465] Asymmetric key parser 'x509' registered
[    1.820278] io scheduler mq-deadline registered
[    1.824788] io scheduler kyber registered
[    1.853583] imx-sdma 302c0000.dma-controller: Direct firmware load for
imx/sdma/sdma-imx7d.bin failed with error -2
[    1.861409] imx-sdma 302c0000.dma-controller: Falling back to sysfs
fallback for: imx/sdma/sdma-imx7d.bin
[    1.888811] SoC: i.MX8MM revision 1.0
[    1.891863] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 34,
base_baud = 1500000) is a IMX
[    1.898749] printk: console [ttymxc1] enabled
[    1.898749] printk: console [ttymxc1] enabled
[    1.907214] printk: bootconsole [ec_imx6q0] disabled
[    1.907214] printk: bootconsole [ec_imx6q0] disabled
[    1.953009] brd: module loaded
[    1.992254] loop: module loaded
[    2.002315] libphy: Fixed MDIO Bus: probed
[    2.008011] CAN device driver interface
[    2.012935] usbcore: registered new interface driver r8152
[    2.018570] usbcore: registered new interface driver lan78xx
[    2.024411] usbcore: registered new interface driver asix
[    2.029973] usbcore: registered new interface driver ax88179_178a
[    2.036213] usbcore: registered new interface driver cdc_ether
[    2.042224] usbcore: registered new interface driver smsc95xx
[    2.048115] usbcore: registered new interface driver net1080
[    2.053919] usbcore: registered new interface driver cdc_subset
[    2.059978] usbcore: registered new interface driver zaurus
[    2.065689] usbcore: registered new interface driver MOSCHIP
usb-ethernet driver
[    2.073272] usbcore: registered new interface driver cdc_ncm
[    2.079012] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.085591] ehci-pci: EHCI PCI platform driver
[    2.090185] ehci-mxc: Freescale On-Chip EHCI Host driver
[    2.096261] usbcore: registered new interface driver usb-storage
[    2.108660] input: 30370000.snvs:snvs-powerkey as
/devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0

[    2.129549] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[    2.136022] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to
1970-01-01T00:00:00 UTC (0)
[    2.145711] i2c /dev entries driver
[    2.156172] Bluetooth: HCI UART driver ver 2.3
[    2.160770] Bluetooth: HCI UART protocol H4 registered
[    2.166164] Bluetooth: HCI UART protocol LL registered
[    2.175841] sdhci: Secure Digital Host Controller Interface driver
[    2.182080] sdhci: Copyright(c) Pierre Ossman
[    2.186488] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.194164] mmc1: CQHCI version 5.10
[    2.194172] mmc2: CQHCI version 5.10
[    2.204129] caam 30900000.crypto: RNG4 SH0 was previously instantiated
without prediction resistance. Tearing it down
[    2.214870] caam 30900000.crypto: Deinstantiated RNG4 SH0
[    2.220348] caam 30900000.crypto: Instantiated RNG4 SH0
[    2.225625] caam 30900000.crypto: RNG4 SH1 was previously instantiated
without prediction resistance. Tearing it down
[    2.228815] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using
ADMA
[    2.236297] caam 30900000.crypto: Deinstantiated RNG4 SH1
[    2.238678] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using
ADMA
[    2.256028] caam 30900000.crypto: Instantiated RNG4 SH1
[    2.261564] caam 30900000.crypto: device ID = 0x0a16040100000000 (Era 9)
[    2.268373] caam 30900000.crypto: job rings = 3, qi = 0
[    2.317047] caam algorithms registered in /proc/crypto
[    2.322719] mmc1: host does not support reading read-only switch,
assuming write-enable
[    2.330944] caam 30900000.crypto: caam pkc algorithms registered in
/proc/crypto
[    2.338549] caam 30900000.crypto: registering rng-caam
[    2.344246] mmc1: new high speed SDHC card at address aaaa
[    2.352113] mmcblk1: mmc1:aaaa SL16G 14.8 GiB
[    2.357695] mmc2: Command Queue Engine enabled
[    2.362680] mmc2: new DDR MMC card at address 0001
[    2.365552]  mmcblk1: p1 p2
[    2.369634] mmcblk2: mmc2:0001 DG4016 7.49 GiB
[    2.372982] usbcore: registered new interface driver usbhid
[    2.375485] mmcblk2boot0: mmc2:0001 DG4016 partition 1 4.00 MiB
[    2.380564] usbhid: USB HID core driver
[    2.384248] optee: probing for conduit method.
[    2.386647] random: fast init done
[    2.390467] optee: revision 3.2 (6d99b525)
[    2.395465] mmcblk2boot1: mmc2:0001 DG4016 partition 2 4.00 MiB
[    2.399823] optee: dynamic shared memory is enabled
[    2.403164] mmcblk2gp0: mmc2:0001 DG4016 partition 4 3.52 GiB
[    2.408849] optee: initialized driver
[    2.419221] random: crng init done
[    2.419691] mmcblk2rpmb: mmc2:0001 DG4016 partition 3 4.00 MiB, chardev
(247:0)
[    2.437017] NET: Registered protocol family 10
[    2.445123] Segment Routing with IPv6
[    2.449078] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    2.456891] NET: Registered protocol family 17
[    2.461441] can: controller area network core
[    2.466153] NET: Registered protocol family 29
[    2.470729] can: raw protocol
[    2.473861] can: broadcast manager protocol
[    2.478207] can: netlink gateway - max_hops=1
[    2.483224] Key type dns_resolver registered
[    2.488220] Loading compiled-in X.509 certificates
[    2.610488] usb_phy_generic usbphynop1: supply vcc not found, using
dummy regulator
[    2.620004] usb_phy_generic usbphynop2: supply vcc not found, using
dummy regulator
[    2.629405] imx-i2c 30a20000.i2c: can't get pinctrl, bus recovery not
supported
[    2.640212] i2c i2c-0: IMX I2C adapter registered
[    2.646483] imx-i2c 30a30000.i2c: can't get pinctrl, bus recovery not
supported
[    2.656217] i2c i2c-1: IMX I2C adapter registered
[    2.662379] imx-i2c 30a40000.i2c: can't get pinctrl, bus recovery not
supported
[    2.671547] i2c i2c-2: IMX I2C adapter registered
[    2.677890] imx_usb 32e40000.usb: No over current polarity defined
[    2.692395] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 2 mkt segment
2 supported-hw 0x4 0x4
[    2.707855] cfg80211: Loading compiled-in X.509 certificates for
regulatory database
[    2.722368] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    2.733458] platform regulatory.0: Direct firmware load for
regulatory.db failed with error -2
[    2.735039] ALSA device list:
[    2.742188] platform regulatory.0: Falling back to sysfs fallback for:
regulatory.db
[    2.745197]   No soundcards found.
[    2.889844] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data
mode. Opts: (null)
[    2.898245] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    2.909022] devtmpfs: mounted
[    2.914214] Freeing unused kernel memory: 2944K
[    2.919148] Run /sbin/init as init process
INIT: version 2.97 booting
Framebuffer /dev/fb0 not detected
Boot splashscreen disabled
Starting udev
[    7.511937] udevd[196]: starting version 3.2.9
[    8.419396] udevd[198]: starting eudev-3.2.9
[    9.479877] imx-sdma 302c0000.dma-controller: loaded firmware 4.5
[    9.479881] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
[    9.486229] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5
[   11.472352] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[   19.231419] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   19.236832] Bluetooth: BNEP socket layer initialized
umount: can't unmount /mnt/.psplash: No such file or directory

Poky (Yocto Project Reference Distro) 3.2.2 imx8mmevk /dev/ttymxc1

imx8mmevk login:
Poky (Yocto Project Reference Distro) 3.2.2 imx8mmevk /dev/ttymxc1

imx8mmevk login: root
root@imx8mmevk:~# uname -a
Linux imx8mmevk 5.10.18+ge96f454f9d4b #1 SMP Tue Feb 23 21:32:29 UTC 2021
aarch64 GNU/Linux
root@imx8mmevk:~#

On Wed, Mar 3, 2021 at 10:31 AM Brian Hutchinson via lists.yoctoproject.org
<b.hutchman=gmail.com@lists.yoctoproject.org> wrote:

> On Tue, Mar 2, 2021 at 6:01 PM Brian Hutchinson via lists.yoctoproject.org
> <b.hutchman=gmail.com@lists.yoctoproject.org> wrote:
>
>>
>>
>> On Tue, Mar 2, 2021 at 2:34 PM Brian Hutchinson via
>> lists.yoctoproject.org <b.hutchman=gmail.com@lists.yoctoproject.org>
>> wrote:
>>
>>>
>>> On Tue, Mar 2, 2021 at 1:23 PM Andrey Zhizhikin <andrey.z@gmail.com>
>>> wrote:
>>>
>>>> Hello Brian,
>>>>
>>>> On Tue, Mar 2, 2021 at 4:34 PM Brian Hutchinson <b.hutchman@gmail.com>
>>>> wrote:
>>>> >
>>>> > On Tue, Mar 2, 2021 at 8:28 AM Brian Hutchinson via
>>>> lists.yoctoproject.org <b.hutchman=gmail.com@lists.yoctoproject.org>
>>>> wrote:
>>>> >>
>>>> >>
>>>> >> On Tue, Mar 2, 2021 at 2:45 AM Peter Bergin <peter@berginkonsult.se>
>>>> wrote:
>>>> >>>
>>>> >>> Hi Brian,
>>>> >>>
>>>> >>> On 2021-03-01 20:59, Brian Hutchinson wrote:
>>>> >>> > Can someone school me on how this works?  I guess I don't know or
>>>> >>> > understand the relationship between linux-fslc and linux-fslc-imx
>>>> >>> > recipies in meta-freescale/recipies-kernel/linux
>>>> >>>
>>>> >>> you have a bit more info in this thread
>>>> >>> https://lists.yoctoproject.org/g/meta-freescale/topic/80897983.
>>>> >>>
>>>> >>> And you can also read the information in the recipes about different
>>>> >>> kernels their sources and how they are composed.
>>>> >>>
>>>> >>> linux-fslc-imx:
>>>> >>>
>>>> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc-imx_5.4.bb#L12
>>>> >>>
>>>> >>> linux-fslc:
>>>> >>>
>>>> https://github.com/Freescale/meta-freescale/blob/9de81869018e78b8b861513735b85c2dbc33ca0b/recipes-kernel/linux/linux-fslc_5.10.bb#L7
>>>> >>>
>>>> >>> My view on this is that linux-fslc is mainline based and
>>>> linux-fslc-imx
>>>> >>> is NXP based.
>>>> >>>
>>>> >>> Best regards,
>>>> >>> /Peter
>>>> >>>
>>>> >>
>>>> >> Thanks Peter,
>>>> >>
>>>> >> That helps a lot.  It was my intent to be using FSL kernel and turns
>>>> out I've been using linux-fslc-imx thus far.  When I first started working
>>>> on NXP SoC (switched from TI about a year ago) I was using NXP releases and
>>>> discovered the hard way their new releases were mainly geared at new boards
>>>> so that's when I switched to fslc.
>>>> >>
>>>> >> Regards,
>>>> >>
>>>> >> Brian
>>>> >>
>>>> >
>>>> > Ok, forgive me but I'm obviously still in the weeds.  Still trying to
>>>> pull in linux 5.10 from master.  If linux-fslc is basically community
>>>> kernel with NXP fixes and patches mainlined ... why is there no
>>>> COMPATIBLE_MACHINE for imx8mmevk?
>>>>
>>>> I've tried to touch this part in
>>>> https://lists.yoctoproject.org/g/meta-freescale/message/24551
>>>>
>>>> Bottom line is: to use linux-fslc as a provider for virtual/kernel -
>>>> you need to change IMX_DEFAULT_BSP from "nxp" to "mainline" in the
>>>> conf/machine/imx8mmevk.conf, effectively changing from NXP BSP to
>>>> Community one.
>>>>
>>>> This would have a lot of consequences though, as the support of mx8m
>>>> machines is not quite there yet.
>>>>
>>>> --
>>>> Regards,
>>>> Andrey.
>>>>
>>>
>>> Thanks Andrey,
>>>
>>> "Consequences" is an understatement.  My heart sank as I started digging
>>> into this and saw things like:
>>>
>>> # Handle default kernel
>>> IMX_DEFAULT_KERNEL = "linux-fslc-imx"
>>> IMX_DEFAULT_KERNEL_mxs = "linux-fslc"
>>> IMX_DEFAULT_KERNEL_mx5 = "linux-fslc"
>>> IMX_DEFAULT_KERNEL_mx6 = "linux-fslc-imx"
>>> IMX_DEFAULT_KERNEL_mx7 = "linux-fslc-imx"
>>> IMX_DEFAULT_KERNEL_mx8 = "linux-fslc-imx"
>>> IMX_DEFAULT_KERNEL_mx7ulp = "linux-fslc-imx"
>>> IMX_DEFAULT_KERNEL_mx6sll = "linux-fslc-imx"
>>> IMX_DEFAULT_KERNEL_mx6ul = "linux-fslc-imx"
>>> IMX_DEFAULT_KERNEL_mx6ull = "linux-fslc-imx"
>>> IMX_DEFAULT_KERNEL_use-mainline-bsp = "linux-fslc"
>>>
>>> ... in sources/meta-freescale/conf/machine/include/imx-base.inc
>>>
>>> I really need at least Linux 5.10 for imx8 for some net-next features I
>>> need.  I was hopeful when I was poking around and saw a 5.10 recipe but now
>>> my hopes are dashed! :(
>>>
>>> Regards,
>>>
>>> Brian
>>>
>>>
>> Update.  So I messed around and changed the things Andrey mentioned and
>> tried another build just for kicks.  If completed with only one kernel
>> error:
>>
>> |   OBJCOPY arch/arm64/boot/Image
>> |   DTC     arch/arm64/boot/dts/freescale/imx8mm-ddr4-evk.dtb
>> | make[2]: *** No rule to make target
>> 'arch/arm64/boot/dts/freescale/imx8mm-ddr4-evk-revb.dtb'.  Stop.
>> | make[1]: ***
>> [/home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/build/tmp/work-shared/imx8mmevk/kernel-source/Makefile:1334:
>> freescale/imx8mm-ddr4-evk-revb.dtb] Error 2
>> | make: ***
>> [/home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/build/tmp/work-shared/imx8mmevk/kernel-source/Makefile:185:
>> __sub-make] Error 2
>> | WARNING: exit code 1 from a shell command.
>> |
>> ERROR: Task
>> (/home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/sources/meta-freescale/recipes-kernel/linux/linux-fslc_5.10.bb:do_compile)
>> failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 4575 tasks of which 1 didn't need to be
>> rerun and 1 failed.
>>
>> Summary: 1 task failed:
>>
>>  /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth/sources/meta-freescale/recipes-kernel/linux/linux-fslc_5.10.bb:do_compile
>>
>> Summary: There were 3 WARNING messages shown.
>> Summary: There were 2 ERROR messages shown, returning a non-zero exit
>> code.
>>
>> ... which is legit as it looks like the freescale .dts files of 5.10 are
>> different than before (no surprise) so I'll try to get past this and see
>> what happens.  I don't need all the NXP EVK stuff (video, touch screen,
>> wifi, bluetooth etc.) which is why I picked Yocto for distro to make a
>> smaller image than all those wayland options ... so just maybe it might
>> work???
>>
>> Will report back soon ...
>>
>> Regards,
>>
>> Brian
>>
>>
> Yet another update.  I further modified my  machine .conf to remove .dtb's
> and features I didn't need and finally got the board booting 5.10.18!  When
> I dd the wic image to sdcard it wouldn't boot so I've got a u-boot issue
> somewhere but I wrote previous version of u-boot with dd and was able to
> get it to boot.
>
> Thank you all for putting up with me once again and keeping me out of the
> weeds.
>
> Now the work begins trying to get some net-next stuff working.
>
> Regards,
>
> Brian
>
>
> 
>
>

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Fabio Estevam]

Hi Brian,

On Wed, Mar 3, 2021 at 12:42 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> Otavio,  tell me again why I'm still getting this:
>
> [    1.853583] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
> [    1.861409] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin

This is normal. The sdma firmware cannot be retrieved at this point
because it stays in the rootfs and the mmc has not been probed yet.

Further in the log you will see:

[    9.479877] imx-sdma 302c0000.dma-controller: loaded firmware 4.5
[    9.479881] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
[    9.486229] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5

which indicated that the sdma firmware was properly loaded.

> It needs to be a loadable module or something?
>
> Anyway ... for the curious ... here's the boot messages:

Glad to see you are able to get it to boot now.

It would be great if someone could help to make this work 'out-of-the-box'.

From what I read here, there were many manual steps involved, such as
changing U-Boot version, etc

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

Hello Fabio,

On Wed, Mar 3, 2021 at 5:31 PM Fabio Estevam <festevam@gmail.com> wrote:
>
> Hi Brian,
>
> On Wed, Mar 3, 2021 at 12:42 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
> >
> > Otavio,  tell me again why I'm still getting this:
> >
> > [    1.853583] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
> > [    1.861409] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
>
> This is normal. The sdma firmware cannot be retrieved at this point
> because it stays in the rootfs and the mmc has not been probed yet.
>
> Further in the log you will see:
>
> [    9.479877] imx-sdma 302c0000.dma-controller: loaded firmware 4.5
> [    9.479881] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
> [    9.486229] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5
>
> which indicated that the sdma firmware was properly loaded.
>
> > It needs to be a loadable module or something?
> >
> > Anyway ... for the curious ... here's the boot messages:
>
> Glad to see you are able to get it to boot now.
>
> It would be great if someone could help to make this work 'out-of-the-box'.
>
> From what I read here, there were many manual steps involved, such as
> changing U-Boot version, etc

I'm working on this solution in my fork, and have it almost ready for
submission.

If anyone would be interested to try it out and test, you can have a
look at https://github.com/zandrey/meta-freescale/tree/boot-container-for-mx8m-fslc

I'll be cleaning it up and getting ready for submission soon(ish).
Currently, the only things that is not supported is OP-TEE - I was not
able to boot the 2020.10 with it, so I removed it for the time being.

What I've tested today with this implementation is:
# DISTRO=poky MACHINE=imx8mm-lpddr4-evk bitbake core-image-base

Had it booted to the shell prompt.

-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Fabio Estevam]

Hi Andrey,

On Wed, Mar 3, 2021 at 1:54 PM Andrey Zhizhikin <andrey.z@gmail.com> wrote:

> I'm working on this solution in my fork, and have it almost ready for
> submission.
>
> If anyone would be interested to try it out and test, you can have a
> look at https://github.com/zandrey/meta-freescale/tree/boot-container-for-mx8m-fslc
>
> I'll be cleaning it up and getting ready for submission soon(ish).
> Currently, the only things that is not supported is OP-TEE - I was not
> able to boot the 2020.10 with it, so I removed it for the time being.
>
> What I've tested today with this implementation is:
> # DISTRO=poky MACHINE=imx8mm-lpddr4-evk bitbake core-image-base
>
> Had it booted to the shell prompt.

That's awesome! Thanks for working on this. Appreciate it.

Cheers

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Wed, Mar 3, 2021 at 11:54 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote:

> Hello Fabio,
>
> On Wed, Mar 3, 2021 at 5:31 PM Fabio Estevam <festevam@gmail.com> wrote:
> >
> > Hi Brian,
> >
> > On Wed, Mar 3, 2021 at 12:42 PM Brian Hutchinson <b.hutchman@gmail.com>
> wrote:
> > >
> > > Otavio,  tell me again why I'm still getting this:
> > >
> > > [    1.853583] imx-sdma 302c0000.dma-controller: Direct firmware load
> for imx/sdma/sdma-imx7d.bin failed with error -2
> > > [    1.861409] imx-sdma 302c0000.dma-controller: Falling back to sysfs
> fallback for: imx/sdma/sdma-imx7d.bin
> >
> > This is normal. The sdma firmware cannot be retrieved at this point
> > because it stays in the rootfs and the mmc has not been probed yet.
> >
> > Further in the log you will see:
> >
> > [    9.479877] imx-sdma 302c0000.dma-controller: loaded firmware 4.5
> > [    9.479881] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
> > [    9.486229] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5
> >
> > which indicated that the sdma firmware was properly loaded.
> >
> > > It needs to be a loadable module or something?
> > >
> > > Anyway ... for the curious ... here's the boot messages:
> >
> > Glad to see you are able to get it to boot now.
> >
> > It would be great if someone could help to make this work
> 'out-of-the-box'.
> >
> > From what I read here, there were many manual steps involved, such as
> > changing U-Boot version, etc
>
> I'm working on this solution in my fork, and have it almost ready for
> submission.
>
> If anyone would be interested to try it out and test, you can have a
> look at
> https://github.com/zandrey/meta-freescale/tree/boot-container-for-mx8m-fslc
>
> I'll be cleaning it up and getting ready for submission soon(ish).
> Currently, the only things that is not supported is OP-TEE - I was not
> able to boot the 2020.10 with it, so I removed it for the time being.
>
> What I've tested today with this implementation is:
> # DISTRO=poky MACHINE=imx8mm-lpddr4-evk bitbake core-image-base
>
> Had it booted to the shell prompt.
>
> --
> Regards,
> Andrey.
>

Since I have the hardware I'll try it out.  I have a stock NXP imx8mm-evk
and a custom board based off the EVK design.

Regards,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

Hello Brian,

On Wed, Mar 3, 2021 at 8:48 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
>
> On Wed, Mar 3, 2021 at 11:54 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
>>
>> Hello Fabio,
>>
>> On Wed, Mar 3, 2021 at 5:31 PM Fabio Estevam <festevam@gmail.com> wrote:
>> >
>> > Hi Brian,
>> >
>> > On Wed, Mar 3, 2021 at 12:42 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> > >
>> > > Otavio,  tell me again why I'm still getting this:
>> > >
>> > > [    1.853583] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
>> > > [    1.861409] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
>> >
>> > This is normal. The sdma firmware cannot be retrieved at this point
>> > because it stays in the rootfs and the mmc has not been probed yet.
>> >
>> > Further in the log you will see:
>> >
>> > [    9.479877] imx-sdma 302c0000.dma-controller: loaded firmware 4.5
>> > [    9.479881] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
>> > [    9.486229] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5
>> >
>> > which indicated that the sdma firmware was properly loaded.
>> >
>> > > It needs to be a loadable module or something?
>> > >
>> > > Anyway ... for the curious ... here's the boot messages:
>> >
>> > Glad to see you are able to get it to boot now.
>> >
>> > It would be great if someone could help to make this work 'out-of-the-box'.
>> >
>> > From what I read here, there were many manual steps involved, such as
>> > changing U-Boot version, etc
>>
>> I'm working on this solution in my fork, and have it almost ready for
>> submission.
>>
>> If anyone would be interested to try it out and test, you can have a
>> look at https://github.com/zandrey/meta-freescale/tree/boot-container-for-mx8m-fslc
>>
>> I'll be cleaning it up and getting ready for submission soon(ish).
>> Currently, the only things that is not supported is OP-TEE - I was not
>> able to boot the 2020.10 with it, so I removed it for the time being.
>>
>> What I've tested today with this implementation is:
>> # DISTRO=poky MACHINE=imx8mm-lpddr4-evk bitbake core-image-base
>>
>> Had it booted to the shell prompt.
>>
>> --
>> Regards,
>> Andrey.
>
>
> Since I have the hardware I'll try it out.  I have a stock NXP imx8mm-evk and a custom board based off the EVK design.

Please do, I would be curious if that works for you and if I missed
something in the implementation.

Bare in mind that this implementation does not have OP-TEE support,
just in case if you rely on it.

For the record, my boot log of imx8mm-lpddr4-evk machine and
core-image-base image:
====

U-Boot SPL 2020.10+fslc+g5003fc093c (Dec 09 2020 - 17:09:55 +0000)
Normal Boot
WDT:   Started with servicing (60s timeout)
Trying to boot from MMC1
NOTICE:  BL31: v2.2(release):rel_imx_5.4.70_2.3.0-0-gf1d7187f2
NOTICE:  BL31: Built : 09:58:42, Dec  1 2020


U-Boot 2020.10+fslc+g5003fc093c (Dec 09 2020 - 17:09:55 +0000)

CPU:   Freescale i.MX8MMQ rev1.0 at 1200 MHz
Reset cause: POR
Model: FSL i.MX8MM EVK board
DRAM:  2 GiB
WDT:   Started with servicing (60s timeout)
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... Run CMD11 1.8V switch
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@30be0000
Hit any key to stop autoboot:  0
Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
Run CMD11 1.8V switch
Failed to load 'boot.scr'
31568384 bytes read in 401 ms (75.1 MiB/s)
Booting from mmc ...
27692 bytes read in 13 ms (2 MiB/s)
Moving Image from 0x40480000 to 0x40600000, end=424b0000
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Device Tree to 000000004fff6000, end 000000004ffffc2b ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.10.18+ge96f454f9d4b (oe-user@oe-host)
(aarch64-poky-linux-gcc (GCC) 10.2.0, GNU ld (GNU Binutils)
2.36.1.20210209) #1 SMP PREEMPT Tue Feb 23 21:32:29 UTC 2021
[    0.000000] Machine model: FSL i.MX8MM EVK board
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Reserved 32 MiB at 0x00000000be000000
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem
0x0000000040000000-0x00000000bfffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xbdbddb00-0xbdbdffff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000040000000-0x000000007fffffff]
[    0.000000]   DMA32    [mem 0x0000000080000000-0x00000000bfffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 23 pages/cpu s56280 r8192 d29736 u94208
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516096
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: console=ttymxc1,115200
root=/dev/mmcblk1p2 rootwait rw
[    0.000000] Dentry cache hash table entries: 262144 (order: 9,
2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8,
1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] software IO TLB: mapped [mem
0x000000007bfff000-0x000000007ffff000] (64MB)
[    0.000000] Memory: 1926564K/2097152K available (14464K kernel
code, 2796K rwdata, 7540K rodata, 5888K init, 518K bss, 137820K
reserved, 32768K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]  Trampoline variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay
is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 128 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] random: get_random_bytes called from
start_kernel+0x330/0x4f4 with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff
max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[    0.000003] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps
every 2199023255500ns
[    0.000733] Console: colour dummy device 80x25
[    0.000812] Calibrating delay loop (skipped), value calculated
using timer frequency.. 16.00 BogoMIPS (lpj=32000)
[    0.000824] pid_max: default: 32768 minimum: 301
[    0.000890] LSM: Security Framework initializing
[    0.000947] Mount-cache hash table entries: 4096 (order: 3, 32768
bytes, linear)
[    0.000959] Mountpoint-cache hash table entries: 4096 (order: 3,
32768 bytes, linear)
[    0.002235] rcu: Hierarchical SRCU implementation.
[    0.003843] EFI services will not be available.
[    0.004066] smp: Bringing up secondary CPUs ...
[    0.004428] Detected VIPT I-cache on CPU1
[    0.004454] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
[    0.004498] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.004900] Detected VIPT I-cache on CPU2
[    0.004917] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
[    0.004941] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.005307] Detected VIPT I-cache on CPU3
[    0.005324] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
[    0.005348] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.005406] smp: Brought up 1 node, 4 CPUs
[    0.005432] SMP: Total of 4 processors activated.
[    0.005438] CPU features: detected: 32-bit EL0 Support
[    0.005444] CPU features: detected: CRC32 instructions
[    0.005452] CPU features: detected: 32-bit EL1 Support
[    0.012471] CPU: All CPU(s) started at EL2
[    0.012494] alternatives: patching kernel code
[    0.013885] devtmpfs: initialized
[    0.017784] KASLR disabled due to lack of seed
[    0.018000] clocksource: jiffies: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.018018] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.019042] pinctrl core: initialized pinctrl subsystem
[    0.020204] DMI not present or invalid.
[    0.020663] NET: Registered protocol family 16
[    0.022121] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
[    0.022169] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for
atomic allocations
[    0.022285] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for
atomic allocations
[    0.022359] audit: initializing netlink subsys (disabled)
[    0.022488] audit: type=2000 audit(0.020:1): state=initialized
audit_enabled=0 res=1
[    0.023421] thermal_sys: Registered thermal governor 'step_wise'
[    0.023425] thermal_sys: Registered thermal governor 'power_allocator'
[    0.023614] cpuidle: using governor menu
[    0.023789] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.023868] ASID allocator initialised with 65536 entries
[    0.025167] Serial: AMBA PL011 UART driver
[    0.045967] debugfs: Directory 'dummy-iomuxc-gpr@30340000' with
parent 'regmap' already present!
[    0.046162] imx8mm-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
[    0.057927] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.057940] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.057946] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.057956] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.058854] cryptd: max_cpu_qlen set to 1000
[    0.061221] ACPI: Interpreter disabled.
[    0.062822] iommu: Default domain type: Translated
[    0.063027] vgaarb: loaded
[    0.063301] SCSI subsystem initialized
[    0.063668] usbcore: registered new interface driver usbfs
[    0.063702] usbcore: registered new interface driver hub
[    0.063730] usbcore: registered new device driver usb
[    0.064810] pps_core: LinuxPPS API ver. 1 registered
[    0.064817] pps_core: Software ver. 5.3.6 - Copyright 2005-2007
Rodolfo Giometti <giometti@linux.it>
[    0.064833] PTP clock support registered
[    0.064948] EDAC MC: Ver: 3.0.0
[    0.066152] FPGA manager framework
[    0.066237] Advanced Linux Sound Architecture Driver Initialized.
[    0.066910] clocksource: Switched to clocksource arch_sys_counter
[    0.067074] VFS: Disk quotas dquot_6.6.0
[    0.067123] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.067287] pnp: PnP ACPI: disabled
[    0.072380] NET: Registered protocol family 2
[    0.072779] tcp_listen_portaddr_hash hash table entries: 1024
(order: 2, 16384 bytes, linear)
[    0.072837] TCP established hash table entries: 16384 (order: 5,
131072 bytes, linear)
[    0.072949] TCP bind hash table entries: 16384 (order: 6, 262144
bytes, linear)
[    0.073188] TCP: Hash tables configured (established 16384 bind 16384)
[    0.073276] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.073320] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.073465] NET: Registered protocol family 1
[    0.073772] RPC: Registered named UNIX socket transport module.
[    0.073779] RPC: Registered udp transport module.
[    0.073785] RPC: Registered tcp transport module.
[    0.073792] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.073805] PCI: CLS 0 bytes, default 64
[    0.074433] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7
counters available
[    0.074863] kvm [1]: IPA Size Limit: 40 bits
[    0.076425] kvm [1]: GICv3: no GICV resource entry
[    0.076432] kvm [1]: disabling GICv2 emulation
[    0.076453] kvm [1]: GIC system register CPU interface enabled
[    0.076518] kvm [1]: vgic interrupt IRQ9
[    0.076628] kvm [1]: Hyp mode initialized successfully
[    0.079508] Initialise system trusted keyrings
[    0.079645] workingset: timestamp_bits=42 max_order=19 bucket_order=0
[    0.085314] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.085909] NFS: Registering the id_resolver key type
[    0.085936] Key type id_resolver registered
[    0.085942] Key type id_legacy registered
[    0.086023] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.086174] 9p: Installing v9fs 9p2000 file system support
[    0.123132] Key type asymmetric registered
[    0.123140] Asymmetric key parser 'x509' registered
[    0.123173] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 245)
[    0.123181] io scheduler mq-deadline registered
[    0.123187] io scheduler kyber registered
[    0.133114] EINJ: ACPI disabled.
[    0.144620] imx-sdma 302c0000.dma-controller: Direct firmware load
for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.144636] imx-sdma 302c0000.dma-controller: Falling back to sysfs
fallback for: imx/sdma/sdma-imx7d.bin
[    0.149893] SoC: i.MX8MM revision 1.0
[    0.153874] debugfs: Directory 'dummy-reset-controller@30390000'
with parent 'regmap' already present!
[    0.157153] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.159476] SuperH (H)SCI(F) driver initialized
[    0.160021] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 34,
base_baud = 1500000) is a IMX
[    1.086567] printk: console [ttymxc1] enabled
[    1.091652] msm_serial: driver initialized
[    1.103074] loop: module loaded
[    1.107138] megasas: 07.714.04.00-rc1
[    1.114339] spi-nor spi0.0: n25q256ax1 (32768 Kbytes)
[    1.125396] libphy: Fixed MDIO Bus: probed
[    1.130645] tun: Universal TUN/TAP device driver, 1.6
[    1.136500] thunder_xcv, ver 1.0
[    1.139786] thunder_bgx, ver 1.0
[    1.143071] nicpf, ver 1.0
[    1.146568] pps pps0: new PPS source ptp0
[    1.152524] libphy: fec_enet_mii_bus: probed
[    1.159221] hclge is initializing
[    1.162564] hns3: Hisilicon Ethernet Network Driver for Hip08
Family - version
[    1.169816] hns3: Copyright (c) 2017 Huawei Corporation.
[    1.175197] e1000: Intel(R) PRO/1000 Network Driver
[    1.180095] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    1.185888] e1000e: Intel(R) PRO/1000 Network Driver
[    1.190860] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.196822] igb: Intel(R) Gigabit Ethernet Network Driver
[    1.202226] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.207827] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[    1.214099] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.220360] sky2: driver version 1.30
[    1.225060] VFIO - User Level meta-driver version: 0.3
[    1.231912] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.238456] ehci-pci: EHCI PCI platform driver
[    1.242941] ehci-platform: EHCI generic platform driver
[    1.248308] ehci-orion: EHCI orion driver
[    1.252423] ehci-exynos: EHCI Exynos driver
[    1.256693] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.262906] ohci-pci: OHCI PCI platform driver
[    1.267388] ohci-platform: OHCI generic platform driver
[    1.272731] ohci-exynos: OHCI Exynos driver
[    1.277437] usbcore: registered new interface driver usb-storage
[    1.286224] i2c /dev entries driver
[    1.296354] sdhci: Secure Digital Host Controller Interface driver
[    1.302603] sdhci: Copyright(c) Pierre Ossman
[    1.307479] Synopsys Designware Multimedia Card Interface Driver
[    1.314465] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.321041] mmc1: CQHCI version 5.10
[    1.321231] mmc2: CQHCI version 5.10
[    1.328497] ledtrig-cpu: registered to indicate activity on CPUs
[    1.335985] usbcore: registered new interface driver usbhid
[    1.341576] usbhid: USB HID core driver
[    1.350835] NET: Registered protocol family 17
[    1.355490] 9pnet: Installing 9P2000 support
[    1.359263] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA
[    1.359829] Key type dns_resolver registered
[    1.371702] registered taskstats version 1
[    1.375812] Loading compiled-in X.509 certificates
[    1.401313] usb_phy_generic usbphynop1: supply vcc not found, using
dummy regulator
[    1.409359] usb_phy_generic usbphynop2: supply vcc not found, using
dummy regulator
[    1.462115] ldo6: supplied by buck5
[    1.465843] i2c i2c-0: IMX I2C adapter registered
[    1.471838] i2c i2c-1: IMX I2C adapter registered
[    1.477541] pca953x 2-0020: supply vcc not found, using dummy regulator
[    1.484274] pca953x 2-0020: using no AI
[    1.490715] i2c i2c-2: IMX I2C adapter registered
[    1.497295] pps pps0: new PPS source ptp0
[    1.503958] libphy: fec_enet_mii_bus: probed
[    1.530581] fec 30be0000.ethernet eth0: registered PHC device 0
[    1.538007] imx_usb 32e40000.usb: No over current polarity defined
[    1.545219] mmc2: Command Queue Engine enabled
[    1.549724] mmc2: new HS400 Enhanced strobe MMC card at address 0001
[    1.553285] mmc1: CQHCI version 5.10
[    1.556868] mmcblk2: mmc2:0001 DG4016 14.7 GiB
[    1.556882] input: bd718xx-pwrkey as
/devices/platform/soc@0/30800000.bus/30a20000.i2c/i2c-0/0-004b/gpio-keys.0.auto/input/input0
[    1.558062] ALSA device list:
[    1.558067]   No soundcards found.
[    1.559783] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[    1.564424] mmcblk2boot0: mmc2:0001 DG4016 partition 1 4.00 MiB
[    1.593421] mmcblk2boot1: mmc2:0001 DG4016 partition 2 4.00 MiB
[    1.593854] mmcblk2rpmb: mmc2:0001 DG4016 partition 3 4.00 MiB,
chardev (234:0)
[    1.608496]  mmcblk2: p1 p2
[    1.609085] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA
[    1.618723] Waiting for root device /dev/mmcblk1p2...
[    1.663268] random: fast init done
[    1.741383] mmc1: host does not support reading read-only switch,
assuming write-enable
[    1.777338] mmc1: new ultra high speed SDR104 SDHC card at address 0001
[    1.785372] mmcblk1: mmc1:0001 SD32G 29.3 GiB
[    1.792696]  mmcblk1: p1 p2
[    1.811506] EXT4-fs (mmcblk1p2): mounted filesystem with ordered
data mode. Opts: (null)
[    1.819688] VFS: Mounted root (ext4 filesystem) on device 179:98.
[    1.827024] devtmpfs: mounted
[    1.831939] Freeing unused kernel memory: 5888K
[    1.836634] Run /sbin/init as init process
INIT: version 2.98 booting
Framebuffer /dev/fb0 not detected
Boot splashscreen disabled
Starting udev
[    2.088043] udevd[166]: starting version 3.2.10
[    2.107906] random: udevd: uninitialized urandom read (16 bytes read)
[    2.115366] random: udevd: uninitialized urandom read (16 bytes read)
[    2.122498] random: udevd: uninitialized urandom read (16 bytes read)
[    2.154826] udevd[167]: starting eudev-3.2.10
[    2.209888] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 3 mkt
segment 0 supported-hw 0x8 0x1
[    2.236830] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
[    2.243173] imx-sdma 302c0000.dma-controller: loaded firmware 4.5
[    2.249473] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5
[    2.258697] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[    2.264963] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system
clock to 1970-01-01T00:00:00 UTC (0)
[    2.274827] input: 30370000.snvs:snvs-powerkey as
/devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input1
[    2.299711] caam 30900000.crypto: Entropy delay = 3200
[    2.308284] caam 30900000.crypto: Entropy delay = 3600
[    2.381510] caam 30900000.crypto: Instantiated RNG4 SH0
[    2.449161] caam 30900000.crypto: Instantiated RNG4 SH1
[    2.454410] caam 30900000.crypto: device ID = 0x0a16040100000000 (Era 9)
[    2.461118] caam 30900000.crypto: job rings = 3, qi = 0
[    2.503875] caam algorithms registered in /proc/crypto
[    2.509829] caam 30900000.crypto: caam pkc algorithms registered in
/proc/crypto
[    2.517265] caam 30900000.crypto: registering rng-caam
[    2.545124] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[    2.725583] random: crng init done
[    2.729187] random: 4 urandom warning(s) missed due to ratelimiting
[    3.067341] Qualcomm Atheros AR8031/AR8033 30be0000.ethernet-1:00:
attached PHY driver [Qualcomm Atheros AR8031/AR8033]
(mii_bus:phy_addr=30be0000.ethernet-1:00, irq=POLL)
[    6.148182] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full -
flow control off
[    9.490972] cfg80211: Loading compiled-in X.509 certificates for
regulatory database
[    9.504547] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.668990] NET: Registered protocol family 10
[    9.674577] Segment Routing with IPv6
[    9.774394] Bluetooth: Core ver 2.22
[    9.778121] NET: Registered protocol family 31
[    9.782621] Bluetooth: HCI device and connection manager initialized
[    9.789035] Bluetooth: HCI socket layer initialized
[    9.789048] Bluetooth: L2CAP socket layer initialized
[    9.799046] Bluetooth: SCO socket layer initialized
[    9.869535] nfc: nfc_init: NFC Core ver 0.1
[    9.873862] NET: Registered protocol family 39

Poky (Yocto Project Reference Distro)
3.2+snapshot-ed7151f9856791fc4a24b1a0a88f87c442b29f38
imx8mm-lpddr4-evk /dev/ttymxc1

imx8mm-lpddr4-evk login:

====

>
> Regards,
>
> Brian



-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Wed, Mar 3, 2021 at 2:48 PM Brian Hutchinson <b.hutchman@gmail.com>
wrote:

>
> Since I have the hardware I'll try it out.  I have a stock NXP imx8mm-evk
> and a custom board based off the EVK design.
>
> Regards,
>
> Brian
>

So maybe I'm not doing this right but I cloned Andrey's git link and tried
to build and didn't get very far.  I'll spell out exactly what I did.

I started off with the normal repo init:
repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b
gatesgarth
repo sync
I moved my meta-freescale directory out of the way (mv meta-freescale
meta_freescale_orig)
cloned Andrey's link he provided: git clone
https://github.com/zandrey/meta-freescale.git -b
boot-container-for-mx8m-fslc
Setup for my board: EULA=1 MACHINE=imx8mm-lpddr4-evk DISTRO=poky source
setup-environment build
Then tried to do a build:
hutch@Gondor:~/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/build$
bitbake core-image-base
NOTE: Your conf/bblayers.conf has been automatically updated.
Loading cache: 100% |



                        |
ETA:  --:--:--
Loaded 0 entries from dependency cache.
Parsing recipes: 100%
|#############################################################################################################################################################################################################################################|
Time: 0:00:13
Parsing of 2289 .bb files complete (0 cached, 2289 parsed). 3495 targets,
258 skipped, 0 masked, 0 errors.
ERROR: No recipes in default available for:
 /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/sources/meta-freescale-3rdparty/recipes-bsp/atf/atf_git.bbappend


 /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/sources/meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-qoriq_2019.10.bbappend



Summary: There was 1 ERROR message shown, returning a non-zero exit code.

I know it was mentioned that OP-TEE isn't there but it appears I'm getting
hung up with atf stuff.

Am I going about building the wrong way?

Regards,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

Hello Brian,

On Thu, Mar 4, 2021 at 3:37 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
>
> On Wed, Mar 3, 2021 at 2:48 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>
>>
>> Since I have the hardware I'll try it out.  I have a stock NXP imx8mm-evk and a custom board based off the EVK design.
>>
>> Regards,
>>
>> Brian
>
>
> So maybe I'm not doing this right but I cloned Andrey's git link and tried to build and didn't get very far.  I'll spell out exactly what I did.
>
> I started off with the normal repo init:
> repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b gatesgarth

You should use the master branch here, as the boot container
implementation I did is on top of master and not gatesgarth.

> repo sync
> I moved my meta-freescale directory out of the way (mv meta-freescale meta_freescale_orig)
> cloned Andrey's link he provided: git clone https://github.com/zandrey/meta-freescale.git -b boot-container-for-mx8m-fslc
> Setup for my board: EULA=1 MACHINE=imx8mm-lpddr4-evk DISTRO=poky source setup-environment build
> Then tried to do a build:
> hutch@Gondor:~/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/build$ bitbake core-image-base
> NOTE: Your conf/bblayers.conf has been automatically updated.
> Loading cache: 100% |                                                                                                                                                                                                                                              | ETA:  --:--:--
> Loaded 0 entries from dependency cache.
> Parsing recipes: 100% |#############################################################################################################################################################################################################################################| Time: 0:00:13
> Parsing of 2289 .bb files complete (0 cached, 2289 parsed). 3495 targets, 258 skipped, 0 masked, 0 errors.
> ERROR: No recipes in default available for:
>  /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/sources/meta-freescale-3rdparty/recipes-bsp/atf/atf_git.bbappend
>  /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/sources/meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-qoriq_2019.10.bbappend
>
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
> I know it was mentioned that OP-TEE isn't there but it appears I'm getting hung up with atf stuff.

OP-TEE would not be available in runtime, you're hitting the build
time issue because of the branch.

>
> Am I going about building the wrong way?

I guess you are. :)

>
> Regards,
>
> Brian
>


-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Thu, Mar 4, 2021 at 9:41 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote:

> Hello Brian,
>
> On Thu, Mar 4, 2021 at 3:37 PM Brian Hutchinson <b.hutchman@gmail.com>
> wrote:
> >
> >
> > On Wed, Mar 3, 2021 at 2:48 PM Brian Hutchinson <b.hutchman@gmail.com>
> wrote:
> >>
> >>
> >> Since I have the hardware I'll try it out.  I have a stock NXP
> imx8mm-evk and a custom board based off the EVK design.
> >>
> >> Regards,
> >>
> >> Brian
> >
> >
> > So maybe I'm not doing this right but I cloned Andrey's git link and
> tried to build and didn't get very far.  I'll spell out exactly what I did.
> >
> > I started off with the normal repo init:
> > repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b
> gatesgarth
>
> You should use the master branch here, as the boot container
> implementation I did is on top of master and not gatesgarth.
>
> > repo sync
> > I moved my meta-freescale directory out of the way (mv meta-freescale
> meta_freescale_orig)
> > cloned Andrey's link he provided: git clone
> https://github.com/zandrey/meta-freescale.git -b
> boot-container-for-mx8m-fslc
> > Setup for my board: EULA=1 MACHINE=imx8mm-lpddr4-evk DISTRO=poky source
> setup-environment build
> > Then tried to do a build:
> > hutch@Gondor:~/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/build$
> bitbake core-image-base
> > NOTE: Your conf/bblayers.conf has been automatically updated.
> > Loading cache: 100% |
>
>
>                                   | ETA:  --:--:--
> > Loaded 0 entries from dependency cache.
> > Parsing recipes: 100%
> |#############################################################################################################################################################################################################################################|
> Time: 0:00:13
> > Parsing of 2289 .bb files complete (0 cached, 2289 parsed). 3495
> targets, 258 skipped, 0 masked, 0 errors.
> > ERROR: No recipes in default available for:
> >
> /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/sources/meta-freescale-3rdparty/recipes-bsp/atf/atf_git.bbappend
> >
> /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/sources/meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-qoriq_2019.10.bbappend
> >
> > Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> >
> > I know it was mentioned that OP-TEE isn't there but it appears I'm
> getting hung up with atf stuff.
>
> OP-TEE would not be available in runtime, you're hitting the build
> time issue because of the branch.
>
> >
> > Am I going about building the wrong way?
>
> I guess you are. :)
>

Ha, ha, doesn't surprise me one bit.

I'll try my steps again but with master.  Last time I tried that none of
the bitbake stuff worked but maybe I wasn't holding my tongue the right way
;)

Regards,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Thu, Mar 4, 2021 at 10:33 AM Brian Hutchinson via lists.yoctoproject.org
<b.hutchman=gmail.com@lists.yoctoproject.org> wrote:

>
>
> On Thu, Mar 4, 2021 at 9:41 AM Andrey Zhizhikin <andrey.z@gmail.com>
> wrote:
>
>> Hello Brian,
>>
>> On Thu, Mar 4, 2021 at 3:37 PM Brian Hutchinson <b.hutchman@gmail.com>
>> wrote:
>> >
>> >
>> > On Wed, Mar 3, 2021 at 2:48 PM Brian Hutchinson <b.hutchman@gmail.com>
>> wrote:
>> >>
>> >>
>> >> Since I have the hardware I'll try it out.  I have a stock NXP
>> imx8mm-evk and a custom board based off the EVK design.
>> >>
>> >> Regards,
>> >>
>> >> Brian
>> >
>> >
>> > So maybe I'm not doing this right but I cloned Andrey's git link and
>> tried to build and didn't get very far.  I'll spell out exactly what I did.
>> >
>> > I started off with the normal repo init:
>> > repo init -u https://github.com/Freescale/fsl-community-bsp-platform
>> -b gatesgarth
>>
>> You should use the master branch here, as the boot container
>> implementation I did is on top of master and not gatesgarth.
>>
>> > repo sync
>> > I moved my meta-freescale directory out of the way (mv meta-freescale
>> meta_freescale_orig)
>> > cloned Andrey's link he provided: git clone
>> https://github.com/zandrey/meta-freescale.git -b
>> boot-container-for-mx8m-fslc
>> > Setup for my board: EULA=1 MACHINE=imx8mm-lpddr4-evk DISTRO=poky source
>> setup-environment build
>> > Then tried to do a build:
>> > hutch@Gondor:~/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/build$
>> bitbake core-image-base
>> > NOTE: Your conf/bblayers.conf has been automatically updated.
>> > Loading cache: 100% |
>>
>>
>>                                     | ETA:  --:--:--
>> > Loaded 0 entries from dependency cache.
>> > Parsing recipes: 100%
>> |#############################################################################################################################################################################################################################################|
>> Time: 0:00:13
>> > Parsing of 2289 .bb files complete (0 cached, 2289 parsed). 3495
>> targets, 258 skipped, 0 masked, 0 errors.
>> > ERROR: No recipes in default available for:
>> >
>> /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/sources/meta-freescale-3rdparty/recipes-bsp/atf/atf_git.bbappend
>> >
>> /home/hutch/yocto/imx8/fsl-community-bsp_gatesgarth_zandrey/sources/meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-qoriq_2019.10.bbappend
>> >
>> > Summary: There was 1 ERROR message shown, returning a non-zero exit
>> code.
>> >
>> > I know it was mentioned that OP-TEE isn't there but it appears I'm
>> getting hung up with atf stuff.
>>
>> OP-TEE would not be available in runtime, you're hitting the build
>> time issue because of the branch.
>>
>> >
>> > Am I going about building the wrong way?
>>
>> I guess you are. :)
>>
>
> Ha, ha, doesn't surprise me one bit.
>
> I'll try my steps again but with master.  Last time I tried that none of
> the bitbake stuff worked but maybe I wasn't holding my tongue the right way
> ;)
>
> Regards,
>
> Brian
>
>
ok, I repeated my steps I listed before using -b master instead of
gatesgarth for the repo init command.  The bitbake of core-image-base was
so ugly I can't even post the output here.  Let's just say it didn't work.

Regards,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

On Thu, Mar 4, 2021 at 7:57 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
[snip]
>
> ok, I repeated my steps I listed before using -b master instead of gatesgarth for the repo init command.  The bitbake of core-image-base was so ugly I can't even post the output here.  Let's just say it didn't work.

Exactly what went wrong would be interesting here! Can you pastebin
the error log somewhere so I can take a look at?

Looks like Peter was able to pull it through - so the build setup should work.

BTW, for the record: I do not use the repo manifest from
fsl-community-bsp-platform repository. I do clone those layers
separately myself and build them.

There is a nice step-by-step tutorial written on how to create a
minimal layer set and build core images from Robert Berger, you can
try to follow those:
https://yoctoproject.blogspot.com/2020/09/how-to-build-core-image-minimal-with.html

>
> Regards,
>
> Brian



-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Thu, Mar 4, 2021 at 2:23 PM Andrey Zhizhikin <andrey.z@gmail.com> wrote:

> On Thu, Mar 4, 2021 at 7:57 PM Brian Hutchinson <b.hutchman@gmail.com>
> wrote:
> >
> [snip]
> >
> > ok, I repeated my steps I listed before using -b master instead of
> gatesgarth for the repo init command.  The bitbake of core-image-base was
> so ugly I can't even post the output here.  Let's just say it didn't work.
>
> Exactly what went wrong would be interesting here! Can you pastebin
> the error log somewhere so I can take a look at?
>
> Looks like Peter was able to pull it through - so the build setup should
> work.
>
> BTW, for the record: I do not use the repo manifest from
> fsl-community-bsp-platform repository. I do clone those layers
> separately myself and build them.
>
> There is a nice step-by-step tutorial written on how to create a
> minimal layer set and build core images from Robert Berger, you can
> try to follow those:
>
> https://yoctoproject.blogspot.com/2020/09/how-to-build-core-image-minimal-with.html
>
>
I repeated the steps I mentioned before just used -b master instead of -b
gatesgarth and it blew up and spewed all over me and I had to go change my
clothes.  Ugliest build I've ever attempted.  Got about a zillion warnings
while bitbase was walking the recipes.  Best you just repeat my steps and
see for yourself.

1) repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b
master
<https://github.com/Freescale/fsl-community-bsp-platform>
2) repo sync
3) I moved my meta-freescale directory out of the way (mv meta-freescale
meta_freescale_orig)
4) cloned Andrey's link he provided: git clone
https://github.com/zandrey/meta-freescale.git -b
boot-container-for-mx8m-fslc
5) Setup for my board: EULA=1 MACHINE=imx8mm-lpddr4-evk DISTRO=poky source
setup-environment build
6) put on whole body prophylactic
7) bitbake core-image-base
8) go decontaminate yourself

Thanks for the tutorial, I don't like repo personally (for one it doesn't
play nice through firewalls) and prefer to set layers up manually .. I like
to know what's going on behind the scenes.

Regards,

Brian

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Thu, Mar 4, 2021 at 2:56 PM Brian Hutchinson via lists.yoctoproject.org
<b.hutchman=gmail.com@lists.yoctoproject.org> wrote:

> On Thu, Mar 4, 2021 at 2:23 PM Andrey Zhizhikin <andrey.z@gmail.com>
> wrote:
>
>> On Thu, Mar 4, 2021 at 7:57 PM Brian Hutchinson <b.hutchman@gmail.com>
>> wrote:
>> >
>> [snip]
>> >
>> > ok, I repeated my steps I listed before using -b master instead of
>> gatesgarth for the repo init command.  The bitbake of core-image-base was
>> so ugly I can't even post the output here.  Let's just say it didn't work.
>>
>> Exactly what went wrong would be interesting here! Can you pastebin
>> the error log somewhere so I can take a look at?
>>
>> Looks like Peter was able to pull it through - so the build setup should
>> work.
>>
>> BTW, for the record: I do not use the repo manifest from
>> fsl-community-bsp-platform repository. I do clone those layers
>> separately myself and build them.
>>
>> There is a nice step-by-step tutorial written on how to create a
>> minimal layer set and build core images from Robert Berger, you can
>> try to follow those:
>>
>> https://yoctoproject.blogspot.com/2020/09/how-to-build-core-image-minimal-with.html
>>
>>
> I repeated the steps I mentioned before just used -b master instead of -b
> gatesgarth and it blew up and spewed all over me and I had to go change my
> clothes.  Ugliest build I've ever attempted.  Got about a zillion warnings
> while bitbase was walking the recipes.  Best you just repeat my steps and
> see for yourself.
>
> 1) repo init -u https://github.com/Freescale/fsl-community-bsp-platform
> -b master
> <https://github.com/Freescale/fsl-community-bsp-platform>
> 2) repo sync
> 3) I moved my meta-freescale directory out of the way (mv meta-freescale
> meta_freescale_orig)
> 4) cloned Andrey's link he provided: git clone
> https://github.com/zandrey/meta-freescale.git -b
> boot-container-for-mx8m-fslc
> 5) Setup for my board: EULA=1 MACHINE=imx8mm-lpddr4-evk DISTRO=poky source
> setup-environment build
> 6) put on whole body prophylactic
> 7) bitbake core-image-base
> 8) go decontaminate yourself
>
> Thanks for the tutorial, I don't like repo personally (for one it doesn't
> play nice through firewalls) and prefer to set layers up manually .. I like
> to know what's going on behind the scenes.
>
> Regards,
>
> Brian
>
>
Ok, now that I've backed away from the ledge I smoked my shell and did a
clean shell and repeated the bitbake and it's working well now.  I suspect
that I switched from trying gatesgarth build to master build in same shell
and didn't follow my rule of always starting a bitbake in clean shell so
the blowup I saw was most likely due to funkiness in the environment so I
apologize for the high SNR.

The build is running now so I'll monitor it.  I'll report back after my 24
huskies are finished mushing out the image in about an hour.

B

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

On Thu, Mar 4, 2021 at 9:36 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
>
> On Thu, Mar 4, 2021 at 2:56 PM Brian Hutchinson via lists.yoctoproject.org <b.hutchman=gmail.com@lists.yoctoproject.org> wrote:
>>
>> On Thu, Mar 4, 2021 at 2:23 PM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
>>>
>>> On Thu, Mar 4, 2021 at 7:57 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>> >
>>> [snip]
>>> >
>>> > ok, I repeated my steps I listed before using -b master instead of gatesgarth for the repo init command.  The bitbake of core-image-base was so ugly I can't even post the output here.  Let's just say it didn't work.
>>>
>>> Exactly what went wrong would be interesting here! Can you pastebin
>>> the error log somewhere so I can take a look at?
>>>
>>> Looks like Peter was able to pull it through - so the build setup should work.
>>>
>>> BTW, for the record: I do not use the repo manifest from
>>> fsl-community-bsp-platform repository. I do clone those layers
>>> separately myself and build them.
>>>
>>> There is a nice step-by-step tutorial written on how to create a
>>> minimal layer set and build core images from Robert Berger, you can
>>> try to follow those:
>>> https://yoctoproject.blogspot.com/2020/09/how-to-build-core-image-minimal-with.html
>>>
>>
>> I repeated the steps I mentioned before just used -b master instead of -b gatesgarth and it blew up and spewed all over me and I had to go change my clothes.  Ugliest build I've ever attempted.  Got about a zillion warnings while bitbase was walking the recipes.  Best you just repeat my steps and see for yourself.
>>
>> 1) repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b master
>> 2) repo sync
>> 3) I moved my meta-freescale directory out of the way (mv meta-freescale meta_freescale_orig)
>> 4) cloned Andrey's link he provided: git clone https://github.com/zandrey/meta-freescale.git -b boot-container-for-mx8m-fslc
>> 5) Setup for my board: EULA=1 MACHINE=imx8mm-lpddr4-evk DISTRO=poky source setup-environment build
>> 6) put on whole body prophylactic
>> 7) bitbake core-image-base
>> 8) go decontaminate yourself
>>
>> Thanks for the tutorial, I don't like repo personally (for one it doesn't play nice through firewalls) and prefer to set layers up manually .. I like to know what's going on behind the scenes.
>>
>> Regards,
>>
>> Brian
>>
>
> Ok, now that I've backed away from the ledge I smoked my shell and did a clean shell and repeated the bitbake and it's working well now.  I suspect that I switched from trying gatesgarth build to master build in same shell and didn't follow my rule of always starting a bitbake in clean shell so the blowup I saw was most likely due to funkiness in the environment so I apologize for the high SNR.

I've tried the manifest build setup from fsl-community-bsp-base, and
indeed it failed during the parsing stage with a ton of errors I
haven't seen before in my builds. I've opened the issue in the
manifest repository for this:
https://github.com/Freescale/fsl-community-bsp-base/issues/17

I guess if you would rather follow a tutorial I sent before - you
should get your build through with flying colors. ;)

>
> The build is running now so I'll monitor it.  I'll report back after my 24 huskies are finished mushing out the image in about an hour.

No worries, keep us posted. An don't loose hope! :)

>
> B
>

-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Peter Bergin]

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

Hi,

On 2021-03-04 21:49, Andrey Zhizhikin wrote:
>> The build is running now so I'll monitor it.  I'll report back after my 24 huskies are finished mushing out the image in about an hour.
> No worries, keep us posted. An don't loose hope!:)
>
there is some strange issues with the build setup using repo manifest 
and I suspect the setup-environment script. When I built for Nano 
earlier today I did not use repo nor setup-environment. But I easily 
reproduced (I guess) the same issue as Brian sees only by using repo 
with master branch and setup-environment script. I also saw the strange 
thing that Brian noticed that after a horrible output from bitbake the 
second build in the same build dir succeeded. This is not related to 
boot-container so I will open a new fresh thread around this issue.

Best regards,
/Peter



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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

Hello Peter,

On Thu, Mar 4, 2021 at 10:56 PM Peter Bergin <peter@berginkonsult.se> wrote:
>
> Hi,
>
> On 2021-03-04 21:49, Andrey Zhizhikin wrote:
>
> The build is running now so I'll monitor it.  I'll report back after my 24 huskies are finished mushing out the image in about an hour.
>
> No worries, keep us posted. An don't loose hope! :)
>
> there is some strange issues with the build setup using repo manifest and I suspect the setup-environment script. When I built for Nano earlier today I did not use repo nor setup-environment. But I easily reproduced (I guess) the same issue as Brian sees only by using repo with master branch and setup-environment script. I also saw the strange thing that Brian noticed that after a horrible output from bitbake the second build in the same build dir succeeded. This is not related to boot-container so I will open a new fresh thread around this issue.

Thanks for clarification, and again for testing the boot container!

I've already opened the issue on GitHub for this:
https://github.com/Freescale/fsl-community-bsp-base/issues/17

If you have any additional information - you can add it there as well.

>
> Best regards,
> /Peter
>
>


-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Brian Hutchinson]

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

On Thu, Mar 4, 2021 at 4:56 PM Peter Bergin <peter@berginkonsult.se> wrote:

> Hi,
> On 2021-03-04 21:49, Andrey Zhizhikin wrote:
>
> The build is running now so I'll monitor it.  I'll report back after my 24 huskies are finished mushing out the image in about an hour.
>
> No worries, keep us posted. An don't loose hope! :)
>
> there is some strange issues with the build setup using repo manifest and
> I suspect the setup-environment script. When I built for Nano earlier today
> I did not use repo nor setup-environment. But I easily reproduced (I guess)
> the same issue as Brian sees only by using repo with master branch and
> setup-environment script. I also saw the strange thing that Brian noticed
> that after a horrible output from bitbake the second build in the same
> build dir succeeded. This is not related to boot-container so I will open a
> new fresh thread around this issue.
>
> Best regards,
> /Peter
>
> Whew, you mean I'm not losing my mind? Cool.  I thought I might need an
intervention (well probably still do).

B

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

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Peter Bergin]

Hi Andrey,

On 2021-03-03 17:54, Andrey Zhizhikin wrote:
> I'm working on this solution in my fork, and have it almost ready for
> submission.
>
> If anyone would be interested to try it out and test, you can have a
> look athttps://github.com/zandrey/meta-freescale/tree/boot-container-for-mx8m-fslc
>
> I'll be cleaning it up and getting ready for submission soon(ish).
> Currently, the only things that is not supported is OP-TEE - I was not
> able to boot the 2020.10 with it, so I removed it for the time being.
>
> What I've tested today with this implementation is:
> # DISTRO=poky MACHINE=imx8mm-lpddr4-evk bitbake core-image-base
>
> Had it booted to the shell prompt.

thanks for the good work! I've tried to boot this on a imx8mn-ddr4-evk 
and see some issues with u-boot environment. I had to tweak the 
environment in order to get this to boot from SD card.

Variable - default -> changed to:
     mmcdev - 0 -> 1
     image - Image.itb -> Image
     boot_fit - try -> false

Seems like CONFIG_SYS_MMC_ENV_DEV is missing in the defconfig for 
imx8mn_ddr4_evk (it is present for imx8mm_evk and imx8mp_evk). I can 
also see a difference for 'image' and 'boot_fit' variable, 
include/configs/imx8mn_evk.h differs from 
include/configs/imx8m{m,p}_evk.h. So in order to get Nano EVK fully 
working the u-boot environment needs an update.

After handling the issue above the Nano EVK boots fine. I put the output 
from the console below for the interested.

Best regards,
/Peter


U-Boot SPL 2020.10+fslc+g5003fc093c (Dec 09 2020 - 17:09:55 +0000)
Normal Boot
WDT:   Started with servicing (60s timeout)
Trying to boot from BOOTROM
image offset 0x8000, pagesize 0x200, ivt offset 0x0
NOTICE:  BL31: v2.2(release):rel_imx_5.4.70_2.3.0-0-gf1d7187f2
NOTICE:  BL31: Built : 09:58:42, Dec  1 2020


U-Boot 2020.10+fslc+g5003fc093c (Dec 09 2020 - 17:09:55 +0000)

CPU:   Freescale i.MX8MNano Quad rev1.0 at 1200 MHz
Reset cause: POR
Model: NXP i.MX8MNano DDR4 EVK board
DRAM:  2 GiB
WDT:   Started with servicing (60s timeout)
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... Run CMD11 1.8V switch
OK
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
Run CMD11 1.8V switch
Failed to load 'boot.scr'
31568384 bytes read in 391 ms (77 MiB/s)
Booting from mmc ...
23443 bytes read in 12 ms (1.9 MiB/s)
Moving Image from 0x40480000 to 0x40600000, end=424b0000
## Flattened Device Tree blob at 43000000
    Booting using the fdt blob at 0x43000000
    Loading Device Tree to 000000004fff7000, end 000000004ffffb92 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.10.18+ge96f454f9d4b (oe-user@oe-host) 
(aarch64-poky-linux-gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 
2.36.1.20210209) #1 SMP PR
EEMPT Tue Feb 23 21:32:29 UTC 2021
[    0.000000] Machine model: NXP i.MX8MNano DDR4 EVK board
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Reserved 32 MiB at 0x00000000be000000
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 
0x0000000040000000-0x00000000bfffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xbdbe1b00-0xbdbe3fff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000040000000-0x000000007fffffff]
[    0.000000]   DMA32    [mem 0x0000000080000000-0x00000000bfffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] Initmem setup node 0 [mem 
0x0000000040000000-0x00000000bfffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 23 pages/cpu s56280 r8192 d29736 u94208
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516096
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: console=ttymxc1,115200 
root=/dev/mmcblk1p2 rootwait rw
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 
2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 
bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] software IO TLB: mapped [mem 
0x000000007bfff000-0x000000007ffff000] (64MB)
[    0.000000] Memory: 1926588K/2097152K available (14464K kernel code, 
2796K rwdata, 7540K rodata, 5888K init, 518K bss, 137796K reserved, 
32768K cma-rese
rved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to 
nr_cpu_ids=4.
[    0.000000]  Trampoline variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay 
is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 128 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: CPU0: found redistributor 0 region 
0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] random: get_random_bytes called from 
start_kernel+0x330/0x4f4 with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff 
max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[    0.000003] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps 
every 2199023255500ns
[    0.000614] Console: colour dummy device 80x25
[    0.000688] Calibrating delay loop (skipped), value calculated using 
timer frequency.. 16.00 BogoMIPS (lpj=32000)
[    0.000700] pid_max: default: 32768 minimum: 301
[    0.000768] LSM: Security Framework initializing
[    0.000825] Mount-cache hash table entries: 4096 (order: 3, 32768 
bytes, linear)
[    0.000843] Mountpoint-cache hash table entries: 4096 (order: 3, 
32768 bytes, linear)
[    0.002083] rcu: Hierarchical SRCU implementation.
[    0.003483] EFI services will not be available.
[    0.003663] smp: Bringing up secondary CPUs ...
[    0.004046] Detected VIPT I-cache on CPU1
[    0.004074] GICv3: CPU1: found redistributor 1 region 
0:0x00000000388a0000
[    0.004113] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.004516] Detected VIPT I-cache on CPU2
[    0.004533] GICv3: CPU2: found redistributor 2 region 
0:0x00000000388c0000
[    0.004558] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.004934] Detected VIPT I-cache on CPU3
[    0.004949] GICv3: CPU3: found redistributor 3 region 
0:0x00000000388e0000
[    0.004972] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.005027] smp: Brought up 1 node, 4 CPUs
[    0.005051] SMP: Total of 4 processors activated.
[    0.005058] CPU features: detected: 32-bit EL0 Support
[    0.005066] CPU features: detected: CRC32 instructions
[    0.005073] CPU features: detected: 32-bit EL1 Support
[    0.012237] CPU: All CPU(s) started at EL2
[    0.012259] alternatives: patching kernel code
[    0.013607] devtmpfs: initialized
[    0.017018] KASLR disabled due to lack of seed
[    0.017241] clocksource: jiffies: mask: 0xffffffff max_cycles: 
0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.017256] futex hash table entries: 1024 (order: 4, 65536 bytes, 
linear)
[    0.018296] pinctrl core: initialized pinctrl subsystem
[    0.019308] DMI not present or invalid.
[    0.019748] NET: Registered protocol family 16
[    0.021180] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic 
allocations
[    0.021231] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for 
atomic allocations
[    0.021347] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for 
atomic allocations
[    0.021419] audit: initializing netlink subsys (disabled)
[    0.021555] audit: type=2000 audit(0.020:1): state=initialized 
audit_enabled=0 res=1
[    0.022425] thermal_sys: Registered thermal governor 'step_wise'
[    0.022429] thermal_sys: Registered thermal governor 'power_allocator'
[    0.022601] cpuidle: using governor menu
[    0.022771] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.022849] ASID allocator initialised with 65536 entries
[    0.024052] Serial: AMBA PL011 UART driver
[    0.041518] debugfs: Directory 'dummy-iomuxc-gpr@30340000' with 
parent 'regmap' already present!
[    0.041703] imx8mn-pinctrl 30330000.pinctrl: initialized IMX pinctrl 
driver
[    0.052834] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.052847] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.052854] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.052861] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.053748] cryptd: max_cpu_qlen set to 1000
[    0.055961] ACPI: Interpreter disabled.
[    0.057435] iommu: Default domain type: Translated
[    0.057624] vgaarb: loaded
[    0.057897] SCSI subsystem initialized
[    0.058185] usbcore: registered new interface driver usbfs
[    0.058221] usbcore: registered new interface driver hub
[    0.058248] usbcore: registered new device driver usb
[    0.059177] pps_core: LinuxPPS API ver. 1 registered
[    0.059185] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 
Rodolfo Giometti <giometti@linux.it>
[    0.059201] PTP clock support registered
[    0.059306] EDAC MC: Ver: 3.0.0
[    0.060391] FPGA manager framework
[    0.060465] Advanced Linux Sound Architecture Driver Initialized.
[    0.061121] clocksource: Switched to clocksource arch_sys_counter
[    0.061268] VFS: Disk quotas dquot_6.6.0
[    0.061313] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 
bytes)
[    0.061487] pnp: PnP ACPI: disabled
[    0.066451] NET: Registered protocol family 2
[    0.066829] tcp_listen_portaddr_hash hash table entries: 1024 (order: 
2, 16384 bytes, linear)
[    0.066866] TCP established hash table entries: 16384 (order: 5, 
131072 bytes, linear)
[    0.067009] TCP bind hash table entries: 16384 (order: 6, 262144 
bytes, linear)
[    0.067243] TCP: Hash tables configured (established 16384 bind 16384)
[    0.067354] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.067397] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, 
linear)
[    0.067541] NET: Registered protocol family 1
[    0.067871] RPC: Registered named UNIX socket transport module.
[    0.067878] RPC: Registered udp transport module.
[    0.067883] RPC: Registered tcp transport module.
[    0.067889] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.067899] PCI: CLS 0 bytes, default 64
[    0.068602] kvm [1]: IPA Size Limit: 40 bits
[    0.069885] kvm [1]: GICv3: no GICV resource entry
[    0.069892] kvm [1]: disabling GICv2 emulation
[    0.069909] kvm [1]: GIC system register CPU interface enabled
[    0.069987] kvm [1]: vgic interrupt IRQ9
[    0.070085] kvm [1]: Hyp mode initialized successfully
[    0.072787] Initialise system trusted keyrings
[    0.072907] workingset: timestamp_bits=42 max_order=19 bucket_order=0
[    0.078327] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.078890] NFS: Registering the id_resolver key type
[    0.078913] Key type id_resolver registered
[    0.078920] Key type id_legacy registered
[    0.078993] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.079130] 9p: Installing v9fs 9p2000 file system support
[    0.115078] Key type asymmetric registered
[    0.115086] Asymmetric key parser 'x509' registered
[    0.115122] Block layer SCSI generic (bsg) driver version 0.4 loaded 
(major 245)
[    0.115129] io scheduler mq-deadline registered
[    0.115135] io scheduler kyber registered
[    0.123922] EINJ: ACPI disabled.
[    0.132282] imx-sdma 302b0000.dma-controller: Direct firmware load 
for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.132297] imx-sdma 302b0000.dma-controller: Falling back to sysfs 
fallback for: imx/sdma/sdma-imx7d.bin
[    0.137249] SoC: i.MX8MN revision 1.0
[    0.140766] debugfs: Directory 'dummy-reset-controller@30390000' with 
parent 'regmap' already present!
[    0.143941] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.146096] SuperH (H)SCI(F) driver initialized
[    0.146596] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 32, 
base_baud = 1500000) is a IMX
[    1.065937] printk: console [ttymxc1] enabled
[    1.070947] msm_serial: driver initialized
[    1.082458] loop: module loaded
[    1.086414] megasas: 07.714.04.00-rc1
[    1.093989] libphy: Fixed MDIO Bus: probed
[    1.099118] tun: Universal TUN/TAP device driver, 1.6
[    1.104849] thunder_xcv, ver 1.0
[    1.108118] thunder_bgx, ver 1.0
[    1.111377] nicpf, ver 1.0
[    1.114880] pps pps0: new PPS source ptp0
[    1.119629] fec 30be0000.ethernet: Invalid MAC address: 00:00:00:00:00:00
[    1.126434] fec 30be0000.ethernet: Using random MAC address: 
fa:f1:4e:05:80:92
[    1.134775] libphy: fec_enet_mii_bus: probed
[    1.139128] mdio_bus 30be0000.ethernet-1: MDIO device at address 0 is 
missing.
[    1.146824] fec 30be0000.ethernet eth0: registered PHC device 0
[    1.153944] hclge is initializing
[    1.157313] hns3: Hisilicon Ethernet Network Driver for Hip08 Family 
- version
[    1.164542] hns3: Copyright (c) 2017 Huawei Corporation.
[    1.169906] e1000: Intel(R) PRO/1000 Network Driver
[    1.174791] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    1.180579] e1000e: Intel(R) PRO/1000 Network Driver
[    1.185550] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.191506] igb: Intel(R) Gigabit Ethernet Network Driver
[    1.196911] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.202521] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[    1.208794] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.214997] sky2: driver version 1.30
[    1.219597] VFIO - User Level meta-driver version: 0.3
[    1.226302] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.232842] ehci-pci: EHCI PCI platform driver
[    1.237320] ehci-platform: EHCI generic platform driver
[    1.242652] ehci-orion: EHCI orion driver
[    1.246747] ehci-exynos: EHCI Exynos driver
[    1.251003] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.257208] ohci-pci: OHCI PCI platform driver
[    1.261683] ohci-platform: OHCI generic platform driver
[    1.267007] ohci-exynos: OHCI Exynos driver
[    1.271640] usbcore: registered new interface driver usb-storage
[    1.280062] i2c /dev entries driver
[    1.289493] sdhci: Secure Digital Host Controller Interface driver
[    1.295727] sdhci: Copyright(c) Pierre Ossman
[    1.300528] Synopsys Designware Multimedia Card Interface Driver
[    1.307386] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.314751] ledtrig-cpu: registered to indicate activity on CPUs
[    1.322067] usbcore: registered new interface driver usbhid
[    1.327664] usbhid: USB HID core driver
[    1.336365] NET: Registered protocol family 17
[    1.340996] 9pnet: Installing 9P2000 support
[    1.345334] Key type dns_resolver registered
[    1.345734] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] 
using ADMA
[    1.350057] registered taskstats version 1
[    1.360770] Loading compiled-in X.509 certificates
[    1.384857] usb_phy_generic usbphynop1: supply vcc not found, using 
dummy regulator
[    1.461779] mmc2: new HS400 MMC card at address 0001
[    1.466108] ldo6: supplied by buck5
[    1.468200] mmcblk2: mmc2:0001 DG4016 14.7 GiB
[    1.470476] i2c i2c-0: IMX I2C adapter registered
[    1.474998] mmcblk2boot0: mmc2:0001 DG4016 partition 1 4.00 MiB
[    1.481024] i2c i2c-1: IMX I2C adapter registered
[    1.485654] mmcblk2boot1: mmc2:0001 DG4016 partition 2 4.00 MiB
[    1.491453] pca953x 2-0020: supply vcc not found, using dummy regulator
[    1.496785] mmcblk2rpmb: mmc2:0001 DG4016 partition 3 4.00 MiB, 
chardev (234:0)
[    1.502791] pca953x 2-0020: using no AI
[    1.514527]  mmcblk2: p1 p2 p3 p4 p5
[    1.515306] i2c i2c-2: IMX I2C adapter registered
[    1.524296] imx_usb 32e40000.usb: No over current polarity defined
[    1.538182] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[    1.540843] input: bd718xx-pwrkey as 
/devices/platform/soc@0/30800000.bus/30a20000.i2c/i2c-0/0-004b/gpio-keys.0.auto/input/input0
[    1.556001] ALSA device list:
[    1.558994]   No soundcards found.
[    1.574209] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] 
using ADMA
[    1.581908] Waiting for root device /dev/mmcblk1p2...
[    1.676516] random: fast init done
[    1.723156] mmc1: host does not support reading read-only switch, 
assuming write-enable
[    1.758762] mmc1: new ultra high speed SDR104 SDHC card at address e624
[    1.766795] mmcblk1: mmc1:e624 SU08G 7.40 GiB
[    1.782688]  mmcblk1: p1 p2
[    1.816060] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data 
mode. Opts: (null)
[    1.824241] VFS: Mounted root (ext4 filesystem) on device 179:98.
[    1.836254] devtmpfs: mounted
[    1.842210] Freeing unused kernel memory: 5888K
[    1.846868] Run /sbin/init as init process
INIT: version 2.99 booting
Framebuffer /dev/fb0 not detected
Boot splashscreen disabled
Starting udev
[    2.083507] udevd[163]: starting version 3.2.10
[    2.099256] random: udevd: uninitialized urandom read (16 bytes read)
[    2.106263] random: udevd: uninitialized urandom read (16 bytes read)
[    2.113239] random: udevd: uninitialized urandom read (16 bytes read)
[    2.138124] udevd[164]: starting eudev-3.2.10
[    2.188777] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 8 mkt 
segment 0 supported-hw 0x100 0x1
[    2.204639] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
[    2.210970] imx-sdma 302c0000.dma-controller: loaded firmware 4.5
[    2.217304] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5
[    2.253252] input: 30370000.snvs:snvs-powerkey as 
/devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input1
[    2.254641] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[    2.274836] bd718xx-clk bd71847-clk.1.auto: No parent clk found
[    2.275097] caam 30900000.crypto: Entropy delay = 3200
[    2.281771] bd718xx-clk: probe of bd71847-clk.1.auto failed with 
error -22
[    2.292932] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock 
to 2018-03-09T13:03:11 UTC (1520600591)
[    2.300969] caam 30900000.crypto: Instantiated RNG4 SH0
[    2.311650] caam 30900000.crypto: Instantiated RNG4 SH1
[    2.318359] caam 30900000.crypto: device ID = 0x0a16040100000100 (Era 9)
[    2.326094] caam 30900000.crypto: job rings = 3, qi = 0
[    2.421546] caam algorithms registered in /proc/crypto
[    2.428007] caam 30900000.crypto: caam pkc algorithms registered in 
/proc/crypto
[    2.435437] caam 30900000.crypto: registering rng-caam
[    2.459802] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[    2.477805] random: crng init done
[    2.481340] random: 4 urandom warning(s) missed due to ratelimiting
[    2.741415] fec 30be0000.ethernet eth0: Unable to connect to phy
[    2.852625] NET: Registered protocol family 10
[    2.858442] Segment Routing with IPv6
[    2.941803] Bluetooth: Core ver 2.22
[    2.945546] NET: Registered protocol family 31
[    2.950043] Bluetooth: HCI device and connection manager initialized
[    2.956448] Bluetooth: HCI socket layer initialized
[    2.961373] Bluetooth: L2CAP socket layer initialized
[    2.966518] Bluetooth: SCO socket layer initialized
[    3.033397] nfc: nfc_init: NFC Core ver 0.1
[    3.037722] NET: Registered protocol family 39

Poky (Yocto Project Reference Distro) 
3.2+snapshot-c8075ed8f157468849d3199c3671b84a6f08785d imx8mn-ddr4-evk 
/dev/ttymxc1

imx8mn-ddr4-evk login:

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Fabio Estevam]

Hi Peter,

On Thu, Mar 4, 2021 at 7:48 AM Peter Bergin <peter@berginkonsult.se> wrote:

> thanks for the good work! I've tried to boot this on a imx8mn-ddr4-evk
> and see some issues with u-boot environment. I had to tweak the
> environment in order to get this to boot from SD card.
>
> Variable - default -> changed to:
>      mmcdev - 0 -> 1
>      image - Image.itb -> Image
>      boot_fit - try -> false

Thanks for testing.

I have addressed the issues you reported:
https://lists.denx.de/pipermail/u-boot/2021-March/443133.html

Cheers

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

Hello Fabio,

On Thu, Mar 4, 2021 at 12:09 PM Fabio Estevam <festevam@gmail.com> wrote:
>
> Hi Peter,
>
> On Thu, Mar 4, 2021 at 7:48 AM Peter Bergin <peter@berginkonsult.se> wrote:
>
> > thanks for the good work! I've tried to boot this on a imx8mn-ddr4-evk
> > and see some issues with u-boot environment. I had to tweak the
> > environment in order to get this to boot from SD card.
> >
> > Variable - default -> changed to:
> >      mmcdev - 0 -> 1
> >      image - Image.itb -> Image
> >      boot_fit - try -> false
>
> Thanks for testing.
>
> I have addressed the issues you reported:
> https://lists.denx.de/pipermail/u-boot/2021-March/443133.html

Thanks for the patch, I'll give it a try and submit PR against
u-boot-fslc once I test it.

>
> Cheers


PS: Apologies for mistyping your name in my previous reply! :)

-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

Hello Fabio,

On Thu, Mar 4, 2021 at 12:19 PM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
>
> Hello Fabio,
>
> On Thu, Mar 4, 2021 at 12:09 PM Fabio Estevam <festevam@gmail.com> wrote:
> >
> > Hi Peter,
> >
> > On Thu, Mar 4, 2021 at 7:48 AM Peter Bergin <peter@berginkonsult.se> wrote:
> >
> > > thanks for the good work! I've tried to boot this on a imx8mn-ddr4-evk
> > > and see some issues with u-boot environment. I had to tweak the
> > > environment in order to get this to boot from SD card.
> > >
> > > Variable - default -> changed to:
> > >      mmcdev - 0 -> 1
> > >      image - Image.itb -> Image
> > >      boot_fit - try -> false
> >
> > Thanks for testing.
> >
> > I have addressed the issues you reported:
> > https://lists.denx.de/pipermail/u-boot/2021-March/443133.html
>
> Thanks for the patch, I'll give it a try and submit PR against
> u-boot-fslc once I test it.

I've applied the patch locally to my build, and imx8mn-ddr4-evk boots
without errors or additional interactions to the command prompt. See
the boot log at the end of the mail.

I can submit it as a PR against u-boot-fslc repository, or you prefer
to do it yourself?

I guess there is no need to wait for it applied upstream, since it is
quite a straightforward fix that is needed.

>
> >
> > Cheers
>
>
> PS: Apologies for mistyping your name in my previous reply! :)
>
> --
> Regards,
> Andrey.


====
U-Boot SPL 2020.10+fslc+g5003fc093c (Dec 09 2020 - 17:09:55 +0000)
Normal Boot
WDT:   Started with servicing (60s timeout)
Trying to boot from BOOTROM
image offset 0x8000, pagesize 0x200, ivt offset 0x0
NOTICE:  BL31: v2.2(release):rel_imx_5.4.70_2.3.0-0-gf1d7187f2
NOTICE:  BL31: Built : 09:58:42, Dec  1 2020


U-Boot 2020.10+fslc+g5003fc093c (Dec 09 2020 - 17:09:55 +0000)

CPU:   Freescale i.MX8MNano Quad rev1.0 at 1200 MHz
Reset cause: POR
Model: NXP i.MX8MNano DDR4 EVK board
DRAM:  2 GiB
WDT:   Started with servicing (60s timeout)
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... Run CMD11 1.8V switch
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
Run CMD11 1.8V switch
Failed to load 'boot.scr'
31568384 bytes read in 384 ms (78.4 MiB/s)
Booting from mmc ...
23443 bytes read in 13 ms (1.7 MiB/s)
Moving Image from 0x40480000 to 0x40600000, end=424b0000
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Device Tree to 000000004fff7000, end 000000004ffffb92 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.10.18+ge96f454f9d4b (oe-user@oe-host)
(aarch64-poky-linux-gcc (GCC) 10.2.0, GNU ld (GNU Binutils)
2.36.1.20210209) #1 SMP PREEMPT Tue Feb 23 21:32:29 UTC 2021
[    0.000000] Machine model: NXP i.MX8MNano DDR4 EVK board
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Reserved 32 MiB at 0x00000000be000000
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem
0x0000000040000000-0x00000000bfffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xbdbe1b00-0xbdbe3fff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000040000000-0x000000007fffffff]
[    0.000000]   DMA32    [mem 0x0000000080000000-0x00000000bfffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 23 pages/cpu s56280 r8192 d29736 u94208
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516096
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: console=ttymxc1,115200
root=/dev/mmcblk1p2 rootwait rw
[    0.000000] Dentry cache hash table entries: 262144 (order: 9,
2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8,
1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] software IO TLB: mapped [mem
0x000000007bfff000-0x000000007ffff000] (64MB)
[    0.000000] Memory: 1926588K/2097152K available (14464K kernel
code, 2796K rwdata, 7540K rodata, 5888K init, 518K bss, 137796K
reserved, 32768K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]  Trampoline variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay
is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 128 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] random: get_random_bytes called from
start_kernel+0x330/0x4f4 with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff
max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[    0.000004] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps
every 2199023255500ns
[    0.000612] Console: colour dummy device 80x25
[    0.000685] Calibrating delay loop (skipped), value calculated
using timer frequency.. 16.00 BogoMIPS (lpj=32000)
[    0.000698] pid_max: default: 32768 minimum: 301
[    0.000765] LSM: Security Framework initializing
[    0.000824] Mount-cache hash table entries: 4096 (order: 3, 32768
bytes, linear)
[    0.000842] Mountpoint-cache hash table entries: 4096 (order: 3,
32768 bytes, linear)
[    0.002088] rcu: Hierarchical SRCU implementation.
[    0.003490] EFI services will not be available.
[    0.003663] smp: Bringing up secondary CPUs ...
[    0.004049] Detected VIPT I-cache on CPU1
[    0.004077] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
[    0.004118] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.004523] Detected VIPT I-cache on CPU2
[    0.004541] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
[    0.004564] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.004934] Detected VIPT I-cache on CPU3
[    0.004950] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
[    0.004973] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.005029] smp: Brought up 1 node, 4 CPUs
[    0.005052] SMP: Total of 4 processors activated.
[    0.005059] CPU features: detected: 32-bit EL0 Support
[    0.005066] CPU features: detected: CRC32 instructions
[    0.005073] CPU features: detected: 32-bit EL1 Support
[    0.012278] CPU: All CPU(s) started at EL2
[    0.012300] alternatives: patching kernel code
[    0.013652] devtmpfs: initialized
[    0.017067] KASLR disabled due to lack of seed
[    0.017289] clocksource: jiffies: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.017305] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.018338] pinctrl core: initialized pinctrl subsystem
[    0.019342] DMI not present or invalid.
[    0.019784] NET: Registered protocol family 16
[    0.021259] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
[    0.021311] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for
atomic allocations
[    0.021426] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for
atomic allocations
[    0.021496] audit: initializing netlink subsys (disabled)
[    0.021629] audit: type=2000 audit(0.020:1): state=initialized
audit_enabled=0 res=1
[    0.022505] thermal_sys: Registered thermal governor 'step_wise'
[    0.022509] thermal_sys: Registered thermal governor 'power_allocator'
[    0.022682] cpuidle: using governor menu
[    0.022850] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.022927] ASID allocator initialised with 65536 entries
[    0.024145] Serial: AMBA PL011 UART driver
[    0.041645] debugfs: Directory 'dummy-iomuxc-gpr@30340000' with
parent 'regmap' already present!
[    0.041830] imx8mn-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
[    0.052970] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.052983] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.052989] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.052996] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.053895] cryptd: max_cpu_qlen set to 1000
[    0.056109] ACPI: Interpreter disabled.
[    0.057564] iommu: Default domain type: Translated
[    0.057749] vgaarb: loaded
[    0.058026] SCSI subsystem initialized
[    0.058325] usbcore: registered new interface driver usbfs
[    0.058362] usbcore: registered new interface driver hub
[    0.058390] usbcore: registered new device driver usb
[    0.059321] pps_core: LinuxPPS API ver. 1 registered
[    0.059328] pps_core: Software ver. 5.3.6 - Copyright 2005-2007
Rodolfo Giometti <giometti@linux.it>
[    0.059344] PTP clock support registered
[    0.059447] EDAC MC: Ver: 3.0.0
[    0.060554] FPGA manager framework
[    0.060630] Advanced Linux Sound Architecture Driver Initialized.
[    0.061273] clocksource: Switched to clocksource arch_sys_counter
[    0.061426] VFS: Disk quotas dquot_6.6.0
[    0.061473] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.061644] pnp: PnP ACPI: disabled
[    0.066690] NET: Registered protocol family 2
[    0.067067] tcp_listen_portaddr_hash hash table entries: 1024
(order: 2, 16384 bytes, linear)
[    0.067129] TCP established hash table entries: 16384 (order: 5,
131072 bytes, linear)
[    0.067243] TCP bind hash table entries: 16384 (order: 6, 262144
bytes, linear)
[    0.067480] TCP: Hash tables configured (established 16384 bind 16384)
[    0.067584] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.067628] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.067767] NET: Registered protocol family 1
[    0.068079] RPC: Registered named UNIX socket transport module.
[    0.068085] RPC: Registered udp transport module.
[    0.068091] RPC: Registered tcp transport module.
[    0.068096] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.068107] PCI: CLS 0 bytes, default 64
[    0.068832] kvm [1]: IPA Size Limit: 40 bits
[    0.070122] kvm [1]: GICv3: no GICV resource entry
[    0.070130] kvm [1]: disabling GICv2 emulation
[    0.070148] kvm [1]: GIC system register CPU interface enabled
[    0.070226] kvm [1]: vgic interrupt IRQ9
[    0.070324] kvm [1]: Hyp mode initialized successfully
[    0.073099] Initialise system trusted keyrings
[    0.073215] workingset: timestamp_bits=42 max_order=19 bucket_order=0
[    0.078624] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.079194] NFS: Registering the id_resolver key type
[    0.079217] Key type id_resolver registered
[    0.079222] Key type id_legacy registered
[    0.079296] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.079434] 9p: Installing v9fs 9p2000 file system support
[    0.115831] Key type asymmetric registered
[    0.115839] Asymmetric key parser 'x509' registered
[    0.115869] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 245)
[    0.115879] io scheduler mq-deadline registered
[    0.115885] io scheduler kyber registered
[    0.124640] EINJ: ACPI disabled.
[    0.132983] imx-sdma 302b0000.dma-controller: Direct firmware load
for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.132998] imx-sdma 302b0000.dma-controller: Falling back to sysfs
fallback for: imx/sdma/sdma-imx7d.bin
[    0.137956] SoC: i.MX8MN revision 1.0
[    0.141497] debugfs: Directory 'dummy-reset-controller@30390000'
with parent 'regmap' already present!
[    0.144593] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.146724] SuperH (H)SCI(F) driver initialized
[    0.147221] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 32,
base_baud = 1500000) is a IMX
[    1.066589] printk: console [ttymxc1] enabled
[    1.071601] msm_serial: driver initialized
[    1.083119] loop: module loaded
[    1.087075] megasas: 07.714.04.00-rc1
[    1.094700] libphy: Fixed MDIO Bus: probed
[    1.099830] tun: Universal TUN/TAP device driver, 1.6
[    1.105585] thunder_xcv, ver 1.0
[    1.108842] thunder_bgx, ver 1.0
[    1.112105] nicpf, ver 1.0
[    1.115567] pps pps0: new PPS source ptp0
[    1.120360] fec 30be0000.ethernet: Invalid MAC address: 00:00:00:00:00:00
[    1.127167] fec 30be0000.ethernet: Using random MAC address:
9a:70:df:87:45:f9
[    1.135522] libphy: fec_enet_mii_bus: probed
[    1.139876] mdio_bus 30be0000.ethernet-1: MDIO device at address 0
is missing.
[    1.147580] fec 30be0000.ethernet eth0: registered PHC device 0
[    1.154697] hclge is initializing
[    1.158041] hns3: Hisilicon Ethernet Network Driver for Hip08
Family - version
[    1.165294] hns3: Copyright (c) 2017 Huawei Corporation.
[    1.170646] e1000: Intel(R) PRO/1000 Network Driver
[    1.175543] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    1.181327] e1000e: Intel(R) PRO/1000 Network Driver
[    1.186297] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.192258] igb: Intel(R) Gigabit Ethernet Network Driver
[    1.197663] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.203264] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[    1.209536] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.215737] sky2: driver version 1.30
[    1.220345] VFIO - User Level meta-driver version: 0.3
[    1.227022] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.233569] ehci-pci: EHCI PCI platform driver
[    1.238050] ehci-platform: EHCI generic platform driver
[    1.243391] ehci-orion: EHCI orion driver
[    1.247489] ehci-exynos: EHCI Exynos driver
[    1.251746] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.257952] ohci-pci: OHCI PCI platform driver
[    1.262429] ohci-platform: OHCI generic platform driver
[    1.267751] ohci-exynos: OHCI Exynos driver
[    1.272394] usbcore: registered new interface driver usb-storage
[    1.280824] i2c /dev entries driver
[    1.290256] sdhci: Secure Digital Host Controller Interface driver
[    1.296504] sdhci: Copyright(c) Pierre Ossman
[    1.301332] Synopsys Designware Multimedia Card Interface Driver
[    1.308172] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.315878] ledtrig-cpu: registered to indicate activity on CPUs
[    1.323082] usbcore: registered new interface driver usbhid
[    1.328672] usbhid: USB HID core driver
[    1.337392] NET: Registered protocol family 17
[    1.341985] 9pnet: Installing 9P2000 support
[    1.345880] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA
[    1.346322] Key type dns_resolver registered
[    1.357836] registered taskstats version 1
[    1.361945] Loading compiled-in X.509 certificates
[    1.385931] usb_phy_generic usbphynop1: supply vcc not found, using
dummy regulator
[    1.469795] ldo6: supplied by buck5
[    1.473495] i2c i2c-0: IMX I2C adapter registered
[    1.479703] i2c i2c-1: IMX I2C adapter registered
[    1.485718] pca953x 2-0020: supply vcc not found, using dummy regulator
[    1.492452] pca953x 2-0020: using no AI
[    1.498592] i2c i2c-2: IMX I2C adapter registered
[    1.504685] imx_usb 32e40000.usb: No over current polarity defined
[    1.511028] mmc2: new HS400 MMC card at address 0001
[    1.516927] mmcblk2: mmc2:0001 DG4016 14.7 GiB
[    1.518766] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[    1.521475] input: bd718xx-pwrkey as
/devices/platform/soc@0/30800000.bus/30a20000.i2c/i2c-0/0-004b/gpio-keys.0.auto/input/input0
[    1.521750] mmcblk2boot0: mmc2:0001 DG4016 partition 1 4.00 MiB
[    1.522512] ALSA device list:
[    1.522517]   No soundcards found.
[    1.550766] mmcblk2boot1: mmc2:0001 DG4016 partition 2 4.00 MiB
[    1.550884] mmcblk2rpmb: mmc2:0001 DG4016 partition 3 4.00 MiB,
chardev (234:0)
[    1.564866] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA
[    1.568283] Alternate GPT is invalid, using primary GPT.
[    1.577304]  mmcblk2: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15
[    1.589824] Waiting for root device /dev/mmcblk1p2...
[    1.664806] random: fast init done
[    1.674128] mmc1: host does not support reading read-only switch,
assuming write-enable
[    1.718167] mmc1: new ultra high speed SDR104 SDHC card at address 0007
[    1.725851] mmcblk1: mmc1:0007 SD32G 29.9 GiB
[    1.732479]  mmcblk1: p1 p2
[    2.488397] EXT4-fs (mmcblk1p2): mounted filesystem with ordered
data mode. Opts: (null)
[    2.496557] VFS: Mounted root (ext4 filesystem) on device 179:98.
[    2.503774] devtmpfs: mounted
[    2.509738] Freeing unused kernel memory: 5888K
[    2.514392] Run /sbin/init as init process
INIT: version 2.98 booting
Framebuffer /dev/fb0 not detected
Boot splashscreen disabled
Starting udev
[    2.760338] udevd[162]: starting version 3.2.10
[    2.778257] random: udevd: uninitialized urandom read (16 bytes read)
[    2.785192] random: udevd: uninitialized urandom read (16 bytes read)
[    2.792171] random: udevd: uninitialized urandom read (16 bytes read)
[    2.817766] udevd[163]: starting eudev-3.2.10
[    2.874676] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 8 mkt
segment 0 supported-hw 0x100 0x1
[    2.897944] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
[    2.904197] imx-sdma 302c0000.dma-controller: loaded firmware 4.5
[    2.910456] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5
[    2.919245] input: 30370000.snvs:snvs-powerkey as
/devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input1
[    2.937768] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[    2.944154] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system
clock to 1970-01-01T00:00:00 UTC (0)
[    2.955077] bd718xx-clk bd71847-clk.1.auto: No parent clk found
[    2.964447] bd718xx-clk: probe of bd71847-clk.1.auto failed with error -22
[    2.976128] caam 30900000.crypto: Entropy delay = 3200
[    2.994398] caam 30900000.crypto: Instantiated RNG4 SH0
[    3.006539] caam 30900000.crypto: Instantiated RNG4 SH1
[    3.011853] caam 30900000.crypto: device ID = 0x0a16040100000100 (Era 9)
[    3.018606] caam 30900000.crypto: job rings = 3, qi = 0
[    3.136541] caam algorithms registered in /proc/crypto
[    3.142452] caam 30900000.crypto: caam pkc algorithms registered in
/proc/crypto
[    3.149871] caam 30900000.crypto: registering rng-caam
[    3.188379] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[    3.193887] random: crng init done
[    3.197317] random: 4 urandom warning(s) missed due to ratelimiting
[    4.495676] fec 30be0000.ethernet eth0: Unable to connect to phy
[    4.668823] cfg80211: Loading compiled-in X.509 certificates for
regulatory database
[    4.683148] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    4.844337] NET: Registered protocol family 10
[    4.850163] Segment Routing with IPv6
[    4.948004] Bluetooth: Core ver 2.22
[    4.951732] NET: Registered protocol family 31
[    4.956234] Bluetooth: HCI device and connection manager initialized
[    4.962641] Bluetooth: HCI socket layer initialized
[    4.967605] Bluetooth: L2CAP socket layer initialized
[    4.967638] Bluetooth: SCO socket layer initialized
[    5.050299] nfc: nfc_init: NFC Core ver 0.1
[    5.054643] NET: Registered protocol family 39

Poky (Yocto Project Reference Distro)
3.2+snapshot-ed7151f9856791fc4a24b1a0a88f87c442b29f38 imx8mn-ddr4-evk
/dev/ttymxc1

imx8mn-ddr4-evk login:
====
-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Fabio Estevam]

Hi Andrey,

On Thu, Mar 4, 2021 at 9:56 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote:

> I've applied the patch locally to my build, and imx8mn-ddr4-evk boots
> without errors or additional interactions to the command prompt. See
> the boot log at the end of the mail.

Excellent, thanks for testing it.

> I can submit it as a PR against u-boot-fslc repository, or you prefer
> to do it yourself?

Please submit it.

> I guess there is no need to wait for it applied upstream, since it is
> quite a straightforward fix that is needed.

Is there any imx8m platform that is missing to test?

My understanding is that it was tested on imx8mm-evk, imx8mn-evk.

Does it also boot fine on imx8mq-evk and imx8mp-evk?

Thanks

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

Hi Fabio,

On Thu, Mar 4, 2021 at 2:41 PM Fabio Estevam <festevam@gmail.com> wrote:
>
> Hi Andrey,
>
> On Thu, Mar 4, 2021 at 9:56 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
>
> > I've applied the patch locally to my build, and imx8mn-ddr4-evk boots
> > without errors or additional interactions to the command prompt. See
> > the boot log at the end of the mail.
>
> Excellent, thanks for testing it.
>
> > I can submit it as a PR against u-boot-fslc repository, or you prefer
> > to do it yourself?
>
> Please submit it.

Sure, would do.

>
> > I guess there is no need to wait for it applied upstream, since it is
> > quite a straightforward fix that is needed.
>
> Is there any imx8m platform that is missing to test?
>
> My understanding is that it was tested on imx8mm-evk, imx8mn-evk.
>
> Does it also boot fine on imx8mq-evk and imx8mp-evk?

If we speak about the patch - then not, it is aimed at imx8mn-evk.

If we speak about the boot container support: I've tested it also on imx8mp-evk.

Currently, I do not posses the imx8mq-evk so there were no tests done
there. But the implementation I did also does not include it, since I
had no means to test it there. It can be extended onto imx8mq-evk
further, but I propose that this would be rather done by anyone with
the access to the HW for testing. Extension is quite straightforward,
there are few variables that should be defined and one
MACHINEOVERRIDE, all of it is already done for Mini, Nano and Plus.

I can also propose that this implementation would be submitted as a PR
first, reviewed and merged into meta-freescale. After that - support
for imx8mq-evk can be added.

>
> Thanks



-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Fabio Estevam]

Hi Andrey,

On Thu, Mar 4, 2021 at 10:53 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote:

> If we speak about the boot container support: I've tested it also on imx8mp-evk.

Yes, I am talking about your boot container patches.

> Currently, I do not posses the imx8mq-evk so there were no tests done
> there. But the implementation I did also does not include it, since I
> had no means to test it there. It can be extended onto imx8mq-evk
> further, but I propose that this would be rather done by anyone with
> the access to the HW for testing. Extension is quite straightforward,
> there are few variables that should be defined and one
> MACHINEOVERRIDE, all of it is already done for Mini, Nano and Plus.
>
> I can also propose that this implementation would be submitted as a PR
> first, reviewed and merged into meta-freescale. After that - support
> for imx8mq-evk can be added.

Excellent, I can help testing on imx8mq-evk.

Thanks for working on this.

Cheers

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

Hello Peter,

On Thu, Mar 4, 2021 at 11:48 AM Peter Bergin <peter@berginkonsult.se> wrote:
>
> Hi Andrey,
>
> On 2021-03-03 17:54, Andrey Zhizhikin wrote:
> > I'm working on this solution in my fork, and have it almost ready for
> > submission.
> >
> > If anyone would be interested to try it out and test, you can have a
> > look athttps://github.com/zandrey/meta-freescale/tree/boot-container-for-mx8m-fslc
> >
> > I'll be cleaning it up and getting ready for submission soon(ish).
> > Currently, the only things that is not supported is OP-TEE - I was not
> > able to boot the 2020.10 with it, so I removed it for the time being.
> >
> > What I've tested today with this implementation is:
> > # DISTRO=poky MACHINE=imx8mm-lpddr4-evk bitbake core-image-base
> >
> > Had it booted to the shell prompt.
>
> thanks for the good work! I've tried to boot this on a imx8mn-ddr4-evk
> and see some issues with u-boot environment. I had to tweak the
> environment in order to get this to boot from SD card.

Thanks for testing it out!

I saw the same issue with booting the Nano, and did the same
adjustment on my end for testing purposes.

>
> Variable - default -> changed to:
>      mmcdev - 0 -> 1
>      image - Image.itb -> Image
>      boot_fit - try -> false
>
> Seems like CONFIG_SYS_MMC_ENV_DEV is missing in the defconfig for
> imx8mn_ddr4_evk (it is present for imx8mm_evk and imx8mp_evk).

I was about to say that Nano needs changes done in 7d080773347
("Convert CONFIG_SYS_MMC_ENV_DEV et al to Kconfig") upstream, but
Faboi chased my up with the patch already. :)

> I can also see a difference for 'image' and 'boot_fit' variable,
> include/configs/imx8mn_evk.h differs from
> include/configs/imx8m{m,p}_evk.h. So in order to get Nano EVK fully
> working the u-boot environment needs an update.
>
> After handling the issue above the Nano EVK boots fine. I put the output
> from the console below for the interested.
>
> Best regards,
> /Peter
>
>
> U-Boot SPL 2020.10+fslc+g5003fc093c (Dec 09 2020 - 17:09:55 +0000)
> Normal Boot
> WDT:   Started with servicing (60s timeout)
> Trying to boot from BOOTROM
> image offset 0x8000, pagesize 0x200, ivt offset 0x0
> NOTICE:  BL31: v2.2(release):rel_imx_5.4.70_2.3.0-0-gf1d7187f2
> NOTICE:  BL31: Built : 09:58:42, Dec  1 2020
>
>
> U-Boot 2020.10+fslc+g5003fc093c (Dec 09 2020 - 17:09:55 +0000)
>
> CPU:   Freescale i.MX8MNano Quad rev1.0 at 1200 MHz
> Reset cause: POR
> Model: NXP i.MX8MNano DDR4 EVK board
> DRAM:  2 GiB
> WDT:   Started with servicing (60s timeout)
> MMC:   FSL_SDHC: 1, FSL_SDHC: 2
> Loading Environment from MMC... Run CMD11 1.8V switch
> OK
> In:    serial
> Out:   serial
> Err:   serial
> Net:   No ethernet found.
> Hit any key to stop autoboot:  0
> Run CMD11 1.8V switch
> switch to partitions #0, OK
> mmc1 is current device
> Run CMD11 1.8V switch
> Failed to load 'boot.scr'
> 31568384 bytes read in 391 ms (77 MiB/s)
> Booting from mmc ...
> 23443 bytes read in 12 ms (1.9 MiB/s)
> Moving Image from 0x40480000 to 0x40600000, end=424b0000
> ## Flattened Device Tree blob at 43000000
>     Booting using the fdt blob at 0x43000000
>     Loading Device Tree to 000000004fff7000, end 000000004ffffb92 ... OK
>
> Starting kernel ...
>
> [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
> [    0.000000] Linux version 5.10.18+ge96f454f9d4b (oe-user@oe-host)
> (aarch64-poky-linux-gcc (GCC) 10.2.0, GNU ld (GNU Binutils)
> 2.36.1.20210209) #1 SMP PR
> EEMPT Tue Feb 23 21:32:29 UTC 2021
> [    0.000000] Machine model: NXP i.MX8MNano DDR4 EVK board
> [    0.000000] efi: UEFI not found.
> [    0.000000] cma: Reserved 32 MiB at 0x00000000be000000
> [    0.000000] NUMA: No NUMA configuration found
> [    0.000000] NUMA: Faking a node at [mem
> 0x0000000040000000-0x00000000bfffffff]
> [    0.000000] NUMA: NODE_DATA [mem 0xbdbe1b00-0xbdbe3fff]
> [    0.000000] Zone ranges:
> [    0.000000]   DMA      [mem 0x0000000040000000-0x000000007fffffff]
> [    0.000000]   DMA32    [mem 0x0000000080000000-0x00000000bfffffff]
> [    0.000000]   Normal   empty
> [    0.000000] Movable zone start for each node
> [    0.000000] Early memory node ranges
> [    0.000000]   node   0: [mem 0x0000000040000000-0x00000000bfffffff]
> [    0.000000] Initmem setup node 0 [mem
> 0x0000000040000000-0x00000000bfffffff]
> [    0.000000] psci: probing for conduit method from DT.
> [    0.000000] psci: PSCIv1.1 detected in firmware.
> [    0.000000] psci: Using standard PSCI v0.2 function IDs
> [    0.000000] psci: MIGRATE_INFO_TYPE not supported.
> [    0.000000] psci: SMC Calling Convention v1.1
> [    0.000000] percpu: Embedded 23 pages/cpu s56280 r8192 d29736 u94208
> [    0.000000] Detected VIPT I-cache on CPU0
> [    0.000000] CPU features: detected: ARM erratum 845719
> [    0.000000] CPU features: detected: GIC system register CPU interface
> [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516096
> [    0.000000] Policy zone: DMA32
> [    0.000000] Kernel command line: console=ttymxc1,115200
> root=/dev/mmcblk1p2 rootwait rw
> [    0.000000] Dentry cache hash table entries: 262144 (order: 9,
> 2097152 bytes, linear)
> [    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576
> bytes, linear)
> [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
> [    0.000000] software IO TLB: mapped [mem
> 0x000000007bfff000-0x000000007ffff000] (64MB)
> [    0.000000] Memory: 1926588K/2097152K available (14464K kernel code,
> 2796K rwdata, 7540K rodata, 5888K init, 518K bss, 137796K reserved,
> 32768K cma-rese
> rved)
> [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
> [    0.000000] rcu: Preemptible hierarchical RCU implementation.
> [    0.000000] rcu:     RCU event tracing is enabled.
> [    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to
> nr_cpu_ids=4.
> [    0.000000]  Trampoline variant of Tasks RCU enabled.
> [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay
> is 25 jiffies.
> [    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
> [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
> [    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
> [    0.000000] GICv3: 128 SPIs implemented
> [    0.000000] GICv3: 0 Extended SPIs implemented
> [    0.000000] GICv3: Distributor has no Range Selector support
> [    0.000000] GICv3: 16 PPIs implemented
> [    0.000000] GICv3: CPU0: found redistributor 0 region
> 0:0x0000000038880000
> [    0.000000] ITS: No ITS available, not enabling LPIs
> [    0.000000] random: get_random_bytes called from
> start_kernel+0x330/0x4f4 with crng_init=0
> [    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
> [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff
> max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
> [    0.000003] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps
> every 2199023255500ns
> [    0.000614] Console: colour dummy device 80x25
> [    0.000688] Calibrating delay loop (skipped), value calculated using
> timer frequency.. 16.00 BogoMIPS (lpj=32000)
> [    0.000700] pid_max: default: 32768 minimum: 301
> [    0.000768] LSM: Security Framework initializing
> [    0.000825] Mount-cache hash table entries: 4096 (order: 3, 32768
> bytes, linear)
> [    0.000843] Mountpoint-cache hash table entries: 4096 (order: 3,
> 32768 bytes, linear)
> [    0.002083] rcu: Hierarchical SRCU implementation.
> [    0.003483] EFI services will not be available.
> [    0.003663] smp: Bringing up secondary CPUs ...
> [    0.004046] Detected VIPT I-cache on CPU1
> [    0.004074] GICv3: CPU1: found redistributor 1 region
> 0:0x00000000388a0000
> [    0.004113] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
> [    0.004516] Detected VIPT I-cache on CPU2
> [    0.004533] GICv3: CPU2: found redistributor 2 region
> 0:0x00000000388c0000
> [    0.004558] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
> [    0.004934] Detected VIPT I-cache on CPU3
> [    0.004949] GICv3: CPU3: found redistributor 3 region
> 0:0x00000000388e0000
> [    0.004972] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
> [    0.005027] smp: Brought up 1 node, 4 CPUs
> [    0.005051] SMP: Total of 4 processors activated.
> [    0.005058] CPU features: detected: 32-bit EL0 Support
> [    0.005066] CPU features: detected: CRC32 instructions
> [    0.005073] CPU features: detected: 32-bit EL1 Support
> [    0.012237] CPU: All CPU(s) started at EL2
> [    0.012259] alternatives: patching kernel code
> [    0.013607] devtmpfs: initialized
> [    0.017018] KASLR disabled due to lack of seed
> [    0.017241] clocksource: jiffies: mask: 0xffffffff max_cycles:
> 0xffffffff, max_idle_ns: 7645041785100000 ns
> [    0.017256] futex hash table entries: 1024 (order: 4, 65536 bytes,
> linear)
> [    0.018296] pinctrl core: initialized pinctrl subsystem
> [    0.019308] DMI not present or invalid.
> [    0.019748] NET: Registered protocol family 16
> [    0.021180] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic
> allocations
> [    0.021231] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for
> atomic allocations
> [    0.021347] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for
> atomic allocations
> [    0.021419] audit: initializing netlink subsys (disabled)
> [    0.021555] audit: type=2000 audit(0.020:1): state=initialized
> audit_enabled=0 res=1
> [    0.022425] thermal_sys: Registered thermal governor 'step_wise'
> [    0.022429] thermal_sys: Registered thermal governor 'power_allocator'
> [    0.022601] cpuidle: using governor menu
> [    0.022771] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
> [    0.022849] ASID allocator initialised with 65536 entries
> [    0.024052] Serial: AMBA PL011 UART driver
> [    0.041518] debugfs: Directory 'dummy-iomuxc-gpr@30340000' with
> parent 'regmap' already present!
> [    0.041703] imx8mn-pinctrl 30330000.pinctrl: initialized IMX pinctrl
> driver
> [    0.052834] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
> [    0.052847] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
> [    0.052854] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
> [    0.052861] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
> [    0.053748] cryptd: max_cpu_qlen set to 1000
> [    0.055961] ACPI: Interpreter disabled.
> [    0.057435] iommu: Default domain type: Translated
> [    0.057624] vgaarb: loaded
> [    0.057897] SCSI subsystem initialized
> [    0.058185] usbcore: registered new interface driver usbfs
> [    0.058221] usbcore: registered new interface driver hub
> [    0.058248] usbcore: registered new device driver usb
> [    0.059177] pps_core: LinuxPPS API ver. 1 registered
> [    0.059185] pps_core: Software ver. 5.3.6 - Copyright 2005-2007
> Rodolfo Giometti <giometti@linux.it>
> [    0.059201] PTP clock support registered
> [    0.059306] EDAC MC: Ver: 3.0.0
> [    0.060391] FPGA manager framework
> [    0.060465] Advanced Linux Sound Architecture Driver Initialized.
> [    0.061121] clocksource: Switched to clocksource arch_sys_counter
> [    0.061268] VFS: Disk quotas dquot_6.6.0
> [    0.061313] VFS: Dquot-cache hash table entries: 512 (order 0, 4096
> bytes)
> [    0.061487] pnp: PnP ACPI: disabled
> [    0.066451] NET: Registered protocol family 2
> [    0.066829] tcp_listen_portaddr_hash hash table entries: 1024 (order:
> 2, 16384 bytes, linear)
> [    0.066866] TCP established hash table entries: 16384 (order: 5,
> 131072 bytes, linear)
> [    0.067009] TCP bind hash table entries: 16384 (order: 6, 262144
> bytes, linear)
> [    0.067243] TCP: Hash tables configured (established 16384 bind 16384)
> [    0.067354] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
> [    0.067397] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes,
> linear)
> [    0.067541] NET: Registered protocol family 1
> [    0.067871] RPC: Registered named UNIX socket transport module.
> [    0.067878] RPC: Registered udp transport module.
> [    0.067883] RPC: Registered tcp transport module.
> [    0.067889] RPC: Registered tcp NFSv4.1 backchannel transport module.
> [    0.067899] PCI: CLS 0 bytes, default 64
> [    0.068602] kvm [1]: IPA Size Limit: 40 bits
> [    0.069885] kvm [1]: GICv3: no GICV resource entry
> [    0.069892] kvm [1]: disabling GICv2 emulation
> [    0.069909] kvm [1]: GIC system register CPU interface enabled
> [    0.069987] kvm [1]: vgic interrupt IRQ9
> [    0.070085] kvm [1]: Hyp mode initialized successfully
> [    0.072787] Initialise system trusted keyrings
> [    0.072907] workingset: timestamp_bits=42 max_order=19 bucket_order=0
> [    0.078327] squashfs: version 4.0 (2009/01/31) Phillip Lougher
> [    0.078890] NFS: Registering the id_resolver key type
> [    0.078913] Key type id_resolver registered
> [    0.078920] Key type id_legacy registered
> [    0.078993] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
> [    0.079130] 9p: Installing v9fs 9p2000 file system support
> [    0.115078] Key type asymmetric registered
> [    0.115086] Asymmetric key parser 'x509' registered
> [    0.115122] Block layer SCSI generic (bsg) driver version 0.4 loaded
> (major 245)
> [    0.115129] io scheduler mq-deadline registered
> [    0.115135] io scheduler kyber registered
> [    0.123922] EINJ: ACPI disabled.
> [    0.132282] imx-sdma 302b0000.dma-controller: Direct firmware load
> for imx/sdma/sdma-imx7d.bin failed with error -2
> [    0.132297] imx-sdma 302b0000.dma-controller: Falling back to sysfs
> fallback for: imx/sdma/sdma-imx7d.bin
> [    0.137249] SoC: i.MX8MN revision 1.0
> [    0.140766] debugfs: Directory 'dummy-reset-controller@30390000' with
> parent 'regmap' already present!
> [    0.143941] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> [    0.146096] SuperH (H)SCI(F) driver initialized
> [    0.146596] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 32,
> base_baud = 1500000) is a IMX
> [    1.065937] printk: console [ttymxc1] enabled
> [    1.070947] msm_serial: driver initialized
> [    1.082458] loop: module loaded
> [    1.086414] megasas: 07.714.04.00-rc1
> [    1.093989] libphy: Fixed MDIO Bus: probed
> [    1.099118] tun: Universal TUN/TAP device driver, 1.6
> [    1.104849] thunder_xcv, ver 1.0
> [    1.108118] thunder_bgx, ver 1.0
> [    1.111377] nicpf, ver 1.0
> [    1.114880] pps pps0: new PPS source ptp0
> [    1.119629] fec 30be0000.ethernet: Invalid MAC address: 00:00:00:00:00:00
> [    1.126434] fec 30be0000.ethernet: Using random MAC address:
> fa:f1:4e:05:80:92
> [    1.134775] libphy: fec_enet_mii_bus: probed
> [    1.139128] mdio_bus 30be0000.ethernet-1: MDIO device at address 0 is
> missing.
> [    1.146824] fec 30be0000.ethernet eth0: registered PHC device 0
> [    1.153944] hclge is initializing
> [    1.157313] hns3: Hisilicon Ethernet Network Driver for Hip08 Family
> - version
> [    1.164542] hns3: Copyright (c) 2017 Huawei Corporation.
> [    1.169906] e1000: Intel(R) PRO/1000 Network Driver
> [    1.174791] e1000: Copyright (c) 1999-2006 Intel Corporation.
> [    1.180579] e1000e: Intel(R) PRO/1000 Network Driver
> [    1.185550] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
> [    1.191506] igb: Intel(R) Gigabit Ethernet Network Driver
> [    1.196911] igb: Copyright (c) 2007-2014 Intel Corporation.
> [    1.202521] igbvf: Intel(R) Gigabit Virtual Function Network Driver
> [    1.208794] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
> [    1.214997] sky2: driver version 1.30
> [    1.219597] VFIO - User Level meta-driver version: 0.3
> [    1.226302] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> [    1.232842] ehci-pci: EHCI PCI platform driver
> [    1.237320] ehci-platform: EHCI generic platform driver
> [    1.242652] ehci-orion: EHCI orion driver
> [    1.246747] ehci-exynos: EHCI Exynos driver
> [    1.251003] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> [    1.257208] ohci-pci: OHCI PCI platform driver
> [    1.261683] ohci-platform: OHCI generic platform driver
> [    1.267007] ohci-exynos: OHCI Exynos driver
> [    1.271640] usbcore: registered new interface driver usb-storage
> [    1.280062] i2c /dev entries driver
> [    1.289493] sdhci: Secure Digital Host Controller Interface driver
> [    1.295727] sdhci: Copyright(c) Pierre Ossman
> [    1.300528] Synopsys Designware Multimedia Card Interface Driver
> [    1.307386] sdhci-pltfm: SDHCI platform and OF driver helper
> [    1.314751] ledtrig-cpu: registered to indicate activity on CPUs
> [    1.322067] usbcore: registered new interface driver usbhid
> [    1.327664] usbhid: USB HID core driver
> [    1.336365] NET: Registered protocol family 17
> [    1.340996] 9pnet: Installing 9P2000 support
> [    1.345334] Key type dns_resolver registered
> [    1.345734] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc]
> using ADMA
> [    1.350057] registered taskstats version 1
> [    1.360770] Loading compiled-in X.509 certificates
> [    1.384857] usb_phy_generic usbphynop1: supply vcc not found, using
> dummy regulator
> [    1.461779] mmc2: new HS400 MMC card at address 0001
> [    1.466108] ldo6: supplied by buck5
> [    1.468200] mmcblk2: mmc2:0001 DG4016 14.7 GiB
> [    1.470476] i2c i2c-0: IMX I2C adapter registered
> [    1.474998] mmcblk2boot0: mmc2:0001 DG4016 partition 1 4.00 MiB
> [    1.481024] i2c i2c-1: IMX I2C adapter registered
> [    1.485654] mmcblk2boot1: mmc2:0001 DG4016 partition 2 4.00 MiB
> [    1.491453] pca953x 2-0020: supply vcc not found, using dummy regulator
> [    1.496785] mmcblk2rpmb: mmc2:0001 DG4016 partition 3 4.00 MiB,
> chardev (234:0)
> [    1.502791] pca953x 2-0020: using no AI
> [    1.514527]  mmcblk2: p1 p2 p3 p4 p5
> [    1.515306] i2c i2c-2: IMX I2C adapter registered
> [    1.524296] imx_usb 32e40000.usb: No over current polarity defined
> [    1.538182] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
> [    1.540843] input: bd718xx-pwrkey as
> /devices/platform/soc@0/30800000.bus/30a20000.i2c/i2c-0/0-004b/gpio-keys.0.auto/input/input0
> [    1.556001] ALSA device list:
> [    1.558994]   No soundcards found.
> [    1.574209] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc]
> using ADMA
> [    1.581908] Waiting for root device /dev/mmcblk1p2...
> [    1.676516] random: fast init done
> [    1.723156] mmc1: host does not support reading read-only switch,
> assuming write-enable
> [    1.758762] mmc1: new ultra high speed SDR104 SDHC card at address e624
> [    1.766795] mmcblk1: mmc1:e624 SU08G 7.40 GiB
> [    1.782688]  mmcblk1: p1 p2
> [    1.816060] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data
> mode. Opts: (null)
> [    1.824241] VFS: Mounted root (ext4 filesystem) on device 179:98.
> [    1.836254] devtmpfs: mounted
> [    1.842210] Freeing unused kernel memory: 5888K
> [    1.846868] Run /sbin/init as init process
> INIT: version 2.99 booting
> Framebuffer /dev/fb0 not detected
> Boot splashscreen disabled
> Starting udev
> [    2.083507] udevd[163]: starting version 3.2.10
> [    2.099256] random: udevd: uninitialized urandom read (16 bytes read)
> [    2.106263] random: udevd: uninitialized urandom read (16 bytes read)
> [    2.113239] random: udevd: uninitialized urandom read (16 bytes read)
> [    2.138124] udevd[164]: starting eudev-3.2.10
> [    2.188777] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 8 mkt
> segment 0 supported-hw 0x100 0x1
> [    2.204639] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
> [    2.210970] imx-sdma 302c0000.dma-controller: loaded firmware 4.5
> [    2.217304] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5
> [    2.253252] input: 30370000.snvs:snvs-powerkey as
> /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input1
> [    2.254641] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
> [    2.274836] bd718xx-clk bd71847-clk.1.auto: No parent clk found
> [    2.275097] caam 30900000.crypto: Entropy delay = 3200
> [    2.281771] bd718xx-clk: probe of bd71847-clk.1.auto failed with
> error -22
> [    2.292932] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock
> to 2018-03-09T13:03:11 UTC (1520600591)
> [    2.300969] caam 30900000.crypto: Instantiated RNG4 SH0
> [    2.311650] caam 30900000.crypto: Instantiated RNG4 SH1
> [    2.318359] caam 30900000.crypto: device ID = 0x0a16040100000100 (Era 9)
> [    2.326094] caam 30900000.crypto: job rings = 3, qi = 0
> [    2.421546] caam algorithms registered in /proc/crypto
> [    2.428007] caam 30900000.crypto: caam pkc algorithms registered in
> /proc/crypto
> [    2.435437] caam 30900000.crypto: registering rng-caam
> [    2.459802] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
> [    2.477805] random: crng init done
> [    2.481340] random: 4 urandom warning(s) missed due to ratelimiting
> [    2.741415] fec 30be0000.ethernet eth0: Unable to connect to phy
> [    2.852625] NET: Registered protocol family 10
> [    2.858442] Segment Routing with IPv6
> [    2.941803] Bluetooth: Core ver 2.22
> [    2.945546] NET: Registered protocol family 31
> [    2.950043] Bluetooth: HCI device and connection manager initialized
> [    2.956448] Bluetooth: HCI socket layer initialized
> [    2.961373] Bluetooth: L2CAP socket layer initialized
> [    2.966518] Bluetooth: SCO socket layer initialized
> [    3.033397] nfc: nfc_init: NFC Core ver 0.1
> [    3.037722] NET: Registered protocol family 39
>
> Poky (Yocto Project Reference Distro)
> 3.2+snapshot-c8075ed8f157468849d3199c3671b84a6f08785d imx8mn-ddr4-evk
> /dev/ttymxc1
>
> imx8mn-ddr4-evk login:
>
>
>


-- 
Regards,
Andrey.

Re: [meta-freescale] Want to use linux-fslc 5.10 with Dunfell

[Andrey Zhizhikin]

Hello Brian,

On Mon, Mar 1, 2021 at 8:59 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
>
> On Mon, Mar 1, 2021 at 2:35 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>
>>
>>
>> On Mon, Mar 1, 2021 at 1:31 PM Otavio Salvador <otavio.salvador@ossystems.com.br> wrote:
>>>
>>> Em seg., 1 de mar. de 2021 às 15:29, Brian Hutchinson
>>> <b.hutchman@gmail.com> escreveu:
>>> > Ok, don't quite know how to do that yet but will try to figure it out.
>>> >
>>> > I thought something was readily available since I saw the 5.10 recipe.
>>>
>>> It is ready for use in gatesgarth and master.
>>>
>>> --
>>> 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
>>
>>
>> I looked using web git this morning before I tried anything and I didn't see 5.10 in meta-freescale/recipes-kernel/linux for Gatesgarth.  Only the one recipe I mentioned above in master is there.
>>
>> Regards,
>>
>> Brian
>>
>
> Can someone school me on how this works?  I guess I don't know or understand the relationship between linux-fslc and linux-fslc-imx recipies in meta-freescale/recipies-kernel/linux

This has been answered by Peter already.

>
> Looking at the linux-fslc-imx_5.4.bb I've been using, it looks like 5.4.98 that i've been using really comes from nxp 5.4.24-1.1.0, kernel.org and some patches???  And a note to "upgraders" that recipe shouldn't collect patches but be applied to linux-fslc kernel tree.

The whole point of the note in the recipe is: if there is a patch that
should be applied to the kernel tree of linux-fslc-imx - then it
should be submitted against the respective branch (which is used in
the recipe) as a PR to https://github.com/Freescale/linux-fslc, and
not kept as a patch in the layer.

>
> Regards,
>
> Brian
>
>
>
> 
>


-- 
Regards,
Andrey.