u-boot.git/Kconfig, branch v2016.05

Kconfig: Simple aesthetic/grammar fixes to top-level Kconfig

2016-04-18T21:11:51+00:00

Signed-off-by: Robert P. J. Day

spl: Add an option to load a FIT containing U-Boot

2016-03-14T23:18:30+00:00

This provides a way to load a FIT containing U-Boot and a selection of device
tree files. The board can select the correct device tree by probing the
hardware. Then U-Boot is started with the selected device tree.

Signed-off-by: Simon Glass

Kconfig: Move CONFIG_FIT and related options to Kconfig

2016-03-14T23:18:07+00:00

There are already two FIT options in Kconfig but the CONFIG options are
still in the header files. We need to do a proper move to fix this.

Move these options to Kconfig and tidy up board configuration:

   CONFIG_FIT
   CONFIG_OF_BOARD_SETUP
   CONFIG_OF_SYSTEM_SETUP
   CONFIG_FIT_SIGNATURE
   CONFIG_FIT_BEST_MATCH
   CONFIG_FIT_VERBOSE
   CONFIG_OF_STDOUT_VIA_ALIAS
   CONFIG_RSA

Unfortunately the first one is a little complicated. We need to make sure
this option is not enabled in SPL by this change. Also this option is
enabled automatically in the host builds by defining CONFIG_FIT in the
image.h file. To solve this, add a new IMAGE_USE_FIT #define which can
be used in files that are built on the host but must also build for U-Boot
and SPL.

Note: Masahiro's moveconfig.py script is amazing.

Signed-off-by: Simon Glass 
[trini: Add microblaze change, various configs/ re-applies]
Signed-off-by: Tom Rini

Move all command code into its own directory

2016-01-25T15:39:43+00:00

There are a lot of unrelated files in common, including all of the commands.
Moving them into their own directory makes them easier to find and is more
logical.

Some commands include non-command code, such as cmd_scsi.c. This should be
sorted out at some point so that the function can be enabled with or without
the associated command.

Unfortunately, with m68k I get this error:

m68k:  +   M5329AFEE
+arch/m68k/cpu/mcf532x/start.o: In function `_start':
+arch/m68k/cpu/mcf532x/start.S:159:(.text+0x452): relocation truncated to fit: R_68K_PC16 against symbol `board_init_f' defined in .text.board_init_f section in common/built-in.o

I hope someone can shed some light on what this means. I hope it isn't
depending on the position of code in the image.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng 
Reviewed-by: Heiko Schocher 
Acked-by: Stefan Roese 
Acked-by: Przemyslaw Marczak

microblaze: move CONFIG_SYS_TEXT_BASE to defconfig

2016-01-20T15:19:35+00:00

This is how CONFIG options are defined by Kconfig.

Signed-off-by: Masahiro Yamada 
Acked-by: Michal Simek

m68k: move CONFIG_SYS_TEXT_BASE to defconfig files

2016-01-20T15:19:34+00:00

For historical reason, CONFIG_SYS_TEXT_BASE has been specified
in various ways:

[1] by board/${VENDOR}/${BOARD}/config.mk

[2] by CONFIG_SYS_EXTRA_OPTIONS
    (This was "options" field of boards.cfg before Kconfig conversion)

[3] by include/configs/${BOARD}.h

[4] by configs/${BOARD}_defconfig

Most of M68K boards use either [1] or [2], both of which we want to
deprecate.  Switch them into [4], which is the newest way (Kconfig).

We still allow [3] too, because it is still used by many boards and
we expect much time for conversion.

Signed-off-by: Masahiro Yamada 
Acked-by: Angelo Dureghello 
Reviewed-by: Simon Glass

dm: spl: Support device tree when BSS is in a different section

2015-11-04T13:49:52+00:00

At present in SPL we place the device tree immediately after BSS. This
avoids needing to copy it out of the way before BSS can be used. However on
some boards BSS is not placed with the image - e.g. it can be in RAM if
available.

Add an option to tell U-Boot that the device tree should be placed at the
end of the image binary (_image_binary_end) instead of at the end of BSS.

Note: A common reason to place BSS in RAM is to support the FAT filesystem.
We should update the code so that it does not use so much BSS.

Signed-off-by: Simon Glass 
Signed-off-by: Michal Simek

malloc_simple: Add support for switching to DRAM heap

2015-10-20T16:40:27+00:00

malloc_simple uses a part of the stack as heap, initially it uses
SYS_MALLOC_F_LEN bytes which typically is quite small as the initial
stacks sits in SRAM and we do not have that much SRAM to work with.

When DRAM becomes available we may switch the stack from SRAM to DRAM
to give use more room. This commit adds support for also switching to
a new bigger malloc_simple heap located in the new stack.

Note that this requires spl_init to be called before spl_relocate_stack_gd
which in practice means that spl_init must be called from board_init_f.

Signed-off-by: Hans de Goede 
Reviewed-by: Tom Rini 
Acked-by: Simon Glass

malloc_simple: Add Kconfig option for using only malloc_simple in the SPL

2015-10-20T16:40:27+00:00

common/dlmalloc.c is quite big, both in .text and .data usage, therefor
on some boards the SPL is build to use only malloc_simple.c and not the
dlmalloc.c code. This is done in various include/configs/foo.h with the
following construct:

 #ifdef CONFIG_SPL_BUILD
 #define CONFIG_SYS_MALLOC_SIMPLE
 #endif

This commit introduces a SPL_MALLOC_SIMPLE Kconfig bool which allows
selecting this functionality through Kconfig instead.

Signed-off-by: Hans de Goede 
Acked-by: Simon Glass

Kconfig: fix typo in CONFIG_FIT description

2015-09-28T14:15:47+00:00

Fix typo in CONFIG_FIT description - remove the accidentially added
redundand 'the'.

Signed-off-by: Igor Grinberg 
Cc: Masahiro Yamada 
Cc: Simon Glass 
Reviewed-by: Simon Glass