All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Schmelzer <hannes@schmelzer.or.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] Using old Config Style
Date: Thu, 11 Feb 2016 11:18:20 +0100	[thread overview]
Message-ID: <56BC5FEC.2000501@schmelzer.or.at> (raw)
In-Reply-To: <F50CAB352C149543A6F2FFE37D4B593492215B82@S1.mackware.local>



On 11.02.2016 09:55, Mario Albrecht wrote:
> Hallo Hannes,
>
> how can I define commands in defconfig file which should be used or not used?
>
> Regards Mario
>
> -----Urspr?ngliche Nachricht-----
> Von: Hannes Schmelzer [mailto:hannes at schmelzer.or.at]
> Gesendet: Mittwoch, 10. Februar 2016 19:01
> An: Mario Albrecht
> Betreff: Re: [U-Boot] Using old Config Style
>
>
> On 2016-02-10 17:02, Mario Albrecht wrote:
>> Hi,
>>
>> i have a small question about using old board specific config files.
>> I have a config file for a board which contains all needed commands
>> defined by #define CONFIG_CMD_ and #undef CONFIG_CMD_.
>> In new u-boot Version a autoconf.h file is generated which conflicts
>> the defines in the board.h file. How can I disable autoconf.h
>> generation or get the right commands in this file.
>>
>> Regards Mario
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>>
> hi Mario,
>
> the much better approach would be converting your board to Kconfig.
> you can create some xxxboard_defconfig in configs/ were all your needed commands are checked.
>
> regards,
> Hannes
hi mario,

have a look for example in configs/tseries_mmc_defconfig.

Basically some commands are defined through Kconfig as 'default on' 
other with 'default off'.

# CONFIG_CMD_FPGA is not set
CONFIG_CMD_GPIO=y

in this example the CMD_FPGA is default on and set through my defconfig 
to OFF.
At the other hand CMD_GPIO is per default off and set through defconfig 
to ON.

To generate some xxx_defconfig file you may config your u-boot simply 
with "make menuconfig" and afterwards "make savedefconfig".
This will generate a "defconfig" File in your build-output folder, from 
there you can merge this with your xxx_defconfig file.

regards,
Hannes

      parent reply	other threads:[~2016-02-11 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 16:02 [U-Boot] Using old Config Style Mario Albrecht
     [not found] ` <56BB7ADE.7090304@schmelzer.or.at>
     [not found]   ` <F50CAB352C149543A6F2FFE37D4B593492215B82@S1.mackware.local>
2016-02-11 10:18     ` Hannes Schmelzer [this message]

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=56BC5FEC.2000501@schmelzer.or.at \
    --to=hannes@schmelzer.or.at \
    --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.