RFC: Location for Device Tree Sources?

[Paul Mackerras]

Tom Rini writes:

> But "content requirements change" isn't the same as "left things out of
> their tree".  It sounds, and I haven't seen the changes, so I'm not
> certain that the meaning behind a field changed.  Something like that
> should change the dt version.

I disagree.  Strongly.  The dt version relates to the representation
of the tree, not its content.

If we *have* to change the meaning of a property value in a particular
node in an incompatible way, then we can do something such as adding
another property to indicate what the interpretation of the first
property value should be.  Usually it's possible to find a way around
the problem without resorting to that, though.

>  New fields aren't a problem.  Changing
> existing fields meaning in incompatible ways is a problem.

Only a minor, localized problem.  Nothing worth changing the whole dt
version number for.

Paul.