summaryrefslogtreecommitdiff
path: root/board/ebv
diff options
context:
space:
mode:
authorNathan Rossi <nathan@nathanrossi.com>2016-12-04 19:33:22 +1000
committerMichal Simek <michal.simek@xilinx.com>2016-12-08 10:04:20 +0100
commit64b67fb24bf4dfd4e15a6e43ba2ed4e5fa31b5b0 (patch)
tree76217c0867c6e44b180d2a7c26c74e410520b6db /board/ebv
parent3fd4de8840ada7d91fdc231049a6543f447e483a (diff)
ARM: zynq: Replace dram_init* functions with board_init_f safe ones
The dram_init* functions for the zynq board are not safe for use from the board_init_f stage due to its use of the 'tmp' static variable. This incorrect use of a static variable was causing rare issues where the dram_init function would overwrite some parts the __rel_dyn section which caused obscure failures. Using the zynq_zybo configuration, U-Boot would generate the following error during image load. This was caused due to dram_init overwriting the relocations for the "image" variable within the do_bootm function. Out of coincidence the un-initialized memory has a compression type which is the same as the value for the relocation type R_ARM_RELATIVE. Uncompressing Invalid Image ... Unimplemented compression type 23 It should be noted that this is just one way the issue could surface, other cases my not be observed in normal boot flow. This change removes the existing code and copies the implementation of the dram_init and dram_init_banksize from the arch/arm/mach-uniphier/dram_init.c source. This version of these functions does not use static variables and behaves the same (reading banks from fdt, and using the first bank as the ram_size). Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Fixes: 758f29d0f8 ("ARM: zynq: Support systems with more memory banks") Cc: Michal Simek <monstr@monstr.eu> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
Diffstat (limited to 'board/ebv')
0 files changed, 0 insertions, 0 deletions