From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Sealey Subject: Re: Device tree binding documentation Date: Tue, 28 Oct 2008 11:58:25 -0500 Message-ID: <490744B1.2000602@genesi-usa.com> References: <9696D7A991D0824DBA8DFAC74A9C5FA3047E572F@az33exm25.fsl.freescale.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA3047E572F-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org To: Yoder Stuart Cc: Hugh Blemings , devicetree-discuss list , Benjamin Herrenschmidt , Anton Vorontsov List-Id: devicetree@vger.kernel.org Yoder Stuart wrote: > > So my vote is to maintain bindings as plain text files. Just like the real elections I don't actually have a vote here, but can I put my oar in that after a certain review process and time has passed and the binding stabilizes, these get published as PDF documents similar to an AppNote or the ePAPR specification so that you get the advantages of bookmarks, pagination, formatting (notes, examples and warnings) and printing it in a reasonable fashion on a dead tree as if it were a book? 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" ? -- Matt Sealey Genesi, Manager, Developer Relations