From: Marlon Smith <marlon.smith10@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Building kernel backports for ARM with Yocto
Date: Thu, 19 Oct 2017 12:38:16 -0700 [thread overview]
Message-ID: <1508441896.4636.70.camel@gmail.com> (raw)
In-Reply-To: <CAMKF1srFzdJusbLTTEikKQHrzKinot3=YgR+nkegsKGUCbM6tQ@mail.gmail.com>
On Wed, 2017-10-18 at 22:50 -0700, Khem Raj wrote:
> On Wed, Oct 18, 2017 at 3:13 PM, Marlon Smith <marlon.smith10@gmail.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
> >
> >
> > 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?
>
> >
> >
> >
> > Thanks
> >
> >
> > Marlon
> >
> >
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
next prev parent reply other threads:[~2017-10-19 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 22:13 Building kernel backports for ARM with Yocto Marlon Smith
2017-10-18 22:53 ` Darcy Watkins
2017-10-18 23:04 ` Marlon Smith
2017-10-19 5:50 ` Khem Raj
2017-10-19 19:38 ` Marlon Smith [this message]
2017-10-19 21:18 ` Khem Raj
2017-10-19 21:23 ` Marlon Smith
2017-10-23 18:07 ` Marlon Smith
2017-10-23 18:11 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1508441896.4636.70.camel@gmail.com \
--to=marlon.smith10@gmail.com \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.