1. 04 2月, 2014 9 次提交
  2. 30 1月, 2014 2 次提交
  3. 28 1月, 2014 1 次提交
  4. 27 1月, 2014 2 次提交
    • F
      boards.cfg: Keep the entries sorted · 0876703c
      Fabio Estevam 提交于
      Run "tools/reformat.py -i -d '-' -s 8 <boards.cfg >boards0.cfg && mv boards0.cfg boards.cfg"
      in order to keep the entries sorted.
      Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com>
      0876703c
    • A
      board_r - fixup functions table after relocation · 7395398a
      Alexey Brodkin 提交于
      This is only required for "PIC" relocation and doesn't apply to modern
      "PIE" relocation which does data relocation as well as code.
      
      "init_sequence_r" is just an array that consists of compile-time
      adresses of init functions. Since this is basically an array of integers
      (pointers to "void" to be more precise) it won't be modified during
      relocation - it will be just copied to new location as it is.
      
      As a consequence on execution after relocation "initcall_run_list" will
      be jumping to pre-relocation addresses. As long as we don't overwrite
      pre-relocation memory area init calls are executed correctly. But still
      it is dangerous because after relocation we don't expect initially used
      memory to stay untouched.
      
      Cc: Tom Rini <trini@ti.com>
      Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Doug Anderson <dianders@chromium.org>
      Cc: Thomas Langer <thomas.langer@lantiq.com>
      Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
      Acked-by: NSimon Glass <sjg@chromium.org>
      Signed-off-by: NAlexey Brodkin <abrodkin@synopsys.com>
      7395398a
  5. 25 1月, 2014 26 次提交