1. 08 Feb, 2017 2 commits
    • Emmanuel Vadot's avatar
      kconfig: Add API kconfig file · 4db98d3d
      Emmanuel Vadot authored
      Add kconfig file to enable API support
      Signed-off-by: default avatarEmmanuel Vadot <manu@bidouilliste.com>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
    • Masahiro Yamada's avatar
      cmd: add a new command "config" to show .config contents · 61304dbe
      Masahiro Yamada authored
      This feature is inspired by /proc/config.gz of Linux.  In Linux,
      if CONFIG_IKCONFIG is enabled, the ".config" file contents are
      embedded in the kernel image.  If CONFIG_IKCONFIG_PROC is also
      enabled, the ".config" contents are exposed to /proc/config.gz.
      Users can do "zcat /proc/config.gz" to check which config options
      are enabled on the running kernel image.
      The idea is almost the same here; if CONFIG_CMD_CONFIG is enabled,
      the ".config" contents are compressed and saved in the U-Boot image,
      then printed by the new command "config".
      The usage is quite simple.  Enable CONFIG_CMD_CONFIG, then run
       > config
      from the command line interface.  The ".config" contents will be
      printed on the console.
      This feature increases the U-Boot image size by about 4KB (this is
      mostly due to the gzip-compressed .config file).  By default, it is
      enabled only for Sandbox because we do not care about the memory
      footprint on it.  Of course, this feature is architecture agnostic,
      so you can enable it on any board if the image size increase is
      acceptable for you.
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
  2. 28 Jan, 2017 2 commits
  3. 20 Jan, 2017 1 commit
  4. 14 Jan, 2017 1 commit
  5. 12 Jan, 2017 1 commit
  6. 10 Jan, 2017 1 commit
  7. 03 Dec, 2016 3 commits
    • Yann E. MORIN's avatar
      cmd: move CMD_PXE to Kconfig · bfb380b3
      Yann E. MORIN authored
      Currently, CMD_PXE is forcibly enabled in config_distro_defaults.h, so
      that general purpose distributions can rely on it being defined. This
      header is included, under conditions or not, by various archs or
      famillies of archs / SoCs.
      However, it is very possible that boards based on those SoCs will not
      have a physical ethernet connector at all, even if the have a MAC; for
      example, the Nanopi Neo AIR (sunxi H3) does not. It is also possible
      that network booting is absolutely not necessary for a device.
      However, it is not possible to disable the PXE command, as it is
      forcibly enabled and is non-configurable.
      But it turns out we already have a config option to build a distro-ready
      image, in the name of DISTRO_DEFAULTS.
      Move CMD_PXE out of the hard-coded config_distro_defaults.h into a
      Kconfig option, that gets selected by DISTRO_DEFAULTS when it is set.
      Signed-off-by: default avatar"Yann E. MORIN" <yann.morin.1998@free.fr>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
      [trini: Make it select MENU, run moveconfig.py]
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
    • Tom Rini's avatar
      Enable DISTRO_DEFAULT on platforms that missed it before · 3337e3af
      Tom Rini authored
      A number of platforms had been using the distro default feature before
      it was moved to Kconfig but did not enable the new Kconfig option when
      it was enabled.  This caused a regression in terms of features and this
      introduces breakage when more things move to Kconfig.
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
    • Masahiro Yamada's avatar
      libfdt: replace ARCH_FIXUP_FDT with ARCH_FIXUP_FDT_MEMORY · 63c09417
      Masahiro Yamada authored
      Commit e2f88dfd ("libfdt: Introduce new ARCH_FIXUP_FDT option")
      allows us to skip memory setup of DTB, but a problem for ARM is that
      spin_table_update_dt() and psci_update_dt() are skipped as well if
      CONFIG_ARCH_FIXUP_FDT is disabled.
      This commit allows us to skip only fdt_fixup_memory_banks() instead
      of the whole of arch_fixup_fdt().  It will be useful when we want to
      use a memory node from a kernel DTB as is, but need some fixups for
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Acked-by: default avatarAlexey Brodkin <abrodkin@synopsys.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      Fixed build error for x86:
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
  8. 29 Nov, 2016 1 commit
  9. 17 Nov, 2016 1 commit
    • Alexander Graf's avatar
      ls2080ardb: Convert to distro boot · b99ebaf9
      Alexander Graf authored
      Most new systems in U-Boot these days make use of the generic "distro"
      framework which allows a user to have U-Boot scan for a bootable OS
      on all available media types.
      This patch extends the LS2080ARDB board to use that framework if the
      hard coded NOR flash location does not contain a bootable image.
      Signed-off-by: default avatarAlexander Graf <agraf@suse.de>
  10. 27 Sep, 2016 1 commit
    • B, Ravi's avatar
      spl: dfu: add dfu support in SPL · bc5dbcb9
      B, Ravi authored
      Traditionally the DFU support is available only
      as part 2nd stage boot loader(u-boot) and DFU
      is not supported in SPL.
      The SPL-DFU feature is useful for boards which
      does not have MMC/SD, ethernet boot mechanism
      to boot the board and only has USB inteface.
      This patch add DFU support in SPL with RAM
      memory device support to load and execute u-boot.
      And then leverage full functionality DFU in
      u-boot to flash boot inital binary images to
      factory or bare-metal boards to memory devices
      like SPI, eMMC, MMC/SD card using USB interface.
      This SPL-DFU support can be enabled through
      Menuconfig->Boot Images->Enable SPL-DFU support
      Signed-off-by: default avatarRavi Babu <ravibabu@ti.com>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
  11. 19 Sep, 2016 1 commit
  12. 16 Sep, 2016 1 commit
  13. 07 Sep, 2016 1 commit
  14. 20 Aug, 2016 2 commits
  15. 12 Aug, 2016 1 commit
    • Andreas Dannenberg's avatar
      common: image: Add support for post-processing of images · eba3fbd6
      Andreas Dannenberg authored
      This commit allows injecting a board/platform/device-specific post-
      processing function into the FIT image data loading process, which can
      include modifying the size and altering the starting source address of
      an image data artifact. This might be desired to do things like strip
      headers or footers attached to the images before they were packaged into
      the FIT, or to perform operations such as decryption or authentication.
      Introduce new configuration option CONFIG_FIT_IMAGE_POST_PROCESS to
      allow controlling this feature. If enabled, a platform-specific post-
      process function must be provided.
      Signed-off-by: default avatarAndreas Dannenberg <dannenberg@ti.com>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
  16. 05 Aug, 2016 1 commit
    • Masahiro Yamada's avatar
      treewide: move CONFIG_PHYS_64BIT to Kconfig · bb6b142f
      Masahiro Yamada authored
      We need to ensure that CONFIG_PHYS_64BIT is configured via Kconfig so
      that it is always available to the build system.  Otherwise we can run
      into cases where we have inconsistent sizes of certain attributes.
      Ravi Babu reported offset mismatch of struct dwc3 across files since
      commit 95ebc253 ("types.h: move and redefine resource_size_t").
      Since the commit, resource_addr_t points to phys_addr_t, whose size
      is dependent on CONFIG_PHYS_64BIT for ARM architecture.
      I tried my best to use "select" where possible (for example, ARMv8
      architecture) because I think this kind of option is generally user-
      unconfigurable.  However, I see some of PowerPC boards have 36BIT
      defconfigs as well as 32BIT ones.  I moved CONFIG_PHYS_64BIT to the
      defconfigs for such boards.
      CONFIG_36BIT is no longer referenced, so all of the defines were
      removed from CONFIG_SYS_EXTRA_OPTIONS.
      Fixes: 95ebc253 ("types.h: move and redefine resource_size_t")
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reported-by: default avatarRavi Babu <ravibabu@ti.com>
      Acked-by: default avatarStefan Roese <sr@denx.de>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      Reviewed-by: default avatarYork Sun <york.sun@nxp.com>
  17. 01 Aug, 2016 1 commit
  18. 14 Jul, 2016 2 commits
  19. 21 Jun, 2016 1 commit
    • Hans de Goede's avatar
      Kconfig: Add a new DISTRO_DEFAULTS Kconfig option · 9f823615
      Hans de Goede authored
      DISTRO_DEFAULTS is intended to mirror / replace
      The intend is for boards which include this file to select this from
      their Kconfig files and when moving setting to Kconfig which are #define-ed
      in config_distro_defaults.h to select this from DISTRO_DEFAULTS so that
      boards which have selected DISTRO_DEFAULTS will keep the same configuration
      as before without needing any defconfig file changes.
      The initial list of selected things matches all settings recently removed
      from config_distro_defaults.h because they have been converted to Kconfig,
      with the exception of CMD_ELF and CMD_NET, which have a default of y, if
      the default of these ever changes they should be selected by DISTRO_DEFAULTS
      For testing and example purposes this commit also converts ARCH_SUNXI
      to use DISTRO_DEFAULT instead of selecting everything it needs itself.
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
  20. 12 Jun, 2016 1 commit
  21. 25 May, 2016 1 commit
  22. 18 Apr, 2016 1 commit
  23. 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>
    • 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:
      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>
  24. 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
      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>
  25. 20 Jan, 2016 2 commits
  26. 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
      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>
  27. 20 Oct, 2015 2 commits
  28. 28 Sep, 2015 1 commit
  29. 05 Aug, 2015 1 commit
  30. 28 Jul, 2015 1 commit
  31. 30 May, 2015 1 commit