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: Mon, 23 Nov 2009 20:01:17 +0000 (UTC)	[thread overview]
Message-ID: <heepmc$umt$1@ger.gmane.org> (raw)
In-Reply-To: heemnr$jrk$1@ger.gmane.org

On 2009-11-23, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> On 2009-11-22, Peter Korsgaard <jacmet@uclibc.org> wrote:
>
>> Grant> The next question was going to be where do I put a kernel
>> Grant> .config file if I already have one I want to use.  I can
>> Grant> probably do a "find" to search for files named .config and
>> Grant> figure out which is the right one. Then I assume I do "make
>> Grant> linux26-oldconfig"?
>>
>> Use the LINUX26_KCONFIG environment variable, similar to
>> BUSYBOX_CONFIG_FILE / UCLIBC_CONFIG_FILE. I'll also update the doc about
>> that one.
>
> Sorry to be so dense, but I still don't get it.  I've got a
> .config file I want to use as the starting point for a
> "make oldconfig".  I can point LINUX26_KCONFIG at that .config
> file, but how do I do the "make oldconfig" step?

I got a working kernel by

 0) pick the arch, board, target filesystem options, etc.

 1) do a "make" and build everything (including a non-working kernel)

 2) overwrite output/build/linux-2.6.30.2/.config with my old
    but "working" config file.

 3) "make ARCH=arm oldconfig" in the  output/build/linux-2.6.30.2
    directory

That doesn't feel like the proper way to do it, but it seems to
have worked. 

-- 
Grant Edwards                   grante             Yow! Zippy's brain cells
                                  at               are straining to bridge
                               visi.com            synapses ...

  reply	other threads:[~2009-11-23 20:01 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
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 [this message]
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='heepmc$umt$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.