summaryrefslogtreecommitdiff
path: root/arch/arm/mach-ixp4xx/vulcan-setup.c
diff options
context:
space:
mode:
authorNicolas Pitre <nicolas.pitre@linaro.org>2011-06-14 02:40:33 -0400
committerNicolas Pitre <nico@fluxnic.net>2011-06-23 02:33:58 -0400
commitfd454c1ab28387cc03618ef84cb172fa9f8fdeb4 (patch)
treebbe0b6d5fc22f8a6f0555663f42efaa7837b09b1 /arch/arm/mach-ixp4xx/vulcan-setup.c
parentd22ebec9fbae7c59ce941957408af7e12f773073 (diff)
ARM: zImage: allow supplementing appended DTB with traditional ATAG data
Some old bootloaders can't be updated to a device tree capable one, yet they provide ATAGs with memory configuration, the ramdisk address, the kernel cmdline string, etc. To allow a device tree enabled kernel to be used with such bootloaders, it is necessary to convert those ATAGs into FDT properties and fold them into the DTB appended to zImage. Currently the following ATAGs are converted: ATAG_CMDLINE ATAG_MEM (up to 8 memory regions) ATAG_INITRD2 If the corresponding information already exists in the appended DTB, it is replaced, otherwise the required node is created to hold it. The code looks for ATAGs at the location pointed by the value of r2 upon entry into the zImage code. If no ATAGs are found there, an attempt at finding ATAGs at the typical 0x100 offset from start of RAM is made. Otherwise the DTB is left unchanged. Thisstarted from an older patch from John Bonesio <bones@secretlab.ca>, with contributions from David Brown <davidb@codeaurora.org>. Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org>
Diffstat (limited to 'arch/arm/mach-ixp4xx/vulcan-setup.c')
0 files changed, 0 insertions, 0 deletions