From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot kconfig option
Date: Sun, 6 Sep 2015 12:10:33 +0300 [thread overview]
Message-ID: <20150906091033.GC2213@tarshish> (raw)
In-Reply-To: <CAKpDV8vL7GHk3cQ5Jk5o4G654KfQpQAfopsrA0Fotvu+vsaKMw@mail.gmail.com>
Hi Katoch,
On Sun, Sep 06, 2015 at 02:33:15PM +0530, Dinesh Guleria wrote:
> I am downloading kernel directly using buildroot. Then select "
> Using an in-tree defconfig file" then
> type the name of the defconfig.
>
> Here i am using a already existing defconfig file in kernel source tree.
>
> Now it could be the case existing configuration in Linux kernel source may
> not be as per my requirement.
>
> My question is, can i perform kconfig operation on the kernel source
> downloaded by buildroot , so that i can tune kernel as per my requirement ?
>
> Buildroot manual says :--
> "use make linux-menuconfig to open the Linux configuration editor"
> http://buildroot.uclibc.org/downloads/manual/manual.html#configure
>
> Or i download kernel source separately & configure it separately & tell
> buildroot to use it ?
>
> How you use to deal with this situation related to kernel kconfig ?
Please see "Linux kernel" in chapter 7 of the manual:
http://nightly.buildroot.org/manual.html#_configuration_of_other_components.
For information on storing your modified kernel configuration see section 9.4:
http://nightly.buildroot.org/manual.html#customize-store-package-config.
Hope this helps,
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-09-06 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 9:03 [Buildroot] Buildroot kconfig option Dinesh Guleria
2015-09-06 9:10 ` Baruch Siach [this message]
2015-09-06 11:37 ` Dinesh Guleria
2015-09-06 11:49 ` Thomas Petazzoni
2015-09-06 11:57 ` Dinesh Guleria
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=20150906091033.GC2213@tarshish \
--to=baruch@tkos.co.il \
--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