From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] perf: add kernel version checks
Date: Tue, 8 Jan 2013 09:15:34 +0100 [thread overview]
Message-ID: <20130108091534.38d07446@skate> (raw)
In-Reply-To: <50EBBFA8.1070503@mind.be>
Dear Arnout Vandecappelle,
On Tue, 08 Jan 2013 07:41:44 +0100, Arnout Vandecappelle wrote:
> There are a number of packages that would benefit from kernel version
> checks. For instance, the native driver implementations of igh-ethercat
> are specific for a certain kernel version. Would it be a good idea to
> make the kernel version user-configurable, and add a check for its
> correctness similar to the external toolchains?
Huh? The kernel version is already user configurable, thanks to the
BR2_LINUX_KERNEL_3_7, BR2_LINUX_KERNEL_SAME_AS_HEADERS,
BR2_LINUX_KERNEL_CUSTOM_VERSION, BR2_LINUX_KERNEL_CUSTOM_TARBALL,
BR2_LINUX_KERNEL_CUSTOM_GIT configuration options.
The thing is that when the BR2_LINUX_KERNEL_CUSTOM_TARBALL or
BR2_LINUX_KERNEL_CUSTOM_GIT options are used, you don't know (at the
Kconfig level), the kernel version that will be used.
And I don't think we should ask the user to tell us, through a separate
option, what kernel version his/her Git tree actually contains.
Or maybe I'm missing what you're proposing here?
Regarding the kernel and the autobuilders, my plan was to modify the
autobuilders script to randomly enable the kernel build. The script of
course knows, per-architecture, of a known-working kernel defconfig
file that it would use in the Buildroot configuration.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-08 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 20:40 [Buildroot] [git commit] perf: add kernel version checks Peter Korsgaard
2013-01-08 6:41 ` Arnout Vandecappelle
2013-01-08 8:15 ` Thomas Petazzoni [this message]
2013-01-08 8:28 ` Arnout Vandecappelle
2013-01-08 8:42 ` Thomas Petazzoni
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=20130108091534.38d07446@skate \
--to=thomas.petazzoni@free-electrons.com \
--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