From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pantelis Antoniou Subject: [RFC] Introducing yamldt, a yaml to dtb compiler Date: Thu, 27 Jul 2017 19:49:11 +0300 Message-ID: <1501174151.1055.8.camel@hp800z> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=konsulko.com; s=google; h=message-id:subject:from:to:cc:date:mime-version :content-transfer-encoding; bh=lRc3u5J4TRmN2qA7iBRWqnPDNDmt/p9TtrjXViW2V5M=; b=rj+gbcR8SnwMqoDU7Ju6ObO6xoVD0QkokhTTTI2zCj6a5IqV7P32HEPRGRAjDPaCVA LqRa7FASBVJypswQkaqLGbOHMbiSmZdug/coLLTyqBqMSFzDbkmFQE6FSCwByGi3WxKy 2we4Z36xrERlKeVeXxZczwFJjwatNlGfwnPEA= Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Frank Rowand Cc: Grant Likely , David Gibson , Tom Rini , Rob Herring , Franklin S Cooper Jr , Matt Porter , Simon Glass , Phil Elwell , Geert Uytterhoeven , Marek Vasut , Devicetree Compiler , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Hi all, This is a project I've been working on lately and it's finally in a usuable form. I'm introducing yamldt. A YAML to DT blob generator/compiler, utilizing a YAML schema that is functionaly equivalent to DTS and supports all DTS features. yamldl parses a device tree description (source) file in YAML format and outputs a (bit-exact if the -C option is used) device tree blob. A DT aware YAML schema is a good fit as a DTS syntax alternative. YAML is a human-readable data serialization language, and is expressive enough to cover all DTS source features. Simple YAML files are just key value pairs that are very easy to parse, even without using a formal YAML parser. For instance YAML in restricted environments may simple be appending a few lines of text in a given YAML file. The parsers of YAML are very mature, as it has been released in 2001. It is in wide-spread use and schema validation tools are available. YAML support is available for every major programming language. Data in YAML can easily be converted to/form other format that a particular tool that we may use in the future understands. More importantly YAML offers (an optional) type information for each data, which is IMHO crucial for thorough validation and checking against device tree bindings (when they will be converted to a machine readable format, preferably YAML). For more take a look here. https://github.com/pantoniou/yamldt I am eagerly awaiting for your comments. Regards -- Pantelis -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html