1. 18 Apr, 2016 1 commit
  2. 14 Mar, 2016 2 commits
    • Simon Glass's avatar
      spl: Add an option to load a FIT containing U-Boot · f1dcee59
      Simon Glass authored
      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: default avatarSimon Glass <sjg@chromium.org>
      f1dcee59
    • Simon Glass's avatar
      Kconfig: Move CONFIG_FIT and related options to Kconfig · 73223f0e
      Simon Glass authored
      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: default avatarSimon Glass <sjg@chromium.org>
      [trini: Add microblaze change, various configs/ re-applies]
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      73223f0e
  3. 25 Jan, 2016 1 commit
    • Simon Glass's avatar
      Move all command code into its own directory · 72a8cf8d
      Simon Glass authored
      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: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarBin Meng <bmeng.cn@gmail.com>
      Reviewed-by: default avatarHeiko Schocher <hs@denx.de>
      Acked-by: default avatarStefan Roese <sr@denx.de>
      Acked-by: default avatarPrzemyslaw Marczak <p.marczak@samsung.com>
      72a8cf8d
  4. 20 Jan, 2016 2 commits
  5. 04 Nov, 2015 1 commit
    • Simon Glass's avatar
      dm: spl: Support device tree when BSS is in a different section · 10172962
      Simon Glass authored
      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: default avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      10172962
  6. 20 Oct, 2015 2 commits
  7. 28 Sep, 2015 1 commit
  8. 05 Aug, 2015 1 commit
  9. 28 Jul, 2015 1 commit
  10. 30 May, 2015 1 commit
  11. 30 Apr, 2015 1 commit
  12. 29 Mar, 2015 1 commit
  13. 28 Mar, 2015 1 commit
  14. 09 Mar, 2015 1 commit
    • Przemyslaw Marczak's avatar
      dlmalloc: do memset in malloc init as new default config · 0aa8a4ad
      Przemyslaw Marczak authored
      This commit introduces new config: CONFIG_SYS_MALLOC_CLEAR_ON_INIT.
      
      This config is an expert option and is enabled by default.
      
      The all amount of memory reserved for the malloc, is by default set
      to zero in mem_malloc_init(). When the malloc reserved memory exceeds
      few MiB, then the boot process can slow down.
      
      So disabling this config, is an expert option to reduce the boot time,
      and can be disabled by Kconfig.
      
      Note:
      After disable this option, only calloc() will return the pointer
      to the zeroed memory area. Previously, without this option,
      the memory pointed to untouched malloc memory region, was filled
      with zeros. So it means, that code with malloc() calls should
      be reexamined.
      Signed-off-by: default avatarPrzemyslaw Marczak <p.marczak@samsung.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      0aa8a4ad
  15. 04 Mar, 2015 1 commit
  16. 25 Feb, 2015 1 commit
  17. 24 Feb, 2015 3 commits
    • Masahiro Yamada's avatar
      kconfig: remove unneeded dependency on !SPL_BUILD · d648964f
      Masahiro Yamada authored
      Now CONFIG_SPL_BUILD is not defined in Kconfig, so
      "!depends on SPL_BUILD" and "if !SPL_BUILD" are redundant.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      d648964f
    • Masahiro Yamada's avatar
      kconfig: switch to single .config configuration · e02ee254
      Masahiro Yamada authored
      When Kconfig for U-boot was examined, one of the biggest issues was
      how to support multiple images (Normal, SPL, TPL).  There were
      actually two options, "single .config" and "multiple .config".
      After some discussions and thought experiments, I chose the latter,
      i.e. to create ".config", "spl/.config", "tpl/.config" for Normal,
      SPL, TPL, respectively.
      
      It is true that the "multiple .config" strategy provided us the
      maximum flexibility and helped to avoid duplicating CONFIGs among
      Normal, SPL, TPL, but I have noticed some fatal problems:
      
      [1] It is impossible to share CONFIG options across the images.
        If you change the configuration of Main image, you often have to
        adjust some SPL configurations correspondingly.  Currently, we
        cannot handle the dependencies between them.  It means one of the
        biggest advantages of Kconfig is lost.
      
      [2] It is too painful to change both ".config" and "spl/.config".
        Sunxi guys started to work around this problem by creating a new
        configuration target.  Commit cbdd9a97 (sunxi: kconfig: Add
        %_felconfig rule to enable FEL build of sunxi platforms.) added
        "make *_felconfig" to enable CONFIG_SPL_FEL on both images.
        Changing the configuration of multiple images in one command is a
        generic demand.  The current implementation cannot propose any
        good solution about this.
      
      [3] Kconfig files are getting ugly and difficult to understand.
        Commit b724bd7d (dm: Kconfig: Move CONFIG_SYS_MALLOC_F_LEN to
        Kconfig) has sprinkled "if !SPL_BUILD" over the Kconfig files.
      
      [4] The build system got more complicated than it should be.
        To adjust Linux-originated Kconfig to U-Boot, the helper script
        "scripts/multiconfig.sh" was introduced.  Writing a complicated
        text processor is a shell script sometimes caused problems.
      
      Now I believe the "single .config" will serve us better.  With it,
      all the problems above would go away.  Instead, we will have to add
      some CONFIG_SPL_* (and CONFIG_TPL_*) options such as CONFIG_SPL_DM,
      but we will not have much.  Anyway, this is what we do now in
      scripts/Makefile.spl.
      
      I admit my mistake with my apology and this commit switches to the
      single .config configuration.
      
      It is not so difficult to do that:
      
       - Remove unnecessary processings from scripts/multiconfig.sh
        This file will remain for a while to support the current defconfig
        format.  It will be removed after more cleanups are done.
      
       - Adjust some makefiles and Kconfigs
      
       - Add some entries to include/config_uncmd_spl.h and the new file
         scripts/Makefile.uncmd_spl.  Some CONFIG options that are not
         supported on SPL must be disabled because one .config is shared
         between SPL and U-Boot proper going forward.  I know this is not
         a beautiful solution and I think we can do better, but let's see
         how much we will have to describe them.
      
       - update doc/README.kconfig
      
      More cleaning up patches will follow this.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      e02ee254
    • Simon Glass's avatar
      kconfig: Adjust ordering so that defaults work as expected · 66afaef2
      Simon Glass authored
      At present defaults in arch-specific Kconfig files are ignored if the
      top-level item comes ahead of it in include order. This means that it is
      not possible to have a U-Boot default that architectures and boards can
      override. This does not seem very useful.
      
      Move the include earlier to support this.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Reported-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Reviewed-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      66afaef2
  18. 12 Feb, 2015 3 commits
  19. 09 Feb, 2015 1 commit
  20. 30 Jan, 2015 1 commit
  21. 14 Jan, 2015 1 commit
    • Alexey Brodkin's avatar
      Kconfig: move CONFIG_SYS_CLK_FREQ to Kconfig · 33d88183
      Alexey Brodkin authored
      It makes sense to specify CONFIG_SYS_CLK_FREQ in "configs/xx_defconfig"
      instead of "include/configs/xxx.h" because then header will be reusable
      across boards with different CPU clocks.
      
      Also this nice to have an ability for end user to tune this value
      himself via "menuconfig".
      
      For now I'm only applying this change to all ARC configs because
      otherwise scope of change will be huge.
      Signed-off-by: default avatarAlexey Brodkin <abrodkin@synopsys.com>
      Cc: Tom Rini <trini@ti.com>
      Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Hans de Goede <hdegoede@redhat.com>
      cc: Simon Glass <sjg@chromium.org>
      Reviewed-by: default avatarTom Rini <trini@ti.com>
      33d88183
  22. 07 Jan, 2015 1 commit
  23. 24 Nov, 2014 1 commit
  24. 23 Nov, 2014 1 commit
  25. 04 Nov, 2014 1 commit
  26. 27 Oct, 2014 2 commits
  27. 25 Sep, 2014 1 commit
  28. 24 Sep, 2014 1 commit
  29. 28 Aug, 2014 2 commits
  30. 21 Aug, 2014 1 commit
  31. 30 Jul, 2014 1 commit