From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Nava kishore Manne <nava.manne@xilinx.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Srinivas Goud <sgoud@xilinx.com>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: Query on DT overlay support.
Date: Thu, 23 Mar 2017 12:02:25 -0700 [thread overview]
Message-ID: <58D41BC1.9070203@gmail.com> (raw)
In-Reply-To: <CAL_JsqL97FvXKc4ZjG5B28tpe=9CvvSY9+zgE7iN8moOz2OHVQ@mail.gmail.com>
(Adding Pantelis and dgibson to cc.)
On 03/23/17 11:32, Rob Herring wrote:
> On Thu, Mar 23, 2017 at 8:22 AM, Nava kishore Manne
> <nava.manne@xilinx.com> wrote:
>> Hi,
>>
>>
>>
>> This mail is regarding the DT overlay support in the Linux
>> kernel
>>
>> I am able to make the device-tree overlay work out of box by
>> using my own dtc complier (I mean I used the dtc compiler
>>
>> Available here
>> http://www.embedded-things.com/bbb/patching-the-device-tree-compiler-for-ubuntu/
>> )
>>
>> When can I expect the same changes in the scripts/dtc in
>> mainline????
>>
>> In case of any support needed for testing I can help on
>> testing the same I works in Xilinx and we had a lot of combinations to test
>> overlay J
>
> It's already there. Landed in 4.11.
>
> Rob
>
One dtc feature that is still missing is what Pantelis calls "syntatic sugar".
His patch for that has not yet been accepted into the dtc project if I have
been following along correctly.
Without the syntactic sugar, the source .dts has to expose the details
of the fragment and __overlay__ nodes.
-Frank
next prev parent reply other threads:[~2017-03-23 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 13:22 Query on DT overlay support Nava kishore Manne
[not found] ` <C89496FEAE474D468F30D558A9468D9F26D7986C-4lKfpRxZ5enZMOc0yg5rMog+Gb3gawCHQz34XiSyOiE@public.gmane.org>
2017-03-23 18:32 ` Rob Herring
2017-03-23 18:32 ` Rob Herring
2017-03-23 19:02 ` Frank Rowand [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-23 13:26 Nava kishore Manne
2017-03-23 13:26 ` Nava kishore Manne
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=58D41BC1.9070203@gmail.com \
--to=frowand.list@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nava.manne@xilinx.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
--cc=sgoud@xilinx.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.