diff options
| author | Stephan Linz <linz@li-pro.net> | 2010-06-25 18:04:59 +0200 |
|---|---|---|
| committer | Wolfgang Denk <wd@denx.de> | 2010-08-08 22:16:05 +0200 |
| commit | 958e120643e8b6765b3ff84dfcf57624076afd21 (patch) | |
| tree | ed6dfa4c17cfd83b3ba796a237ad415432b800be /board/kup/common/kup.c | |
| parent | cd1535564c3d52d2bc063e54e7d11ace7aeb9f52 (diff) | |
| download | u-boot-imx-958e120643e8b6765b3ff84dfcf57624076afd21.zip u-boot-imx-958e120643e8b6765b3ff84dfcf57624076afd21.tar.gz u-boot-imx-958e120643e8b6765b3ff84dfcf57624076afd21.tar.bz2 | |
fdt relocate: have more attention to use a bootmap or not
Platforms with flat device tree support can use a bootmap to relocate
the fdt_blob. This is not a must. That's why the relocation function
boot_relocate_fdt() should be use only if CONFIG_OF_LIBFDT was defined
together with CONFIG_SYS_BOOTMAPSZ (see common/cmd_bootm.c).
On MicroBlaze platforms there is no need to use a bootmap to relocate
a fdt blob. So we need a more precise focus on the compilation and usage
of boot_relocate_fdt().
In general it is valid to exclude the function boot_relocate_fdt() if
the bootmap size CONFIG_SYS_BOOTMAPSZ is not defined.
Signed-off-by: Stephan Linz <linz@li-pro.net>
Diffstat (limited to 'board/kup/common/kup.c')
0 files changed, 0 insertions, 0 deletions