All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Stefan Seefeld <stefan-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
Cc: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Formal grammar for DTS
Date: Mon, 2 Mar 2015 15:54:03 +1100	[thread overview]
Message-ID: <20150302045403.GE29409@voom.fritz.box> (raw)
In-Reply-To: <54F1DD4F.3080304-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

On Sat, Feb 28, 2015 at 10:22:55AM -0500, Stefan Seefeld wrote:
> Hello,
> 
> I would like to write a tool / library that allows me to
> (programmatically) edit .dts files, with the ability to regenerate the
> source files, preserving the original formatting (including comments and
> other non-semantic content).
> 
> To that end I need a formal definition of the DTS grammar. While I have
> found the dtc tool, all its source files (in particular the dtc-lexer.l
> and dtc-parser.y files) are released under GPL, so it isn't entirely
> clear whether I may use the grammar encoded in those and transcribe that
> into my own (I'm writing my tool in Java, most likely using the JavaCC
> parser generator tool).
> 
> So, is there another place where the grammar of Device Tree source files
> is formally defined in ways that allows tools developers to use that ?
> Any help and advice would be highly appreciated.

I'm not aware of any other presentation of the dts grammar than in the
source files.

IANAL, but fwiw, I wouldn't consider transcribing the grammar rules
(without the semantic actions) into some other form to be a derived
work triggering the GPL.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-03-02  4:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28 15:22 Formal grammar for DTS Stefan Seefeld
     [not found] ` <54F1DD4F.3080304-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
2015-03-02  4:54   ` David Gibson [this message]
     [not found]     ` <20150302045403.GE29409-RXTfZT5YzpxwFLYp8hBm2A@public.gmane.org>
2015-03-02 15:42       ` Stefan Seefeld
     [not found]         ` <54F484D4.8080501-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
2015-03-03 12:22           ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150302045403.GE29409@voom.fritz.box \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=stefan-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.