From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] board: add support for ARC AXS101 and AXS103 Software Development Platforms
Date: Tue, 4 Aug 2015 15:55:25 +0200 [thread overview]
Message-ID: <20150804155525.58062d6e@free-electrons.com> (raw)
In-Reply-To: <1438695423.22313.22.camel@synopsys.com>
Alexey,
On Tue, 4 Aug 2015 13:37:04 +0000, Alexey Brodkin wrote:
> Hw, I do understand your concern with implicitly specified version of
> kernel/headers but what I meant if I use "make savedefconfig" it eliminates
> versions if they match today's defaults.
Not if you explicitly specify "custom version", i.e if you do:
Kernel Headers (Manually specified Linux version) --->
(4.1) linux version
Then you get:
BR2_KERNEL_HEADERS_VERSION=y
BR2_DEFAULT_KERNEL_VERSION="4.1"
which is what we want.
> So now if I understood you correctly you propose to insert:
> --------->8---------
> BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.2-rc5"
Yes for kernel version.
> BR2_DEFAULT_KERNEL_HEADERS="4.1.3"
But no for kernel headers: see above what you should do.
Again, please look at qemu_*_defconfig, they do the right thing:
# Lock to 4.1 headers to avoid breaking with newer kernels
BR2_KERNEL_HEADERS_VERSION=y
BR2_DEFAULT_KERNEL_VERSION="4.1"
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.1"
BR2_LINUX_KERNEL_DEFCONFIG="vexpress"
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-04 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 12:00 [Buildroot] [PATCH] board: add support for ARC AXS101 and AXS103 Software Development Platforms Alexey Brodkin
2015-08-04 12:57 ` Thomas Petazzoni
2015-08-04 13:17 ` Alexey Brodkin
2015-08-04 13:24 ` Thomas Petazzoni
2015-08-04 13:37 ` Alexey Brodkin
2015-08-04 13:55 ` Thomas Petazzoni [this message]
2015-08-04 14:12 ` Alexey Brodkin
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=20150804155525.58062d6e@free-electrons.com \
--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 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.