1. 11 9月, 2018 29 次提交
  2. 10 9月, 2018 1 次提交
    • M
      fdt: fix get_next_memory_node() · f8503719
      Marek Vasut 提交于
      The get_next_memory_node() always sets mem to -1 , which is incorrect,
      because then every iteration of memory bank parsing will start from the
      first memory bank instead of the previous one.
      
      On systems with 1 memory bank defined in DT and CONFIG_NR_DRAM_BANKS=4 ,
      like ie. r8a77965-salvator-x , this will result in U-Boot incorrectly
      reporting four identical memory banks with the same memory configuration.
      
      Fix this by setting mem to startoffset value, which restores the behavior
      before the fixed patch was applied.
      Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com>
      Cc: Jens Wiklander <jens.wiklander@linaro.org>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Tom Rini <trini@konsulko.com>
      Fixes: 452bc121 ("fdt: fix fdtdec_setup_memory_banksize()")
      Tested-by: Michal Simek <michal.simek@xilinx.com> [on ZynqMP}
      f8503719
  3. 07 9月, 2018 1 次提交
  4. 06 9月, 2018 7 次提交
  5. 05 9月, 2018 2 次提交