1. 27 12月, 2017 1 次提交
  2. 28 11月, 2017 1 次提交
  3. 23 10月, 2017 2 次提交
  4. 21 10月, 2017 1 次提交
  5. 04 9月, 2017 2 次提交
  6. 03 9月, 2017 1 次提交
  7. 30 8月, 2017 1 次提交
  8. 20 8月, 2017 1 次提交
  9. 29 7月, 2017 1 次提交
  10. 26 7月, 2017 2 次提交
    • M
      ARM: uniphier: remove SPL support for ARMv8 SoCs · ee8d037c
      Masahiro Yamada 提交于
      It has been a while since ARM Trusted Firmware supported UniPhier SoC
      family.  U-Boot SPL was intended as a temporary loader that runs in
      secure world.  It is a maintenance headache to support two different
      boot mechanisms.  Secure firmware is realm of ARM Trusted Firmware
      and now U-Boot only serves as a non-secure boot loader for UniPhier
      ARMv8 SoCs.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      ee8d037c
    • S
      Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig · 2be29653
      Simon Glass 提交于
      This converts the following to Kconfig:
         CONFIG_ENV_IS_IN_MMC
         CONFIG_ENV_IS_IN_NAND
         CONFIG_ENV_IS_IN_UBI
         CONFIG_ENV_IS_NOWHERE
      
      In fact this already exists for sunxi as a 'choice' config. However not
      all the choices are available in Kconfig yet so we cannot use that. It
      would lead to more than one option being set.
      
      In addition, one purpose of this series is to allow the environment to be
      stored in more than one place. So the existing choice is converted to a
      normal config allowing each option to be set independently.
      
      There are not many opportunities for Kconfig updates to reduce the size of
      this patch. This was tested with
      
         ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC
      
      And then manual updates.  This is because for CHAIN_OF_TRUST boards they
      can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
      now.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      2be29653
  11. 04 6月, 2017 1 次提交
  12. 22 5月, 2017 1 次提交
  13. 17 5月, 2017 2 次提交
  14. 20 3月, 2017 1 次提交
  15. 23 2月, 2017 1 次提交
  16. 13 2月, 2017 1 次提交
    • M
      flash: complete CONFIG_SYS_NO_FLASH move with renaming · e856bdcf
      Masahiro Yamada 提交于
      We repeated partial moves for CONFIG_SYS_NO_FLASH, but this is
      not completed. Finish this work by the tool.
      
      During this move, let's rename it to CONFIG_MTD_NOR_FLASH.
      Actually, we have more instances of "#ifndef CONFIG_SYS_NO_FLASH"
      than those of "#ifdef CONFIG_SYS_NO_FLASH".  Flipping the logic will
      make the code more readable.  Besides, negative meaning symbols do
      not fit in obj-$(CONFIG_...) style Makefiles.
      
      This commit was created as follows:
      
      [1] Edit "default n" to "default y" in the config entry in
          common/Kconfig.
      
      [2] Run "tools/moveconfig.py -y -r HEAD SYS_NO_FLASH"
      
      [3] Rename the instances in defconfigs by the following:
        find . -path './configs/*_defconfig' | xargs sed -i \
        -e '/CONFIG_SYS_NO_FLASH=y/d' \
        -e 's/# CONFIG_SYS_NO_FLASH is not set/CONFIG_MTD_NOR_FLASH=y/'
      
      [4] Change the conditionals by the following:
        find . -name '*.[ch]' | xargs sed -i \
        -e 's/ifndef CONFIG_SYS_NO_FLASH/ifdef CONFIG_MTD_NOR_FLASH/' \
        -e 's/ifdef CONFIG_SYS_NO_FLASH/ifndef CONFIG_MTD_NOR_FLASH/' \
        -e 's/!defined(CONFIG_SYS_NO_FLASH)/defined(CONFIG_MTD_NOR_FLASH)/' \
        -e 's/defined(CONFIG_SYS_NO_FLASH)/!defined(CONFIG_MTD_NOR_FLASH)/'
      
      [5] Modify the following manually
        - Rename the rest of instances
        - Remove the description from README
        - Create the new Kconfig entry in drivers/mtd/Kconfig
        - Remove the old Kconfig entry from common/Kconfig
        - Remove the garbage comments from include/configs/*.h
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      e856bdcf
  17. 09 2月, 2017 1 次提交
  18. 31 1月, 2017 1 次提交
    • M
      mmc: move CONFIG_GENERIC_MMC to Kconfig · 54925327
      Masahiro Yamada 提交于
      Now, CONFIG_GENERIC_MMC seems equivalent to CONFIG_MMC.
      
      Let's create an entry for "config GENERIC_MMC" with "default MMC",
      then convert all macro defines in headers to Kconfig.  Almost all
      of the defines will go away.
      
      I see only two exceptions:
        configs/blanche_defconfig
        configs/sandbox_noblk_defconfig
      
      They define CONFIG_GENERIC_MMC, but not CONFIG_MMC.  Something
      might be wrong with these two boards, so should be checked later.
      
      Anyway, this is the output of the moveconfig tool.
      
      This commit was created as follows:
      
      [1] create a config entry in drivers/mmc/Kconfig
      
      [2] tools/moveconfig.py -r HEAD GENERIC_MMC
      
      [3] manual clean-up of garbage comments in doc/README.* and
          include/configs/*.h
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: NTom Rini <trini@konsulko.com>
      54925327
  19. 29 1月, 2017 7 次提交
    • M
      ARM: uniphier: make update commands more flexible for ATF · b7b43036
      Masahiro Yamada 提交于
      Currently, SPL (u-boot-spl.bin) and U-Boot (u-boot.bin) are stored
      in non-volatile devices, and some environments are defined to update
      the images easily.
      
      When ARM Trusted Firmware is fully used, SPL is not used.  U-Boot
      proper is contained as BL33 into FIP (Firmware Image Package), which
      is standard container used by ATF.  Allow to use it.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      b7b43036
    • M
      ARM: uniphier: change CONFIG_SPL_PAD_TO to 128KB · c0efc314
      Masahiro Yamada 提交于
      The Boot ROM supports authentication feature to prevent malformed
      software from being run on products.  The signature is added at the
      tail of the second stage loader (= SPL in U-boot terminology).
      
      The size of the second stage loader was 64KB, and it was consistent
      across SoCs.  The situation changed when LD20 SoC appeared; it loads
      80KB second stage loader, and it is the only exception.
      
      Currently, CONFIG_SPL_PAD_TO is set to 64KB and U-Boot proper is
      loaded from the 64KB offset of non-volatile devices.  This means the
      signature of LD20 SoC (located at 80KB offset) corrupts the U-Boot
      proper image.
      
      Let's move the U-Boot proper image to 128KB offset.  It uses 48KB
      for nothing but padding, and we could actually locate the U-Boot
      proper at 80KB offset.  However, the power of 2 generally seems a
      better choice for the offset address.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      c0efc314
    • M
      ARM: uniphier: change the offset to environment storage area · 0b93e3de
      Masahiro Yamada 提交于
      When ARM Trusted Firmware is used, bl1.bin + fip.bin exceeds 512KB,
      so the boot image and the current environment area will overlap.
      Move the environment storage to 1MB offset.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      0b93e3de
    • M
      ARM: uniphier: set initrd_high environment to skip initrd relocation · c0df1faf
      Masahiro Yamada 提交于
      The boot_ramdisk_high() checks the environment "initrd_high" and,
      if it is set to (ulong)-1, skip the initrd relocation.  This is
      useful for faster booting when we know the initrd is already located
      within the reach of the kernel.
      
      Change "norboot" to copy images in order to make it work without
      depending on the automatic relocation.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      c0df1faf
    • M
      ARM: uniphier: use Image.gz instead Image for booting ARM64 Linux · 99b85170
      Masahiro Yamada 提交于
      The ARM64 Linux raw image now amounts to 15MB and it is getting
      bigger and bigger.  Using Image.gz saves about 8MB.  The cost of
      unzip is smaller than what we get by saving the kernel loading
      from non-volatile devices.
      
      The ARM32 Linux still uses zImage, a self-decompressor image,
      so it should not be affected.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      99b85170
    • M
      ARM: uniphier: collect SPL CONFIG symbols to the bottom of header · 3e0cfaa0
      Masahiro Yamada 提交于
      For clarification, move CONFIG symbols that affect SPL building
      into a single place.  Drop #ifdef CONFIG_SPL ... #endif since it is
      harmless to define CONFIG_SPL_... during U-Boot proper building.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      3e0cfaa0
    • M
      ARM: uniphier: detect RAM size by decoding HW register instead of DT · 3e9952be
      Masahiro Yamada 提交于
      U-Boot needs to set up available memory area(s) in dram_init() and
      dram_init_banksize().  It is platform-dependent how to detect the
      memory banks.  Currently, UniPhier adopts the memory banks _alleged_
      by DT.  This is based on the assumption that users bind a correct DT
      in their build process.
      
      Come to think of it, the DRAM controller has already been set up
      before U-Boot is entered (because U-Boot runs on DRAM).  So, the
      DRAM controller setup register seems a more reliable source of any
      information about DRAM stuff.  The DRAM banks are initialized by
      preliminary firmware (SPL, ARM Trusted Firmware BL2, or whatever),
      so this means the source of the reliability is shifted from Device
      Tree to such early-stage firmware.  However, if the DRAM controller
      is wrongly configured, the system will crash.  If your system is
      running, the DRAM setup register is very likely to provide the
      correct DRAM mapping.
      
      Decode the SG_MEMCONF register to get the available DRAM banks.
      The dram_init() and dram_init_banksize() need similar decoding.
      It would be nice if dram_init_banksize() could reuse the outcome
      of dram_init(), but global variables are unavailable at this stage
      because the .bss section is available only after the relocation.
      As a result, SG_MEMCONF must be checked twice, but a new helper
      uniphier_memconf_decode() will help to avoid code duplication.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      3e9952be
  20. 28 1月, 2017 1 次提交
  21. 22 1月, 2017 2 次提交
    • M
      ARM: uniphier: make SPL optional for ARVv8 SoCs · 561ca649
      Masahiro Yamada 提交于
      We may want to run different firmware before running U-Boot.  For
      example, ARM Trusted Firmware runs before U-Boot, making U-Boot
      a non-secure world boot loader.  In this case, the SoC might be
      initialized there, which enables us to skip SPL entirely.
      
      This commit removes "select SPL" to make it configurable.  This
      also enables the Multi SoC support for the UniPhier ARMv8 SoCs.
      (CONFIG_ARCH_UNIPHIER_V8_MULTI)  Thanks to the driver model and
      Device Tree, the U-Boot proper part is now written in a generic way.
      The board/SoC parameters reside in DT.  The Multi SoC support
      increases the memory footprint a bit, but the U-Boot proper does
      not have strict memory constraint.  This will mitigate the per-SoC
      (sometimes per-board) defconfig burden.
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      561ca649
    • J
      config: Move CONFIG_BOARD_LATE_INIT to defconfigs · 3788b451
      Jagan Teki 提交于
      Cc: Tom Rini <trini@konsulko.com>
      Signed-off-by: NJagan Teki <jagan@openedev.com>
      3788b451
  22. 16 12月, 2016 1 次提交
  23. 19 11月, 2016 1 次提交
  24. 18 10月, 2016 1 次提交
  25. 12 10月, 2016 2 次提交
  26. 10 10月, 2016 3 次提交