All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How do I configure the kernel?
Date: Sat, 21 Nov 2009 05:00:12 +0000 (UTC)	[thread overview]
Message-ID: <he7s4s$330$1@ger.gmane.org> (raw)
In-Reply-To: b680c1c10911201435k3e8e6988pea7dcaaa301ee5d7@mail.gmail.com

On 2009-11-20, Nicholas Walton <nwalton@aplopteng.com> wrote:
> On Fri, Nov 20, 2009 at 2:23 PM, Grant Edwards
><grant.b.edwards@gmail.com> wrote:
>> How do you configure the kernel when using buildroot?
>
> make linux26-menuconfig

Doh!  I trield make kernel-menuconfig and several other
variations.  For future reference, is there somewhere that's
documented?

The next question was going to be where do I put a kernel
.config file if I already have one I want to use.  I can
probably do a "find" to search for files named .config and
figure out which is the right one. Then I assume I do "make
linux26-oldconfig"?

> Other targets, such as Busybox, follow the same convention.

Yes, the docs do explain how to configure busybox and uclibc.
I just hadn't guessed the correct "label" for doing the same
thing for the kernel.

-- 
Grant

  reply	other threads:[~2009-11-21  5:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 22:23 [Buildroot] How do I configure the kernel? Grant Edwards
     [not found] ` <b680c1c10911201430s25dadd6aj8d1c48afaff91445@mail.gmail.com>
2009-11-20 22:35   ` Nicholas Walton
2009-11-21  5:00     ` Grant Edwards [this message]
2009-11-21 18:20       ` Nicholas Walton
2009-11-22 20:44       ` Peter Korsgaard
2009-11-23 19:10         ` Grant Edwards
2009-11-23 20:01           ` Grant Edwards
2009-11-23 20:39             ` Nicholas Walton
2009-11-23 21:41               ` Grant Edwards
2009-11-23 21:50                 ` Nicholas Walton
2009-11-23 21:56                   ` Grant Edwards

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='he7s4s$330$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.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.