diff options
author | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2016-06-14 12:19:58 +0200 |
---|---|---|
committer | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2016-06-18 15:05:15 +0200 |
commit | 53ced1f6d3da6b037d45a70ed0d8a25f5ab15142 (patch) | |
tree | 86b3f4bb56c4cce1a69ddb8956a73ec706246719 /package/json-javascript | |
parent | bcc8d367140d00f76aba6ef4387a12469fa0c024 (diff) | |
download | buildroot-53ced1f6d3da6b037d45a70ed0d8a25f5ab15142.tar.gz buildroot-53ced1f6d3da6b037d45a70ed0d8a25f5ab15142.zip |
linux: allow the selection of the architecture's default configuration
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>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/json-javascript')
0 files changed, 0 insertions, 0 deletions