This project is mirrored from git:// The repository failed to update .
Repository mirroring has been paused due to too many failed attempts, and can be resumed by a project maintainer.
Last successful update .
  1. 25 Nov, 2017 1 commit
  2. 16 Oct, 2017 1 commit
  3. 06 Oct, 2017 1 commit
  4. 15 Sep, 2017 1 commit
  5. 12 Sep, 2017 1 commit
  6. 16 Aug, 2017 2 commits
  7. 10 Jul, 2017 2 commits
  8. 10 Jun, 2017 1 commit
  9. 22 May, 2017 2 commits
    • Tom Rini's avatar
      lib: move hash CONFIG options to Kconfig · 089df18b
      Tom Rini authored
      Commit 94e3c8c4 ("crypto/fsl - Add progressive hashing support
      using hardware acceleration.") created entries for CONFIG_SHA1,
      However, no defconfig has migrated to it.  Complete the move by first
      adding additional logic to various Kconfig files to select this when
      required and then use the moveconfig tool.  In many cases we can select
      these because they are required to implement other drivers.  We also
      correct how we include the various hashing algorithms in SPL.
      This commit was generated as follows (after Kconfig additions):
      [1] tools/ -y SHA1 SHA256 SHA_HW_ACCEL
      [2] tools/ -y SHA_PROG_HW_ACCEL
      We cannot move SHA_HW_ACCEL and SHA_PROG_HW_ACCEL simultaneously
      because there is dependency between them.
      Cc: Poonam Aggrwal <>
      Cc: Naveen Burmi <>
      Cc: Po Liu <>
      Cc: Shengzhou Liu <>
      Cc: Priyanka Jain <>
      Cc: Shaohui Xie <>
      Cc: Chunhe Lan <>
      Cc: Chander Kashyap <>
      Cc: Steve Rae <>
      Cc: Dirk Eibach <>
      Cc: Feng Li <>
      Cc: Alison Wang <>
      Cc: Sumit Garg <>
      Cc: Mingkai Hu <>
      Cc: York Sun <>
      Cc: Prabhakar Kushwaha <>
      Cc: Jaehoon Chung <>
      Cc: Akshay Saraswat <>
      Cc: Heiko Schocher <>
      Cc: Jagan Teki <>
      Signed-off-by: Tom Rini's avatarTom Rini <>
      Reviewed-by: default avatarSimon Glass <>
      Signed-off-by: Tom Rini's avatarTom Rini <>
    • Tom Rini's avatar
      FIT: Rename FIT_DISABLE_SHA256 to FIT_ENABLE_SHA256_SUPPORT · 0db7f685
      Tom Rini authored
      is enabled by default and now a positive option.  Convert the handful of boards
      that were disabling it before to save space.
      Cc: Dirk Eibach <>
      Cc: Lukasz Dalek <>
      Signed-off-by: Tom Rini's avatarTom Rini <>
      Reviewed-by: default avatarSimon Glass <>
      Reviewed-by: default avatarSimon Glass <>
  10. 09 Apr, 2017 1 commit
  11. 17 Mar, 2017 1 commit
  12. 20 Jan, 2017 1 commit
    • Rick Altherr's avatar
      bootm: relocate ramdisk if CONFIG_SYS_BOOT_RAMDISK_HIGH set · c2e7e72b
      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 <>
      Reviewed-by: default avatarSimon Glass <>
      Reviewed-by: Joel Stanley's avatarJoel Stanley <>
  13. 14 Jan, 2017 1 commit
  14. 13 Jan, 2017 1 commit
  15. 02 Jan, 2017 1 commit
  16. 03 Dec, 2016 2 commits
  17. 21 Nov, 2016 4 commits
  18. 06 Oct, 2016 1 commit
  19. 15 Aug, 2016 1 commit
  20. 21 Jul, 2016 1 commit
    • Masahiro Yamada's avatar
      image: fix IH_ARCH_... values for uImage compatibility · ff87b081
      Masahiro Yamada authored
      Commit 555f45d8 ("image: Convert the IH_... values to enums")
      accidentally changed some IH_ARCH_... values.
      Prior to that commit, there existed a gap between IH_ARCH_M68K and
      IH_ARCH_MICROBLAZE, like follows.
        #define IH_ARCH_SPARC64         11      /* Sparc 64 Bit */
        #define IH_ARCH_M68K            12      /* M68K         */
        #define IH_ARCH_MICROBLAZE      14      /* MicroBlaze   */
        #define IH_ARCH_NIOS2           15      /* Nios-II      */
      The enum conversion broke the compatibility with existing uImage
      files.  Reverting 555f45d8 will cause build error unfortunately,
      so here is a more easy fix.
      I dug the git history and figured out the gap was introduced by
      commit 1117cbf2 ("nios: remove nios-32 arch").  So, I revived
      IH_ARCH_NIOS just for filling the gap.
      I added comments to each enum block.  Once we assign a value to
      IH_... it is not allowed to change it.
      Acked-by: default avatarMichal Simek <>
      Signed-off-by: default avatarMasahiro Yamada <>
      Reviewed-by: default avatarSimon Glass <>
  21. 14 Jul, 2016 4 commits
  22. 24 Jun, 2016 1 commit
  23. 31 May, 2016 1 commit
    • Masahiro Yamada's avatar
      Revert "image.h: Tighten up content using handy CONFIG_IS_ENABLED() macro." · 6f41751f
      Masahiro Yamada authored
      This reverts commit 56adbb38.
      Since commit 56adbb38 ("image.h: Tighten up content using handy
      CONFIG_IS_ENABLED() macro."), I found my boards fail to boot Linux
      because the commit changed the logic of macros it touched.  Now,
      the boards.
      As you can see in include/linux/kconfig.h, CONFIG_IS_ENABLE() (and
      IS_ENABLED() as well) can only take a macro that is either defined
      as 1 or undefined.  This is met for boolean options defined in
      Kconfig.  On the other hand, CONFIG_SYS_BOOT_RAMDISK_HIGH and
      CONFIG_SYS_BOOT_GET_CMDLINE are defined without any value in
      arch/*/include/asm/config.h .  This kind of clean-up is welcome,
      but the options should be moved to Kconfig beforehand.
      Moreover, CONFIG_IS_ENABLED(SPL_CRC32_SUPPORT) looks weird.
      It should be either CONFIG_IS_ENABLED(CRC32_SUPPORT) or
      IS_ENABLED(CONFIG_SPL_CRC32_SUPPORT).  But, I see no define for
      CONFIG_SPL_CRC32_SUPPORT anywhere.  Likewise for the other three.
      also changed for SPL.  This can be a problem for boards defining
      CONFIG_SPL_OF_LIBFDT.  I guess it should have been changed to
      In the first place, if we replace the references in C code,
      the macros IMAGE_* will go away.
      Signed-off-by: default avatarMasahiro Yamada <>
  24. 27 May, 2016 1 commit
  25. 24 May, 2016 3 commits
  26. 14 Mar, 2016 3 commits