[PATCH 15/16] Add device tree for Ebony

[Paul Mackerras]

Segher Boessenkool writes:

> > We don't require an OF device tree;
> 
> When booting on real OF you do.

No, the kernel requires a flattened tree, which is created by glue
code from the OF device tree.  Currently everything in the OF tree
goes across into the flattened tree, but in future there may not be a
1-1 correspondence.

> > what we require is something that
> > provides a way to express what the kernel needs to know about the
> > hierarchy, interconnections and characteristics of the devices in the
> > system.
> 
> Sure.  You could have chosen a structure that is closer to the
> internal Linux structures.

What internal Linux structures?  In any case it's a mistake to tie
internal and external structures together because it creates future
compatibility headaches.

> > That it looks strangely familiar to you is just a
> > coincidence. :)
> 
> Heh suuuuuuuure :-)

The device tree is basically a generalization of the list of tags +
values that ppc and other architectures use.  The tags are strings
rather than numbers, because that makes sense, and you can group sets
of tags + values that relate to a particular device together, and you
can link devices together in a hierarchical arrangement.

The last thing I want to do is to put unnecessary burdens on embedded
platforms just to comply with OF requirements.  We have the device
tree because it makes sense both for embedded and for desktop/server
machines, not because OF is some sort of holy writ.

Paul.