[U-Boot] Using old Config Style

[Hannes Schmelzer]

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