PREFERRED_PROVIDER_virtual/kernel not works as expected

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

PREFERRED_PROVIDER_virtual/kernel not works as expected

4,478 Views
csoapy
Contributor III

I'm building the latest source on https://source.codeaurora.org/external/imx/imx-manifest for imx6q:

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

DISTRO=fsl-imx-fb MACHINE=imx6qsabreauto source fsl-setup-release.sh -b build-fb

But failed on switching kernel to linux-fslc_4.9 or 4.14, defined in 

imx-yocto-bsp/sources/meta-freescale/recipes-kernel/linux/linux-fslc_4.9.bb

imx-yocto-bsp/sources/meta-freescale/recipes-kernel/linux/linux-fslc_4.14.bb

Reproduce steps:

1. bitbake virtual/kernel && bitbake virtual/kernel -e | grep ^T=

    output:

        T="/home/XXX/imx-yocto-bsp/build-fb/tmp/work/imx6qsabreauto-poky-linux-gnueabi/linux-imx/4.9.88-r0/temp"

2. Add two lines to conf/local.conf:

       PREFERRED_PROVIDER_virtual/kernel = "linux-fslc"
       PREFERRED_VERSION_linux-fslc = "4.14"

3. bitbake virtual/kernel -c cleansstate

4. Check again: bitbake virtual/kernel -e | grep ^T=

        The output as same as in step 1, not switched to linux-fslc

Even if execute bitbake virtual/kernel without other parameters, linux-fslc still not built but linux-imx instead.

I tried yocto's official poky 2.5.1 as above steps, it switched kernel from linux-yocto_4.14.48 to linux-yocto-rt_4.15.18 successfully.

Labels (2)
0 Kudos
Reply
2 Replies

3,498 Views
csoapy
Contributor III

Anybody?

I also checked SRC_URI:

bitbake virtual/kernel -e | grep ^SRC_URI=

output:

SRC_URI="git://source.codeaurora.org/external/imx/linux-imx.git;protocol=https;branch=imx_4.9.88_2.0.0_ga"

not works.

AND, imx-4.1.15-2.0.3 on git.freescale.com not works too.

0 Kudos
Reply

3,498 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello 计龙 杨,

I’m trying to get to the root of this behavior. I’m currently testing it on the BSP Release. The BSP Releases point to a specific commit, it is possible that the kernel revision is fixed since it’s tied to this commit. It should be possible to override it, I’m looking for an alternative.

The Community BSP is a changing branch, which allows for much more flexibility in these variables.

I’ll let you know as soon as I have more information.

Regards,

0 Kudos
Reply