1. 20 2月, 2014 2 次提交
  2. 09 1月, 2014 3 次提交
  3. 13 12月, 2013 1 次提交
    • A
      board_f: explicitly disable console on early boot · 9aed5a27
      Alexey Brodkin 提交于
      If U-Boot build with DEBUG enabled/defined the first call of "debug"
      function (that dumps data to any available console) will happen before
      zeroing of initial "gd" in init call "zero_global_data" in
      "init_sequence_f".
      
      And if stack was not filled with zeros chances are high that
      "gd->have_console" won't be 0. In its turn it will cause attempt to
      output things to non-initialized yet serial console.
      
      So for safety and predictability we set "gd->have_console = 0".
      Signed-off-by: NAlexey Brodkin <abrodkin@synopsys.com>
      
      Cc: Mischa Jonker <mjonker@synopsys.com>
      Cc: Wolfgang Denk <wd@denx.de>
      Cc: Simon Glass <sjg@chromium.org>
      Acked-by: NSimon Glass <sjg@chromium.org>
      9aed5a27
  4. 17 10月, 2013 1 次提交
    • T
      i2c: fix init on generic board · 815a76f2
      trem 提交于
      On generic board, the i2c init initialize only
      one bus. But the new i2c subsystem allow to
      manage severals i2c bus. So in the case, instead
      of initializing a bus, we just set the current
      i2c bus. The initialization will be done in
      the i2c command.
      Signed-off-by: NPhilippe Reynes <tremyfr@yahoo.fr>
      815a76f2
  5. 24 7月, 2013 1 次提交
  6. 23 7月, 2013 2 次提交
  7. 26 6月, 2013 1 次提交
    • S
      Add trace support to generic board · 71c52dba
      Simon Glass 提交于
      Add hooks for tracing to generic board, including:
      
      - allow early tracing to start early as possible in U-Boot
      - reserve memory for trace buffer
      - copy early trace buffer to main trace buffer after relocation
      - setup full tracing support after relocation
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      71c52dba
  8. 08 6月, 2013 1 次提交
    • M
      generic_board: reduce the redundancy of gd_t struct members · a0ba279a
      Masahiro Yamada 提交于
      This commit refactors common/board_f.c and common/board_r.c
      in order to delete the dest_addr and dest_addr_sp from
      gd_t struct.
      
      As mentioned as follows in include/asm-generic/global_data.h,
      
        /* TODO: is this the same as relocaddr, or something else? */
        unsigned long dest_addr;        /* Post-relocation address of U-Boot */
      
      dest_addr is the same as relocaddr.
      Likewise, dest_addr_sp is the same as start_addr_sp.
      
      It seemed dest_addr/dest_addr_sp was used only as a scratch variable
      to calculate relocaddr/start_addr_sp, respectively.
      
      With a little refactoring, we can delete dest_addr and dest_addr_sp.
      Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Simon Glass <sjg@chromium.org>
      a0ba279a
  9. 05 6月, 2013 1 次提交
    • M
      common: board_f: Do not call board_postclk_init twice · b8521b74
      Masahiro Yamada 提交于
      The generic-board board_init_f function called board_postclk_init twice.
      
      The first one came from arch/arm/lib/board.c, while the second one
      from arch/powerpc/lib/board.c.
      
      This commit deletes the first occurrence.
      In addition, the second get_clocks call is moved after
      board_postclk_init in order to keep the function call order
      both for ARM and PowerPC.
      ARM board calles get_clocks function after board_postclk_init.
      Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
      b8521b74
  10. 15 5月, 2013 1 次提交
  11. 02 5月, 2013 1 次提交
  12. 01 5月, 2013 2 次提交
  13. 16 4月, 2013 2 次提交
    • S
      x86: Allow setup code to manage its own global data · 7525c2da
      Simon Glass 提交于
      Currently x86 has its own means of managing the global data and board data
      (bd_t), and this code resides in start.S. With generic board, we need to
      ensure that we leave this alone - i.e. don't clear it as we do on other
      archs.
      
      This fixes a problem where the memory init data is cleared which causes
      the video driver to operate very slowly.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      7525c2da
    • S
      x86: Fix DRAM bank size init with generic board · 8b42dfc3
      Simon Glass 提交于
      The intention of the memory init code is that it should work the same with
      CONFIG_SYS_GENERIC_BOARD and without. This is tricky because dram_init()
      is called prior to relocation with generic board (matching other archs)
      and after relocation without generic board.
      
      Adjust the init sequence so that dram_init() is not called in the generic
      board case, which seems like the easiest fix for now. Also ensure that
      relocation addresses are still calculated.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      8b42dfc3
  14. 12 4月, 2013 1 次提交
  15. 16 3月, 2013 5 次提交