From mboxrd@z Thu Jan 1 00:00:00 1970 From: swarren@wwwdotorg.org (Stephen Warren) Date: Wed, 31 Jul 2013 13:57:37 -0600 Subject: Defining schemas for Device Tree In-Reply-To: References: <51F6E30B.7060106@wwwdotorg.org> <1706112.Xn49tiCSKF@thinkpad> <20130730102511.GM9858@sirena.org.uk> <51F7F596.6020503@wwwdotorg.org> <20130730205716.GZ9858@sirena.org.uk> <20130730230331.GC9858@sirena.org.uk> Message-ID: <51F96C31.8030305@wwwdotorg.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 07/30/2013 05:23 PM, jonsmirl at gmail.com wrote: ... > Uboot could be an issue but I don't think they are actually doing > anything with FDTs yet, they are just talking about doing it. A couple U-Boot platforms (Tegra, Exynos) actually use DT to parameterize U-Boot itself, just like the kernel uses it, although: * often the bindings used there are not the "real" bindings defined in the kernel:-( * They use a DTB embedded into the U-Boot binary, which is a different DTB to that passed to the kernel, which at least in the Tegra case is always loaded from disk e.g. from /boot, just like zImage is. U-Boot certainly passes DTs to the kernel, and performs some limited modification on it such as setting the kernel cmdline, memory size, etc.