1. 30 11月, 2017 4 次提交
  2. 11 10月, 2017 1 次提交
    • T
      cmd: Toggle the default value of CONFIG_CMD_IMLS · ad12dc18
      Tuomas Tynkkynen 提交于
      Having this as a 'default y' is rather annoying because it doesn't
      actually compile unless other options are defined in the board header:
      
      ../cmd/bootm.c: In function 'do_imls_nor':
      ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
         i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {
      
      Make it 'default n' so people who develop new boards that start from a
      blank defconfig have one less compilation failure to debug.
      Signed-off-by: NTuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
      ad12dc18
  3. 04 10月, 2017 1 次提交
  4. 28 9月, 2017 3 次提交
  5. 24 9月, 2017 2 次提交
  6. 13 9月, 2017 1 次提交
  7. 08 9月, 2017 1 次提交
    • M
      ARM: rmobile: Disable CONFIG_ARCH_FIXUP_FDT_MEMORY · 25f840d7
      Marek Vasut 提交于
      Disable CONFIG_ARCH_FIXUP_FDT_MEMORY to prevent U-Boot from modifying
      the memory {} nodes in the DT passed to the Linux kernel. The R8A779x
      DT contains multiple memory {} nodes, while U-Boot only modifies the
      first one and stuffs all the memory entries into it, which is wrong.
      Disabling CONFIG_ARCH_FIXUP_FDT_MEMORY is the least intrusive way to
      fix the issue this close to the release, while the real fix is to
      extend the fdt_fixup_memory_banks() to handle multiple memory nodes
      in DT.
      Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com>
      Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
      25f840d7
  8. 28 8月, 2017 1 次提交
  9. 26 8月, 2017 3 次提交
  10. 15 8月, 2017 2 次提交
  11. 12 8月, 2017 1 次提交
  12. 11 8月, 2017 1 次提交
  13. 08 8月, 2017 1 次提交
  14. 03 8月, 2017 4 次提交
  15. 26 7月, 2017 1 次提交
    • 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
  16. 21 6月, 2017 1 次提交
  17. 19 6月, 2017 1 次提交
  18. 04 6月, 2017 1 次提交
  19. 22 5月, 2017 7 次提交
  20. 08 4月, 2017 1 次提交
  21. 14 3月, 2017 1 次提交
  22. 28 1月, 2017 1 次提交