On Mon, 30 Sep 2013, Tim Bird wrote: > What is the long-term mechanism/methodology for creating a kernel > that runs on a single system? So many drivers now have device-tree > dependencies that it seems unlikely we'll be able to avoid using > device tree. But if we don't care or don't want to support more than > a single platform, what should we do (if appending DTB to the zImage > will eventually go away). Will the requirement be that all future > Linux bootloaders will be DT-aware? The ability to append a DTB to zImage is not going away tomorrow, although I encourage you to use another solution if possible. What can be done on a simple single platform setup is to load the DTB from flash into RAM just like another blob along with the ramdisk image and the zImage itself. Then you just have to branch into zImage with the address of the DTB in RAM into r2. Most bootloaders are able to load arbitrary binaries into memory, and most bootloaders (except for U-Boot) are able to set arbitrary values into r0-r3 before branching to some location in memory. Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
