Device tree binding documentation

[Matt Sealey]

Scott Wood wrote:
> Matt Sealey wrote:
>> Maintaining them as text for the development process is good but
>> they need to be *published* as the ePAPR binding is *published*,
>> so that you can say.. "hey, this is a canonical reference on a
>> dead tree, my platform confirms to the ePAPR MPC5200B device
>> tree binding V1.0 that I ordered from the Freescale website",
>> instead of "my platform conforms to git commit fab927fe363ac2a872bb872"
> 
> The latter is actually much less subject to change... :-)

Right until the git repo is down and you don't have a copy as
reference :D

Basically it would solve all the nitpicking about how a device tree
wasn't right on a certain board (as long as it fit a certain spec,
drivers would be required to maintain compatibility with that spec)
and wouldn't get these weird effects when they change USB and decide
that they need to pare down the matchlists and break a working
board.

At least if you can refer to ePAPR right now, it's there for download
as a book-type spec for the basic elements, the same way you could with
OF, and the OF bindings were traditionally published in Postscript (and
written in tex? lord knows.. that's complicating documentation writing
but the symbol support and math support is far, far better than ASCII
art)

-- 
Matt Sealey <matt at genesi-usa.com>
Genesi, Manager, Developer Relations