From: Julia Lawall <julia.lawall-L2FTfq7BK8M@public.gmane.org>
To: Grant Likely <glikely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: Frank Rowand
<frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Matt Porter <mporter-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>,
Behan Webster
<behanw-k/hB3zQhLwledRVtV/plodBPR1lH4CV8@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>,
Pantelis Antoniou
<pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: device tree verification tools
Date: Fri, 4 Nov 2016 22:08:50 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1611042208270.2019@hadrien> (raw)
In-Reply-To: <CACxGe6vFmHRtE+=rJnsWrm7BGqqXBXq8FJq_T0r5deGP5pnCYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, 4 Nov 2016, Grant Likely wrote:
> On Fri, Nov 4, 2016 at 2:03 PM, Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > On 07/26/16 13:43, Julia Lawall wrote:
> >> I saw that there will be a microconference on device trees at Linux
> >> Plumbers. Unfortunately, I won't be able to attend, due to another event
> >> at the same time, but I was wondering what is the status of verification
> >> tools for device tree specifications?
> >>
> >> thanks,
> >> julia
> >>
> >
> > Hi Julia,
> >
> > Grant Likely is breathing new life into the verification effort.
>
> Hey Julia,
>
> The status is: there are no verification tools for dt. :-)
>
> I'm /hoping/ to fix that. I've started experimenting with a grammar
> for DT schema and writing a schema validation tool, but this isn't my
> domain of expertise. I could certainly use your insight. You can see
> some of what I've been playing with in this git tree:
>
> https://github.com/glikely/dtgendoc
>
> It is little more than prototype code, and nothing has been formalized
> yet. I'm open to taking other approaches.
Thanks for the pointer. I haven't had a chance to look into it, but I
hope to get to it soon.
julia
>
> Cheers,
> g.
>
>
> >
> > -Frank
>
prev parent reply other threads:[~2016-11-04 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 20:43 device tree verification tools Julia Lawall
2016-08-03 19:49 ` Frank Rowand
2016-08-03 23:42 ` Stewart Smith
[not found] ` <87vazh8ln8.fsf-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-08-04 5:18 ` Julia Lawall
2016-08-09 3:34 ` Stewart Smith
2016-11-04 20:03 ` Frank Rowand
[not found] ` <581CE982.60605-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-11-04 20:07 ` Grant Likely
[not found] ` <CACxGe6vFmHRtE+=rJnsWrm7BGqqXBXq8FJq_T0r5deGP5pnCYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-04 21:08 ` Julia Lawall [this message]
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=alpine.DEB.2.20.1611042208270.2019@hadrien \
--to=julia.lawall-l2ftfq7bk8m@public.gmane.org \
--cc=behanw-k/hB3zQhLwledRVtV/plodBPR1lH4CV8@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=glikely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=mporter-OWPKS81ov/FWk0Htik3J/w@public.gmane.org \
--cc=pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).