Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Differences in kernel configuration
Date: Fri, 21 Mar 2008 11:34:30 +0100	[thread overview]
Message-ID: <20080321103430.GA10140@mx.loc> (raw)
In-Reply-To: <01b801c88b3c$b94aba00$ad289e86@LPSC0173W>

On Fri, Mar 21, 2008 at 11:17:02AM +0100, Guillaume Dargaud wrote:
>Hello all,
>
>How come I don't get the same options if I do this from the buildroot 
>directory:
>make ARCH=ppc menuconfig
>(with the [Kernel][Run make ARCH=$(ARCH) xconfig before build] activated)
>
>And this:
>cd ./project_build_ppc/genepy/linux-2.6.24; make ARCH=ppc xconfig
>
>In particular, in the 2nd case I have an option for [Processor][IBM 4xx 
>options][Machine type]  available for Xilinx-ML403 which is missing in the 
>first case
>
>linux-2.6.24 $ grep XIL .config
># CONFIG_XILINX_ML300 is not set
>CONFIG_XILINX_ML403=y
>CONFIG_XILINX_VIRTEX_4_FX=y
>CONFIG_XILINX_VIRTEX=y
># CONFIG_XILINX_SYSACE is not set
>
>buildroot $ grep XIL project_build_ppc/genepy/linux-2.6.24/.config
>CONFIG_XILINX_VIRTEX_GENERIC_BOARD=y
>CONFIG_XILINX_VIRTEX=y
>CONFIG_XILINX_VIRTEX_II_PRO=y
>CONFIG_XILINX_VIRTEX_4_FX=y
># CONFIG_XILINX_SYSACE is not set
>
>
>I've also heard that there can be discrepancies between using xconfig and 
>menuconfig, so is it possible to tell the main 'make' to use the kernel's 

xconfig and menuconfig should result in the same .config, IIRC.

Apart from that you want to read
docs/README
for the reliable way to configure your kernel.

HTH,

  reply	other threads:[~2008-03-21 10:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 10:17 [Buildroot] Differences in kernel configuration Guillaume Dargaud
2008-03-21 10:34 ` Bernhard Fischer [this message]
2008-03-21 14:47   ` [Buildroot] Wrong compiling commands ? Guillaume Dargaud

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=20080321103430.GA10140@mx.loc \
    --to=rep.dot.nop@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox