From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: allow the selection of the architecture's default configuration
Date: Sat, 18 Jun 2016 15:05:45 +0200 [thread overview]
Message-ID: <20160618150545.0f4b1131@free-electrons.com> (raw)
In-Reply-To: <1465899598-2855-1-git-send-email-thomas.petazzoni@free-electrons.com>
Hello,
On Tue, 14 Jun 2016 12:19:58 +0200, Thomas Petazzoni wrote:
> To configure the Linux kernel, we currently provide two options:
>
> 1. Passing a defconfig name (for example "multi_v7"), to which we append
> "_defconfig" to run "make multi_v7_defconfig".
>
> 2. Passing a path to a custom configuration file.
>
> Unfortunately, those two possibilities do not allow to configure the
> kernel when you want to use the default configuration built into the
> kernel for a given architecture. For example, on ARM64, there is a
> single defconfig simply called "defconfig", which you can load by
> running "make defconfig".
>
> Using the mechanism (1) above doesn't work because we append
> "_defconfig" automatically.
>
> One solution would be to change (1) and require the user to enter the
> full defconfig named (i.e "multi_v7_defconfig" instead of "multi_v7"),
> but we would break all existing Buildroot configurations.
>
> So instead, we add a third option, which simply tells Buildroot to use
> the default configuration for the selected architecture. In this case,
> Buildroot will configure the kernel by running "make defconfig".
>
> Cc: Naresh Kamboju <naresh.kamboju@linaro.org>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> This proposal aims at replacing:
Applied to master. Thanks Yann for the review!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-06-18 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 10:19 [Buildroot] [PATCH] linux: allow the selection of the architecture's default configuration Thomas Petazzoni
2016-06-18 9:39 ` Yann E. MORIN
2016-06-18 13:05 ` Thomas Petazzoni [this message]
2016-06-19 14:35 ` Naresh Kamboju
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=20160618150545.0f4b1131@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox