[U-Boot] [PATCH] fdt relocate: have more attention to use a bootmap or not

[Wolfgang Denk]

Dear Stephan Linz,

In message <0ac40268094bc00a447aeb4f5775c670a79868e9.1277481856.git.linz at li-pro.net> you wrote:
> 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 at li-pro.net>
> ---
>  arch/powerpc/lib/bootm.c |    4 ++--
>  common/image.c           |    2 ++
>  2 files changed, 4 insertions(+), 2 deletions(-)

Applied, thanks.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Extended Epstein-Heisenberg Principle: In an R & D orbit, only  2  of
the  existing 3 parameters can be defined simultaneously. The parame-
ters are: task, time and resources ($).