1. 21 11月, 2014 1 次提交
    • S
      fdt: Allow ft_board_setup() to report failure · e895a4b0
      Simon Glass 提交于
      This function can fail if the device tree runs out of space. Rather than
      silently booting with an incomplete device tree, allow the failure to be
      detected.
      
      Unfortunately this involves changing a lot of places in the code. I have
      not changed behvaiour to return an error where one is not currently
      returned, to avoid unexpected breakage.
      
      Eventually it would be nice to allow boards to register functions to be
      called to update the device tree. This would avoid all the many functions
      to do this. However it's not clear yet if this should be done using driver
      model or with a linker list. This work is left for later.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Acked-by: NAnatolij Gustschin <agust@denx.de>
      e895a4b0
  2. 23 7月, 2014 1 次提交
    • Y
      powerpc/mpc85xx: Check return value of find_tlb_idx · 9d045682
      York Sun 提交于
      find_tlb_idx() is called in board_early_init_r() on multiple boards.
      The return value is not checked before being used to disable a TLB.
      In normal case the return value wouldn't be -1. In case of a mis-
      configuration during porting to a new board, checking the return value
      may be helpful to reveal some user errors.
      Signed-off-by: NYork Sun <yorksun@freescale.com>
      9d045682
  3. 26 11月, 2013 1 次提交
  4. 17 10月, 2013 3 次提交
  5. 24 7月, 2013 1 次提交
  6. 03 5月, 2013 1 次提交
  7. 04 2月, 2013 1 次提交
  8. 07 7月, 2012 2 次提交
  9. 25 4月, 2012 1 次提交
    • T
      powerpc/85xx: don't display address map size (32-bit vs. 36-bit) during boot · 5d065c3e
      Timur Tabi 提交于
      Most 85xx boards can be built as a 32-bit or a 36-bit.  Current code sometimes
      displays which of these is actually built, but it's inconsistent.  This is
      especially problematic since the "default" build for a given 85xx board can
      be either one, so if you don't see a message, you can't always know which
      size is being used.  Not only that, but each board includes code that displays
      the message, so there is duplication.
      
      The 'bdinfo' command has been updated to display this information, so
      we don't need to display it at boot time.  The board-specific code is
      deleted.
      Signed-off-by: NTimur Tabi <timur@freescale.com>
      Signed-off-by: NAndy Fleming <afleming@freescale.com>
      5d065c3e
  10. 08 11月, 2011 1 次提交
  11. 30 9月, 2011 1 次提交