From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] How to handle custom kernel config
Date: Wed, 18 Jun 2014 23:01:30 +0200 [thread overview]
Message-ID: <53A1FE2A.5060908@mind.be> (raw)
In-Reply-To: <CAGm1_kvcZDk_ke4OVgx1dO6_qWOhff7LupEKj42kgiq0Fyog6w@mail.gmail.com>
On 17/06/14 15:58, Yegor Yefremov wrote:
> On Tue, Jun 17, 2014 at 3:43 PM, Marco Trapanese
> <marcotrapanese@gmail.com> wrote:
>> Il 17/06/2014 15:40, Yegor Yefremov ha scritto:
>>
>>> As soon as you're happy with your new .config in the build directory,
>>> you just manually overwrite your board/sub_directory/linux.config Yegor
>>
>>
>> Ok, so I should do the following:
>>
>> 1) copy the custom file to .config
>
> This step will be made by Buildroot, when you first compile the kernel
> or perhaps if you invoke make linux-reconfigure. Your custom .config
> will be copied to output/build/linux-xxx
>
>> 2) edit that with make linux-menuconfig
>> 3) copy back the .config to custom file
This step can be done with the command
make linux-update-defconfig
Regards,
Arnout
>
> Other step are correct.
>
> Yegor
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind 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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2014-06-18 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 13:37 [Buildroot] How to handle custom kernel config Marco Trapanese
2014-06-17 13:40 ` Yegor Yefremov
2014-06-17 13:43 ` Marco Trapanese
2014-06-17 13:58 ` Yegor Yefremov
2014-06-18 21:01 ` Arnout Vandecappelle [this message]
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=53A1FE2A.5060908@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