RFC: Location for Device Tree Sources?

Li Yang LeoLi at freescale.com
Fri Aug 4 01:47:08 EST 2006

On 8/3/06, Tom Rini <trini at kernel.crashing.org> wrote:
> On Wed, Aug 02, 2006 at 08:35:55AM -0500, Kumar Gala wrote:
> > I like this location and agree that having them in tree makes sense.
> > And putting them under boot isolates them from the kernel proper.
> >
> > The reason I see to having them in tree is to ensure proper version
> > compatibility.  This way there is no concern about which .dts version
> > will work with which kernel.  In the future we can always pull them
> > out when things are more stable.
> I'd rephrase that as an arguement to keep them out of tree:
> The reason I see to having them out of tree is to ensure we follow the
> intent trees holding the information about where devices live and the
> kernel being good and asking the trees.  This way there is no concern
> about which (otherwise valid) .dts version will work with which kernel,
> as breaking a valid .dts is either a bug (unintentional API change or a
> 'Oops, I forgot that the tree might not specify X' which potentially
> preempts the custom board Y (that's like a sandpoint!) just doesn't have
> X bugs) or a change that requires a dts version bump.
> I'll throw in the caveat that I'm not 100% sure we're that stable yet,
> but it certainly seems like it, at least for the overall portion where
> you might really have incompatible trees.  More or less complete (now
> every device is described!) dts should be interchangable to the kernel
> for the custom board X is just a little different from ref board Y
> issues (and now, in theory, the Just Like A Sandpoint board, with a
> correct dts will boot the 'sandpoint' kernel).

I don't know why we are talking about versions here.  My argument to
including dts in tree is very simple.  dts is in many ways similiar to
kernel config file.  If we justified to put default kernel config
files in tree.  There will be no difference to make dts in tree too.
Moreover, dts can't be generated or modified easily like kernel
config.  It's even more important to make a working example handier to
get for user.

More information about the Linuxppc-dev mailing list