summaryrefslogtreecommitdiff
path: root/board/cm-bf537e
diff options
context:
space:
mode:
authorYe.Li <B37916@freescale.com>2014-01-10 17:55:46 +0800
committerYe.Li <B37916@freescale.com>2014-01-10 18:23:05 +0800
commit372f1e0c87e1e43b4d4dac7b05ddd077aff7d24e (patch)
treecc8f8e594ddd829873798fc0a134812e06ae6bac /board/cm-bf537e
parentc089f6c136bf04dd813633a00bf47cd6e1a5bb30 (diff)
downloadu-boot-imx-372f1e0c87e1e43b4d4dac7b05ddd077aff7d24e.zip
u-boot-imx-372f1e0c87e1e43b4d4dac7b05ddd077aff7d24e.tar.gz
u-boot-imx-372f1e0c87e1e43b4d4dac7b05ddd077aff7d24e.tar.bz2
ENGR00294746 ARM:imx6:sabresd/sabreauto/slevk Support android FDT embedded image
Since the "mkbootimg" tool can't use the "unused" fields of bootimg header, Android will set the FDT info at the "second_addr" and "second_size" fields. To support this change, booti command was changed to use new fields. The memory management(lmb) is added in booti, and the relocation of DTB and ramdisk is disabled at default, to prevent relocating to a high address which overlaps kernel's vmalloc area. The kernel image which needs FDT accompanied is larger than old. So in making boot.img, suggest to set "--base" parameter enough offset from kernel entry "0x10008000" to keep ramdisk and DTB not be overwritten by zImage decompression. For example "--base 0x14000000" Signed-off-by: Ye.Li <B37916@freescale.com>
Diffstat (limited to 'board/cm-bf537e')
0 files changed, 0 insertions, 0 deletions