1. 07 7月, 2016 1 次提交
  2. 04 5月, 2016 1 次提交
  3. 26 4月, 2016 2 次提交
  4. 15 3月, 2016 2 次提交
    • S
      Kconfig: Move CONFIG_FIT and related options to Kconfig · 73223f0e
      Simon Glass 提交于
      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: NSimon Glass <sjg@chromium.org>
      [trini: Add microblaze change, various configs/ re-applies]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      73223f0e
    • S
      Move CONFIG_OF_LIBFDT to Kconfig · 69e173eb
      Simon Glass 提交于
      Move this option to Kconfig and tidy up existing boards.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      69e173eb
  5. 25 11月, 2015 2 次提交
  6. 22 11月, 2015 1 次提交
  7. 19 11月, 2015 1 次提交
    • V
      km: update the boot script to check for a DTB · c6d32dfd
      Valentin Longchamp 提交于
      If a DTB is found with cramfsls, the bootscript continues as expected.
      If none is found, the cramfsloadfdt and boot subbootcmds are updated to
      not load the DTB from cramfs and not pass it to the kernel. The kernel
      thus must have an appended DTB otherwise the boot will fail.
      
      This is required for the km_kirkwood boards that must support .esw where
      the DTB sometimes is appended (for backwards compatibility) and sometimes
      is passed correctly (as we do now for all newer boards).
      Signed-off-by: NValentin Longchamp <valentin.longchamp@keymile.com>
      Reviewed-by: NHeiko Schocher <hs@denx.de>
      c6d32dfd
  8. 25 10月, 2015 1 次提交
  9. 22 8月, 2015 1 次提交
  10. 26 6月, 2015 2 次提交
  11. 01 6月, 2015 1 次提交
  12. 31 3月, 2015 1 次提交
  13. 16 12月, 2014 1 次提交
  14. 15 11月, 2014 2 次提交
  15. 02 8月, 2014 1 次提交
  16. 13 5月, 2014 3 次提交
  17. 23 4月, 2014 1 次提交
  18. 13 3月, 2014 1 次提交
  19. 13 2月, 2014 1 次提交
    • G
      arm/km: define fdt_high env variable and allow backwards compatibility · b1c2a7ae
      Gerlando Falauto 提交于
      Add set_fdthigh subcommand to "subbootcmds" (release) so to set "fdt_high"
      This is necessary on Kirkwood so that the FDT does not get relocated
      above the memory limit that the kernel cannot access
      (that is the memory part reserved for the switch).
      This was tested on NUSA1, where it is necessary, and on ETER1, where it
      doesn't seem to hurt.
      
      We want the scripts to also work with older versions of u-boot, where:
      a) set_fdthigh is not defined (will be default env for newer u-boots)
      b) the fdt will not be available
      
      For this reason, we use "set_fdthigh" to tell whether we are running
      a newer (FDT-aware) u-boot or not.
      So if "set_fdthigh" runs successfully or arch != arm we try loading
      the fdt; otherwise we proceed normally.
      
      Notice how, contrary to release mode, set_fdthigh will _not_ be part of
      subbootcmds for develop and ramfs, but will be executed as part of
      "tftpfdt".
      
      Since this is only needed for kirkwood cards, and it prevents the kernel
      from booting on QorIQ (though it seemed to work on ETER1), we change
      its definition in the default env for powerpc so that the value is only
      set on ARM.
      Signed-off-by: NValentin Longchamp <valentin.longchamp@keymile.com>
      Signed-off-by: NGerlando Falauto <gerlando.falauto@keymile.com>
      Signed-off-by: NHolger Brunck <holger.brunck@keymile.com>
      Acked-by: NValentin Longchamp <valentin.longchamp@keymile.com>
      b1c2a7ae
  20. 04 2月, 2014 4 次提交
  21. 25 1月, 2014 1 次提交
  22. 22 1月, 2014 1 次提交
  23. 13 12月, 2013 1 次提交
  24. 26 11月, 2013 1 次提交
  25. 25 10月, 2013 1 次提交
    • V
      mpc85xx: introduce the kmp204x reference design support · 877bfe37
      Valentin Longchamp 提交于
      This patch introduces the support for Keymile's kmp204x reference
      design. This design is based on Freescale's P2040/P2041 SoC.
      
      The peripherals used by this design are:
      - DDR3 RAM with SPD support
      - SPI NOR Flash as boot medium
      - NAND Flash
      - 2 PCIe busses (hosts 1 and 3)
      - 3 FMAN Ethernet devices (FMAN1 DTSEC1/2/5)
      - 3 Local Bus windows, with one dedicated to the QRIO reset/power mgmt
        FPGA
      - 2 HW I2C busses
      - last but not least, the mandatory serial port
      
      The board/keymile/kmp204x code is mostly based on Freescale's P2041rdb
      support and was changed according to our design (that means essentially
      removing what is not present on the designs and a few adaptations).
      
      There is currently only one prototype board that is based on this design
      and this patch also introduces it. The board is called kmlion1.
      Signed-off-by: NStefan Bigler <stefan.bigler@keymile.com>
      Signed-off-by: NValentin Longchamp <valentin.longchamp@keymile.com>
      
      kmp204x: update the ENV #define
      
      The comments had to be refined as well as the total size
      Signed-off-by: NValentin Longchamp <valentin.longchamp@keymile.com>
      [York Sun: fix ddr.c]
      Acked-by: NYork Sun <yorksun@freescale.com>
      877bfe37