Re: Device tree flattening code not copying properties from blob
From: Walter Goossens <hidden>
Date: 2013-06-12 19:12:39
On 06/12/13 20:23, Grant Likely wrote:
On Wed, Jun 12, 2013 at 6:33 PM, Collins, Rod [off-list ref] wrote:quoted
The blob is built into the zImage.initramfs.gz image which is put into flash. The zImage.initramfs.gz is self copied from flash to RAM, then uncompressed to the running area. I will dig into the location of the blob in the image and report back.Thanks. If it is appended to the zImage wrapper, then things should be fine (this is the expected way to do when not passed in from the bootloader). If a *.dtb.o target has been used to embedded it into the kernel-proper (vmlinux) then you will have a problem. The *.dtb.S target puts the dtb data into the dtb.init.rodata section which gets discarded. g.
Hi Grant, you're right that's exactly what nios2 is doing... I guess we could modify the section where it gets loaded but that sounds to me a bit like a hack... What is the best target to look at for a clean, similar solution? Arm with CONFIG_ARM_APPENDED_DTB? Walter
_______________________________________________ devicetree-discuss mailing list devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org https://lists.ozlabs.org/listinfo/devicetree-discuss