On 12/10/2011 03:42 PM, Linus Walleij wrote: ...
Since this was so convenient I made a patch to attach a DTB the same way which was floated on devicetree-discuss: http://www.mail-archive.com/devicetree-discuss@lists.ozlabs.org/msg07256.htm...
Nico didn't like that: http://www.mail-archive.com/devicetree-discuss@lists.ozlabs.org/msg06828.htm...
Alas, I'm still using that patch though. For systems where I cannot influence the boot loader it's easiest, since I just add another config snippet when I want to run them with DT:
scripts/config --file .config \ --enable USE_OF \ --enable ARM_APPENDED_DTB \ --enable ARM_ATAG_DTB_COMPAT \ --enable PROC_DEVICETREE \ --set-str ARM_APPENDED_DTB_FILE my-device-tree.dtb
Jut as an FYI, there's also:
git://git.secretlab.ca/git/linux-2.6 devicetree/test fbae2702ae21ad8d1de5f135647c30b250782060 "Build a uImage with dtb already appended".
I tend to use this all the time for device-tree.
I find this significantly easier than using U-Boot's pass-an-FDT-to-the-kernel feature, because right now half the time I'm passing an FDT and half not, and making U-Boot's script support either option automatically isn't something I really want to get into when I can simply "make uImage" or "make uImage-dtb.tegra-${board}" to select which option I want when building the kernel.