All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Quick guide to Kconfig
Date: Thu, 31 Jul 2014 16:38:47 +0200	[thread overview]
Message-ID: <53DA54F7.3010202@redhat.com> (raw)
In-Reply-To: <20140731135125.5D2B.AA925319@jp.panasonic.com>

Hi,

On 07/31/2014 06:51 AM, Masahiro Yamada wrote:
> Hi all,
> 
> 
> 
> The mainline has switched to Kconfig.
> 
> Please make sure to use "make <board>_defconfig"
> instead of "make <board>_config".
> 
> 
> 
> [1] Board Configuration
> 
>      make  <board_name>_defconfig
> 
> 
> 
> [2] Modify configuration
> 
> 
>  make config,  make menuconfig,  make nconfig, ... etc.
> 
> 
>  For SPL,
>    make spl/config,  make spl/menuconfig,  make spl/nconfig, ... etc.

I'm a bit confused here, a single "make" will build both the SPL +
the regular u-boot binary, so why 2 separate menuconfig commands for them ?

To be a bit more specific, currently for sunxi for some boards
(the ones most used by devs) we have both Foo_defconfig and Foo_FEL_defconfig
with the latter one being identical to the first one, except that it not only
defines SPL (all our builds use SPL) but also SPL_FEL, this changes some
compile time settings as well as leads to using a different linker script
for the SPL. The end result is a SPL binary which can be loaded through the
"FEL" allwinner usb firmware loading / update mechanism, rather then written
to a sdcard as our regular builds.

Rather then doubling the amount of defconfigs we have to allow using FEL
on any sunxi board, I would like to remove the Foo_FEL_defconfig files
and make it possible to do a FEL build by doing something like this:

make Foo_defconfig
make menuconfig
<select FEL>
make

I was planning on taking a shot at this, but the different make menuconfig
and make spl/menuconfigs have me somewhat confused (I've a decent knowledge of
Kconfig from my kernel work).

Perhaps you can give me some hints on how I can best implement the above ?

Thanks & Regards,

Hans

  parent reply	other threads:[~2014-07-31 14:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31  4:51 [U-Boot] Quick guide to Kconfig Masahiro Yamada
2014-07-31  6:29 ` Frank Ihle
2014-07-31  6:38   ` Masahiro Yamada
2014-07-31  7:17     ` Frank Ihle
2014-07-31 14:38 ` Hans de Goede [this message]
2014-07-31 15:07   ` Ian Campbell
2014-08-01  4:42     ` Masahiro Yamada
2014-08-04 15:49       ` Tom Rini
2014-08-04 15:52         ` Ian Campbell
2014-08-01  4:37   ` Masahiro Yamada
2014-08-04 14:27     ` Tom Rini
2014-08-04 15:35       ` Hans de Goede
2014-08-05  9:26         ` Ian Campbell
2014-08-05  1:01       ` Masahiro Yamada
2014-08-04  7:12 ` Yan, Miao
2014-08-04 10:19   ` Masahiro Yamada
2014-08-04 10:36     ` Yan, Miao
2014-08-04 11:15 ` Simon Glass
2014-08-04 15:50   ` Tom Rini

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=53DA54F7.3010202@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=u-boot@lists.denx.de \
    /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.