From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Cannot build Custom Kernel Module
Date: Wed, 13 Apr 2016 18:07:18 +0200 [thread overview]
Message-ID: <570E6EB6.8020003@mind.be> (raw)
In-Reply-To: <CAN34fozx7-myS-6xvHiwkZdovdfCO_vkjDJU8V427yEk5-ckAA@mail.gmail.com>
On 04/13/16 18:00, Stephen Beckwith wrote:
[snip]
> - The build root version I have is 2015.08.01 - this supports a 4.1.4
> kernel. Since 4.1.x is an LTS kernel, is there a way to tell/configure
> Buildroot to fetch a patch for the latest . release (currently 4.1.21)???
> Meaning, a patch from 4.1.4 -> 4.1.21? I've done something like this in the
> past, wasn't easy.
Just set BR2_LINUX_KERNEL_CUSTOM_VERSION and fill in the version.
Or, if you're using BR2_LINUX_KERNEL_SAME_AS_HEADERS, choose
BR2_KERNEL_HEADERS_VERSION and fill in the version.
This even works for versions > 4.1 if you want. Just claim that it's a 4.1
version.
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-04-13 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 18:25 [Buildroot] Cannot build Custom Kernel Module Stephen Beckwith
2016-04-12 21:07 ` Arnout Vandecappelle
2016-04-13 14:38 ` Stephen Beckwith
2016-04-13 15:37 ` Arnout Vandecappelle
2016-04-13 16:00 ` Stephen Beckwith
2016-04-13 16:07 ` Arnout Vandecappelle [this message]
2016-04-13 19:03 ` Stephen Beckwith
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=570E6EB6.8020003@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox