Skip to contentSkip to conversation

Building kernel backports for ARM with Yocto

DISCUSSION Marlon Smith 3 participants 9 messages Oct 18, 2017 – Oct 23, 2017

lore
Share & tools
lore
#0 lore raw

Hi everyone,

I'm trying to build the Linux backports project to get updated wifi drivers on an older kernel.  The problem is that when building backports, it first builds several tools that need to be run natively before cross-compiling the rest of the project.

I know how to write a bitbake recipe to compile natively, and how to write one to build for the target, but I can't figure out how to combine the two.  The backports project has steps for LTIB:

 %Build
 export PATH=$UNSPOOF_PATH

 make menuconfig prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

 export PATH=$SPOOF_PATH

 make prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

I believe what I need is an equivalent to the line export PATH=$UNSPOOF_PATH but I can't find anything in the Yocto documentation or mailing lists that would be equivalent to that.

Any help would be much appreciated!

Thanks

Marlon

#2 lore raw
In reply to Darcy Watkins

Darcy, thanks for the detailed reply!
Do you remember how you were able to get it to compile in the first place?  I end up with this error:
./kconf/conf: 1: ./kconf/conf: Syntax error: word unexpected (expecting ")")
..because backports needs to compile conf for x86_64, but instead compiles it for ARM.  Once that step is done, it needs to compile the rest of the project for ARM, but this error stops it.
I think I could work around the sysroot arm-wrestle because of the way our project is built, but haven't made it to that point yet. Here's the bb file I'm using:
---------------------------
include backports.inc
SRCBRANCH = "linux-4.2.y"
LOCALVERSION = "v4.2.6-1-0-g90118c7"
SRCREV = "90118c7656bb55243620c9dc9cc3f12582b1807f"

DEPENDS += "linux-myproject"do_configure_prepend() {
	export CROSS_COMPILE=${TARGET_PREFIX}
	export ARCH=${TARGET_ARCH}
	export KLIB_BUILD=${STAGING_KERNEL_DIR}
	export KLIB=${STAGING_DIR_TARGET}
	make
}

-----------------------------------

Quoted 96 lines · Darcy Watkins

I tried building backports under Yocto a few years back using Yocto daisy branch with kernel 3.4 for x86 and kernel 3.12 for ARM.  After a fair amount of pain I was able to get it to sort of work.  The problem was mainly a sysroot arm-wrestle between kernel and backports because they both generate the same kernel module packages.  It was a last-one-wins arm-wrestle.  It sort of worked OK with daisy branch, but newer yocto versions have stricter management of sysroots and staging areas.

I think what we need is some sort of virtual provider or alternatives scheme to make this work properly.

You can also run into problems related to exports to other out-of- tree modules but IIRC, it would only affect an out-of-tree module with an incompatible license.

I was able to run a few circa kernel 3.18 backports experimentally on a kernel 3.4 and a kernel 3.12.  Eventually we just upgraded the kernel.  Another project I know of used backports to update their kernel source and then created a recipe to build kernel from that source.

The notes/questions I had in the end were:

was building backports as out-of-tree kernel modules
was concerned that this wouldn’t provide updated kernel staging source, particularly with respect to any updated includes wasn’t sure what would be propagated into the sysroot should consider the backports use case that patches the kernel source and then perhaps use this to generate patchset to be added to kernel recipe (bbappend)
otherwise need to ensure proper handling of sysroot, staging, (as well as a notion of providers and/or alternatives like I mentioned earlier)

I haven’t touched this in years, but perhaps it may help a bit.
I think your best bet for short term is to use it to patch the kernel and then capture the changes as a patchset to add to a kernel recipe.


Regards,

Darcy

Darcy Watkins ::  Senior Staff Engineer, Firmware

SIERRA WIRELESS
Direct  +1 604 233 7989   ::  Fax  +1 604 231 1109  ::  Main  +1 604 231 1100
13811 Wireless Way  :: Richmond, BC Canada V6V 3A4
[P2]
[email protected] :: www.sierrawireless.com

From: [email protected] [mailto:yocto-bounces@yoctoproje ct.org] On Behalf Of Marlon Smith
Sent: October-18-17 3:14 PM
To: [email protected]
Subject: [yocto] Building kernel backports for ARM with Yocto
Hi everyone,

I'm trying to build the Linux backports project to get updated wifi drivers on an older kernel.  The problem is that when building backports, it first builds several tools that need to be run natively before cross-compiling the rest of the project.

I know how to write a bitbake recipe to compile natively, and how to write one to build for the target, but I can't figure out how to combine the two.  The backports project has steps for LTIB:

 %Build
 export PATH=$UNSPOOF_PATH

 make menuconfig prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

 export PATH=$SPOOF_PATH

 make prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

I believe what I need is an equivalent to the line export PATH=$UNSPOOF_PATH but I can't find anything in the Yocto documentation or mailing lists that would be equivalent to that.
Any help would be much appreciated!

Thanks

Marlon

#1 lore raw
In reply to Marlon Smith

I tried building backports under Yocto a few years back using Yocto daisy branch with kernel 3.4 for x86 and kernel 3.12 for ARM. After a fair amount of pain I was able to get it to sort of work. The problem was mainly a sysroot arm-wrestle between kernel and backports because they both generate the same kernel module packages. It was a last-one-wins arm-wrestle. It sort of worked OK with daisy branch, but newer yocto versions have stricter management of sysroots and staging areas.

I think what we need is some sort of virtual provider or alternatives scheme to make this work properly.

You can also run into problems related to exports to other out-of-tree modules but IIRC, it would only affect an out-of-tree module with an incompatible license.

I was able to run a few circa kernel 3.18 backports experimentally on a kernel 3.4 and a kernel 3.12. Eventually we just upgraded the kernel. Another project I know of used backports to update their kernel source and then created a recipe to build kernel from that source.

The notes/questions I had in the end were:

  *   was building backports as out-of-tree kernel modules
  *   was concerned that this wouldn’t provide updated kernel staging source, particularly with respect to any updated includes
  *   wasn’t sure what would be propagated into the sysroot
  *   should consider the backports use case that patches the kernel source and then perhaps use this to generate patchset to be added to kernel recipe (bbappend)
  *   otherwise need to ensure proper handling of sysroot, staging, (as well as a notion of providers and/or alternatives like I mentioned earlier)

I haven’t touched this in years, but perhaps it may help a bit.

I think your best bet for short term is to use it to patch the kernel and then capture the changes as a patchset to add to a kernel recipe.

Regards,

Darcy

Darcy Watkins :: Senior Staff Engineer, Firmware

SIERRA WIRELESS
Direct +1 604 233 7989 :: Fax +1 604 231 1109 :: Main +1 604 231 1100
13811 Wireless Way :: Richmond, BC Canada V6V 3A4
[P2]
[email protected]<mailto:[email protected]> :: www.sierrawireless.com<http://www.sierrawireless.com/>

From: [email protected] [mailto:[email protected]] On Behalf Of Marlon Smith
Sent: October-18-17 3:14 PM
To: [email protected]
Subject: [yocto] Building kernel backports for ARM with Yocto

Hi everyone,

I'm trying to build the Linux backports project to get updated wifi drivers on an older kernel. The problem is that when building backports, it first builds several tools that need to be run natively before cross-compiling the rest of the project.

I know how to write a bitbake recipe to compile natively, and how to write one to build for the target, but I can't figure out how to combine the two. The backports project has steps for LTIB:

%Build

export PATH=$UNSPOOF_PATH

make menuconfig prefix=%{_prefix} \

   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \

   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \

   KLIB_BUILD=${TOP}/rpm/BUILD/linux

export PATH=$SPOOF_PATH

make prefix=%{_prefix} \

   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \

   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \

   KLIB_BUILD=${TOP}/rpm/BUILD/linux

I believe what I need is an equivalent to the line export PATH=$UNSPOOF_PATH but I can't find anything in the Yocto documentation or mailing lists that would be equivalent to that.

Any help would be much appreciated!

Thanks

Marlon

#3 lore raw
In reply to Marlon Smith
Quoted 27 lines · Marlon Smith

Hi everyone,

I'm trying to build the Linux backports project to get updated wifi drivers on an older kernel. The problem is that when building backports, it first builds several tools that need to be run natively before cross-compiling the rest of the project.

I know how to write a bitbake recipe to compile natively, and how to write one to build for the target, but I can't figure out how to combine the two. The backports project has steps for LTIB:

%Build
export PATH=$UNSPOOF_PATH

 make menuconfig prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

export PATH=$SPOOF_PATH

 make prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux
Quoted 6 lines

I believe what I need is an equivalent to the line export PATH=$UNSPOOF_PATH but I can't find anything in the Yocto documentation or mailing lists that would be equivalent to that.

Any help would be much appreciated!

You might try this out

https://github.com/kraj/meta-himvis/blob/master/recipes-kernel/linux-backports/linux-backports_4.14-rc4.bb

it does not work out of box but with few fixes here and there it should work

Quoted 14 lines

Thanks

Marlon

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#4 lore raw
Quoted 42 lines · Khem Raj
Quoted 40 lines · Marlon Smith

Hi everyone,

I'm trying to build the Linux backports project to get updated wifi drivers
on an older kernel.  The problem is that when building backports, it first
builds several tools that need to be run natively before cross- compiling the
rest of the project.

I know how to write a bitbake recipe to compile natively, and how to write
one to build for the target, but I can't figure out how to combine the two.
The backports project has steps for LTIB:

 %Build
 export PATH=$UNSPOOF_PATH

 make menuconfig prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

 export PATH=$SPOOF_PATH

 make prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

I believe what I need is an equivalent to the line export PATH=$UNSPOOF_PATH
but I can't find anything in the Yocto documentation or mailing lists that
would be equivalent to that.

Quoted 8 lines
Quoted 1 line

Any help would be much appreciated!

You might try this out

https://github.com/kraj/meta-himvis/blob/master/recipes-kernel/linux-
backports/linux-backports_4.14-rc4.bb

it does not work out of box but with few fixes here and there it should work

It looks like that recipe inherits backports_module and kernel- backports_module-split.. do I need those files as well?

Quoted 16 lines
Quoted 16 lines

Thanks

Marlon

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#5 lore raw
Quoted 46 lines · Marlon Smith
Quoted 45 lines · Khem Raj
Quoted 33 lines · Marlon Smith

Hi everyone,

I'm trying to build the Linux backports project to get updated wifi drivers
on an older kernel. The problem is that when building backports, it first
builds several tools that need to be run natively before cross- compiling the
rest of the project.

I know how to write a bitbake recipe to compile natively, and how to write
one to build for the target, but I can't figure out how to combine the two.
The backports project has steps for LTIB:

%Build
export PATH=$UNSPOOF_PATH

 make menuconfig prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

export PATH=$SPOOF_PATH

 make prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux
Quoted 8 lines

I believe what I need is an equivalent to the line export PATH=$UNSPOOF_PATH
but I can't find anything in the Yocto documentation or mailing lists that
would be equivalent to that.

Any help would be much appreciated!

You might try this out

Quoted 9 lines
Quoted 5 lines

https://github.com/kraj/meta-himvis/blob/master/recipes-kernel/linux-
backports/linux-backports_4.14-rc4.bb

it does not work out of box but with few fixes here and there it should work

It looks like that recipe inherits backports_module and kernel- backports_module-split.. do I need those files as well?

backports_module is merged into recipe itsellf. Other one can be replaced with inehrtiting
module bbclasss

Quoted 16 lines
Quoted 16 lines
Quoted 16 lines

Thanks

Marlon

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#6 lore raw
Quoted 60 lines · Khem Raj
Quoted 58 lines · Marlon Smith
Quoted 56 lines · Khem Raj
Quoted 38 lines · Marlon Smith

Hi everyone,

I'm trying to build the Linux backports project to get updated wifi
drivers
on an older kernel.  The problem is that when building backports,
it first
builds several tools that need to be run natively before cross- compiling the
rest of the project.

I know how to write a bitbake recipe to compile natively, and how
to write
one to build for the target, but I can't figure out how to combine
the two.
The backports project has steps for LTIB:

 %Build
 export PATH=$UNSPOOF_PATH

 make menuconfig prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

 export PATH=$SPOOF_PATH

 make prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

Quoted 8 lines

I believe what I need is an equivalent to the line export PATH=$UNSPOOF_PATH
but I can't find anything in the Yocto documentation or mailing lists that
would be equivalent to that.

Any help would be much appreciated!

You might try this out

https://github.com/kraj/meta-himvis/blob/master/recipes-kernel/li
nux-
backports/linux-backports_4.14-rc4.bb

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

it does not work out of box but with few fixes here and there it should work

It looks like that recipe inherits backports_module and kernel- backports_module-split.. do I need those files as well?

backports_module is merged into recipe itsellf. Other one can be replaced with inehrtiting
module bbclasss

Ok I'll give that a try.  Thanks for the help!

Quoted 20 lines
Quoted 20 lines
Quoted 20 lines
Quoted 20 lines

Thanks

Marlon

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#7 lore raw
In reply to Khem Raj

Khem, with a couple of modifications I was able to get this script working perfectly and installing the modules into the system automatically.  Thanks a lot!
If you or anyone else would like a copy of the modified bitbake file I'd be happy to share it.

Quoted 88 lines · Khem Raj
Quoted 54 lines · On Thu, Oct 19, 2017 at 12:38 PM, Marlon Smith com> wrote:
Quoted 52 lines · Khem Raj
Quoted 38 lines · On Wed, Oct 18, 2017 at 3:13 PM, Marlon Smith il.c om> wrote:

Hi everyone,

I'm trying to build the Linux backports project to get updated wifi
drivers
on an older kernel.  The problem is that when building backports,
it first
builds several tools that need to be run natively before cross- compiling the
rest of the project.

I know how to write a bitbake recipe to compile natively, and how
to write
one to build for the target, but I can't figure out how to combine
the two.
The backports project has steps for LTIB:

 %Build
 export PATH=$UNSPOOF_PATH

 make menuconfig prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

 export PATH=$SPOOF_PATH

 make prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

Quoted 8 lines

I believe what I need is an equivalent to the line export PATH=$UNSPOOF_PATH
but I can't find anything in the Yocto documentation or mailing lists that
would be equivalent to that.

Any help would be much appreciated!

You might try this out

Quoted 9 lines
Quoted 6 lines

https://github.com/kraj/meta-himvis/blob/master/recipes-kernel/li
nux-
backports/linux-backports_4.14-rc4.bb

it does not work out of box but with few fixes here and there it should work

It looks like that recipe inherits backports_module and kernel- backports_module-split.. do I need those files as well?

backports_module is merged into recipe itsellf. Other one can be replaced with inehrtiting
module bbclasss

Quoted 19 lines
Quoted 19 lines
Quoted 19 lines

Thanks

Marlon

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#8 lore raw
Quoted 6 lines · Marlon Smith

Khem, with a couple of modifications I was able to get this script working perfectly and installing the modules into the system automatically. Thanks a lot!

If you or anyone else would like a copy of the modified bitbake file I'd be happy to share it.

Please contribute it back to meta-openembedded or meta-himvis
(https://github.com/kraj/meta-himvis)

Quoted 90 lines · Khem Raj

On Thu, Oct 19, 2017 at 12:38 PM, Marlon Smith <[email protected]> wrote:

On Wed, 2017-10-18 at 22:50 -0700, Khem Raj wrote:

On Wed, Oct 18, 2017 at 3:13 PM, Marlon Smith <[email protected] om> wrote:

Hi everyone,

I'm trying to build the Linux backports project to get updated wifi drivers
on an older kernel. The problem is that when building backports, it first
builds several tools that need to be run natively before cross- compiling the
rest of the project.

I know how to write a bitbake recipe to compile natively, and how to write
one to build for the target, but I can't figure out how to combine the two.
The backports project has steps for LTIB:

%Build
export PATH=$UNSPOOF_PATH

 make menuconfig prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

export PATH=$SPOOF_PATH

 make prefix=%{_prefix} \
   CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} \
   ARCH=$LINTARCH KLIB=${TOP}/rootfs/lib/modules/%{kversion} \
   KLIB_BUILD=${TOP}/rpm/BUILD/linux

I believe what I need is an equivalent to the line export PATH=$UNSPOOF_PATH
but I can't find anything in the Yocto documentation or mailing lists that
would be equivalent to that.

Any help would be much appreciated!

You might try this out

https://github.com/kraj/meta-himvis/blob/master/recipes-kernel/linux-
backports/linux-backports_4.14-rc4.bb

it does not work out of box but with few fixes here and there it should work

It looks like that recipe inherits backports_module and kernel- backports_module-split.. do I need those files as well?

backports_module is merged into recipe itsellf. Other one can be replaced with inehrtiting
module bbclasss

Thanks

Marlon

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto