I am working with a powerpc embedded system where u-boot seems to be passing in
a constructed fdt (or one embedded in u-boot) as opposed to one that is either
passed directly to bootm or as the third image of a multi-file image.
I'm sure sure that the system is NOT using my dtb file because I modified the
my linux platform file to print out the "model" and "compatible" properties of
root, and they make sense, but are not the values that I pass in with my dtb.
I've tried "bootm ${kerneladdr} - ${dtbaddr}" for nfs boot, and I've
constructed a multi-file uImage with kernel:initramfs:dtb. The behavior is the
same in all cases. Is this expected behavior, and if so, is there some way to
force u-boot to use my dtb file?
Thanks,
JR
_______________________________________________
U-Boot mailing list
[email protected]
http://lists.denx.de/mailman/listinfo/u-boot
