1. 03 May, 2019 2 commits
  2. 19 Apr, 2019 2 commits
  3. 05 Apr, 2019 1 commit
  4. 04 Apr, 2019 1 commit
  5. 24 Jul, 2018 4 commits
  6. 12 Jul, 2018 2 commits
  7. 20 Feb, 2018 1 commit
  8. 13 Feb, 2018 3 commits
  9. 20 Oct, 2017 2 commits
  10. 24 Aug, 2017 2 commits
  11. 26 Jun, 2017 3 commits
  12. 26 May, 2017 2 commits
  13. 17 Jan, 2017 1 commit
  14. 16 Jan, 2017 1 commit
  15. 19 Dec, 2016 1 commit
  16. 07 Dec, 2016 3 commits
    • Rick Altherr's avatar
      Enable FIT image support and FDT loading for AST2400/AST2500 · deddff79
      Rick Altherr authored
      FIT is the modern U-Boot native image format for kernels, device trees,
      and ramdisks.  Enabling FIT only compiles in support for the image
      format.  For these devices, the kernel+dtb and ramdisk are loaded from
      separate locations in flash and can be any mix of legacy or FIT images.
      When using FIT images, the dtb is stored as a separate entry that
      requires CONFIG_OF_LIBFDT to load it into RAM and pass it to the kernel.
      
      U-Boot enables EFI support by default but it only builds once FIT
      support is enabled.  EFI support adds ~13k to the binary and is
      currently unused for any Aspeed platforms.  Explicitly disable EFI
      support now that FIT support is enabled.
      
      Tested under qemu with both legacy and FIT kernel+dtb images for
      palmetto and witherspoon.
      Signed-off-by: default avatarRick Altherr <raltherr@google.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarCédric Le Goater <clg@kaod.org>
      Signed-off-by: default avatarJoel Stanley <joel@jms.id.au>
      deddff79
    • Rick Altherr's avatar
      bootm: relocate ramdisk if CONFIG_SYS_BOOT_RAMDISK_HIGH set · 6b26bf14
      Rick Altherr authored
      In 35fc84fa, bootm was refactored so plain 'bootm' and
      'bootm <subcommand>' shared a common implementation.
      The 'bootm ramdisk' command implementation is now part of the common
      implementation but not invoke by plain 'bootm' since the original
      implementation never did ramdisk relocation.  Instead, ramdisk
      relocation happened in image_setup_linux() which is typically called
      during the OS portion of 'bootm'.
      
      On ARM, parameters to the Linux kernel can either be passed by FDT or
      ATAGS. When using FDT, image_setup_linux() is called which also triggers
      ramdisk relocation.  When using ATAGS, image_setup_linux() is _not_
      called because it mostly does FDT setup.
      
      Instead of calling image_setup_linux() in both FDT and ATAGS cases,
      include BOOTM_STATE_RAMDISK in the requested states during a plain
      'bootm' if CONFIG_SYS_BOOT_RAMDISK_HIGH is set and remove the ramdisk
      relocation from image_setup_linux().  This causes ramdisk relocation to
      happen on any system where CONFIG_SYS_BOOT_RAMDISK_HIGH regardless of
      the OS being booted. Also remove IMAGE_ENABLE_RAMDISK_HIGH as it was
      only used by the now-removed code from image_setup_linux().
      Signed-off-by: default avatarRick Altherr <raltherr@google.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarCédric Le Goater <clg@kaod.org>
      Signed-off-by: default avatarJoel Stanley <joel@jms.id.au>
      6b26bf14
    • Cédric Le Goater's avatar
      207efe13
  17. 27 Jul, 2016 8 commits
  18. 11 Jul, 2016 1 commit