1. 02 Aug, 2019 1 commit
  2. 12 Apr, 2019 1 commit
  3. 25 Mar, 2019 2 commits
  4. 17 Aug, 2018 1 commit
  5. 07 May, 2018 1 commit
    • Tom Rini's avatar
      SPDX: Convert all of our single license tags to Linux Kernel style · 83d290c5
      Tom Rini authored
      When U-Boot started using SPDX tags we were among the early adopters and
      there weren't a lot of other examples to borrow from.  So we picked the
      area of the file that usually had a full license text and replaced it
      with an appropriate SPDX-License-Identifier: entry.  Since then, the
      Linux Kernel has adopted SPDX tags and they place it as the very first
      line in a file (except where shebangs are used, then it's second line)
      and with slightly different comment styles than us.
      In part due to community overlap, in part due to better tag visibility
      and in part for other minor reasons, switch over to that style.
      This commit changes all instances where we have a single declared
      license in the tag as both the before and after are identical in tag
      contents.  There's also a few places where I found we did not have a tag
      and have introduced one.
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
  6. 24 Feb, 2018 1 commit
  7. 17 Nov, 2017 1 commit
  8. 03 Sep, 2017 1 commit
  9. 14 Aug, 2017 1 commit
  10. 26 Jul, 2017 2 commits
    • Simon Glass's avatar
      Convert CONFIG_ENV_IS_IN_SPI_FLASH to Kconfig · 91c868fe
      Simon Glass authored
      This converts the following to Kconfig:
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    • Simon Glass's avatar
      Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig · 2be29653
      Simon Glass authored
      This converts the following to Kconfig:
      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
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
  11. 22 May, 2017 3 commits
  12. 12 Feb, 2017 1 commit
    • Masahiro Yamada's avatar
      flash: complete CONFIG_SYS_NO_FLASH move with renaming · e856bdcf
      Masahiro Yamada authored
      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
      [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: Masahiro Yamada's avatarMasahiro Yamada <yamada.masahiro@socionext.com>
  13. 08 Feb, 2017 1 commit
  14. 28 Jan, 2017 2 commits
  15. 23 Oct, 2016 2 commits
  16. 20 Sep, 2016 1 commit
  17. 25 Apr, 2016 4 commits
  18. 14 Mar, 2016 1 commit
  19. 25 Nov, 2015 1 commit
  20. 24 Oct, 2015 1 commit
  21. 21 Oct, 2015 1 commit
  22. 13 Aug, 2015 1 commit
    • Nikita Kiryanov's avatar
      kconfig: add config option for shell prompt · 181bd9dc
      Nikita Kiryanov authored
      Add option to set shell prompt string from menuconfig and migrate
      boards globally.
      The migration is done as follows:
      - Boards that explicitly and unconditionally set CONFIG_SYS_PROMPT had the
        entry moved to their defconfig files.
      - Boards that defined some kind of #ifdef logic which selects the
        CONFIG_SYS_PROMPT (for example qemu-mips) got an #undef CONFIG_SYS_PROMPT
        right before the #ifdef logic and were left alone.
      - This change forces CONFIG_SYS_PROMPT to be a per board decision, and thus
        CONFIG_SYS_PROMPT was removed from all <soc>_common.h and <arch>_common.h
        files. This results in a streamlined default value across platforms, and
        includes the following files: spear-common, sunxi-common, mv-common,
        ti_armv7_common, tegra-common, at91-sama5_common, and zynq-common.
      - Boards that relied on <arch/soc>_common.h values of CONFIG_SYS_PROMPT were
        not updated in their respective defconfig files under the assumption that
        since they did not explicitly define a value, they're fine with whatever
        the default is.
      - On the other hand, boards that relied on a value defined in some
        <boards>_common.h file such as woodburn_common, rpi-common,
        bur_am335x_common, ls2085a_common, siemens_am33x_common, and
        omap3_evm_common, had their values moved to the respective defconfig files.
      - The define V_PROMPT was removed, since it is not used anywhere except for
        assigning a value for CONFIG_SYS_PROMPT.
      Cc: Tom Rini <trini@konsulko.com>
      Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Signed-off-by: default avatarNikita Kiryanov <nikita@compulab.co.il>
      [trini: Add spring, sniper, smartweb to conversion]
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
  23. 26 Jun, 2015 1 commit
  24. 01 Jun, 2015 1 commit
  25. 20 May, 2015 1 commit
  26. 12 Feb, 2015 3 commits
    • Michael Walle's avatar
      lsxl: switch from bootm to bootz for boot commands · 4fe49d7b
      Michael Walle authored
      Use the bootz command to load zImages in case of any new boot scripts. Only
      the legacy one will still use bootm. Apart form the fact, that this will
      simplify the image generation process, it saves one copy of the kernel
      image: Common practice is to generate an uImage with a loading address of
      0x8000. This uImage contains a compressed zImage, which will unpack the
      kernel image to the beginning of the RAM. But because there is already the
      compressed image the uncompressor first relocates the compressed image to a
      higher location. The load address is encoded into the uImage which is
      generated by the distributions and thus cannot be easily changed. By using
      the bootz command we can load the compressed image to a higher memory
      address and the decompressor doesn't have to reloacte the image.
      Signed-off-by: default avatarMichael Walle <michael@walle.cc>
    • Michael Walle's avatar
      lsxl: place the dtb below the inital ramdisk · 145df6fe
      Michael Walle authored
      The dtb was loaded at a memory address after the initial ramdisk. Thus a
      large ramdisk would overwrite the dtb. Move it to "ramdisk_start - 64k".
      64k should be enough for the device tree blob. Also the kernel
      documentation arm/Booting suggests to put the dtb before the initial
      Signed-off-by: default avatarMichael Walle <michael@walle.cc>
    • Michael Walle's avatar
      lsxl: use default load addresses for legacy boot · bc2ad9f0
      Michael Walle authored
      The load addresses for the bootcmd_legacy script were taken from the
      original bootloader from Buffalo. But newer kernels are too big and the
      uncompressing will overwrite parts of the initial ramdisk. Therefore,
      we switch to the load addresses which are also used by the other boot
      Signed-off-by: default avatarMichael Walle <michael@walle.cc>
  27. 06 Oct, 2014 1 commit
  28. 31 Aug, 2014 1 commit
  29. 25 May, 2014 1 commit
    • Michael Walle's avatar
      lsxl: rework boot scripts · 848fe239
      Michael Walle authored
      Move addresses for kernel, ramdisk and fdt blob to own variables. Add dtb
      blob loading to all existing boot scripts, dtb filenames were taken from
      vanilla kernel. Introduce new boot script bootcmd_legacy, which only loads
      a kernel and a ramdisk. Make this the default boot script. This should also
      restore the behaviour of the original bootloader.
      Cc: Prafulla Wadaskar <prafulla@marvell.com>
      Cc: Tom Rini <trini@ti.com>
      Signed-off-by: default avatarMichael Walle <michael@walle.cc>