From: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Frank Rowand <frowand.list@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
David Gibson <david@gibson.dropbear.id.au>,
Tom Rini <trini@konsulko.com>,
Franklin S Cooper Jr <fcooper@ti.com>,
Matt Porter <mporter@konsulko.com>,
Simon Glass <sjg@chromium.org>,
Phil Elwell <philip.j.elwell@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Marek Vasut <marex@denx.de>,
Devicetree Compiler <devicetree-compiler@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] yamldt v0.5, now a DTS compiler too
Date: Mon, 2 Oct 2017 10:36:09 +0300 [thread overview]
Message-ID: <9E7F3A15-C60F-4CC9-9063-9DDAB0FCD451@konsulko.com> (raw)
In-Reply-To: <CAL_Jsq+Hxjf8PecU+ZpCoFqbKAYJtzHpFco2Wsi_KT499fb-=g@mail.gmail.com>
> On Oct 2, 2017, at 01:00 , Rob Herring <robherring2@gmail.com> wrote:
>
> On Thu, Sep 28, 2017 at 2:58 PM, Pantelis Antoniou
> <pantelis.antoniou@konsulko.com> wrote:
>> Hello again,
>>
>> Significant progress has been made on yamldt and is now capable of
>> not only generating yaml from DTS source but also compiling DTS sources
>> and being almost fully compatible with DTC.
>
> Can you quantify "almost”?
The —sort option and /include-bin/ doesn’t work yet.
It’s a day or so to add them but there are no kernel dtb files that rely on them.
>
>> Compiling the kernel's DTBs using yamldt is as simple as using a
>> DTC=yamldt.
>
> Good.
>
>>
>> Error reporting is accurate and validation against a YAML based schema
>> works as well. In a short while I will begin posting patches with
>> fixes on bindings and DTS files in the kernel.
>
> What I would like to see is the schema format posted for review.
>
It is based on your binding schema you’ve posted but tweaked slightly to
be parseable by the YAML subset that matches the DTS style.
In particular bare sequences do not map to DT at all, so:
- name: foo
is changed to
name: foo
And so on.
> I would also like to see the bindings for top-level compatible strings
> (aka boards) as an example. That's something that's simple enough that
> I'd think we could agree on a format and start moving towards defining
> board bindings that way.
>
I’ll see what I can do.
> Rob
Regards
— Pantelis
next prev parent reply other threads:[~2017-10-02 7:36 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 19:58 [RFC] yamldt v0.5, now a DTS compiler too Pantelis Antoniou
2017-09-28 19:58 ` Pantelis Antoniou
2017-10-01 22:00 ` Rob Herring
2017-10-01 22:00 ` Rob Herring
2017-10-02 7:36 ` Pantelis Antoniou [this message]
2017-10-02 19:46 ` Pantelis Antoniou
2017-10-03 7:17 ` Geert Uytterhoeven
2017-10-03 7:33 ` Pantelis Antoniou
2017-10-03 13:18 ` Rob Herring
2017-10-03 14:13 ` Pantelis Antoniou
2017-10-03 14:13 ` Pantelis Antoniou
2017-10-03 17:13 ` Rob Herring
2017-10-03 17:39 ` Pantelis Antoniou
2017-10-03 17:39 ` Pantelis Antoniou
2017-10-06 13:55 ` Rob Herring
2017-10-06 13:55 ` Rob Herring
2017-10-07 10:23 ` Pantelis Antoniou
2017-10-08 23:08 ` Frank Rowand
2017-10-08 23:08 ` Frank Rowand
2017-10-09 0:00 ` David Gibson
2017-10-09 0:00 ` David Gibson
2017-10-09 15:07 ` Pantelis Antoniou
2017-10-09 15:07 ` Pantelis Antoniou
2017-10-10 1:50 ` David Gibson
2017-10-10 15:19 ` Pantelis Antoniou
2017-10-10 15:19 ` Pantelis Antoniou
2017-10-11 3:49 ` David Gibson
2017-10-11 3:49 ` David Gibson
2017-10-09 14:59 ` Pantelis Antoniou
2017-10-20 17:46 ` Grant Likely
2017-10-20 17:46 ` Grant Likely
2017-10-20 19:16 ` Pantelis Antoniou
2017-10-22 17:54 ` Grant Likely
2017-10-22 17:54 ` Grant Likely
2017-10-22 18:23 ` Pantelis Antoniou
2017-10-22 18:23 ` Pantelis Antoniou
2017-10-22 19:13 ` Grant Likely
2017-10-22 19:13 ` Grant Likely
2017-10-23 10:08 ` Pantelis Antoniou
2017-10-23 10:08 ` Pantelis Antoniou
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=9E7F3A15-C60F-4CC9-9063-9DDAB0FCD451@konsulko.com \
--to=pantelis.antoniou@konsulko.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fcooper@ti.com \
--cc=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=mporter@konsulko.com \
--cc=philip.j.elwell@gmail.com \
--cc=robherring2@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
/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.