devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: Devicetree Discuss
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: diff-ing two device tree
Date: Fri, 9 Sep 2011 10:38:16 +1000	[thread overview]
Message-ID: <20110909003816.GX30278@yookeroo.fritz.box> (raw)
In-Reply-To: <20110908182753.GK2967-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>

On Thu, Sep 08, 2011 at 11:27:53AM -0700, Grant Likely wrote:
> On Thu, Sep 08, 2011 at 10:31:59AM -0500, Kumar Gala wrote:
> > Do we have a utility that can diff two device trees.  What I'm
> > looking for is something that has some context awareness.  It can
> > deal with (p)handle values being different, properties in a node in
> > different order, etc.
> 
> I hacked something together which sorts the two trees and then diffs
> the output, but that is rather a hack.

You mean like the "dtdiff" script that's in the dtc repo...

>  I don't think anyone has put
> together a context sensitive dt diff tool.

What would you envisage this tool doing?

-- 
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

      parent reply	other threads:[~2011-09-09  0:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 15:31 diff-ing two device tree Kumar Gala
     [not found] ` <66A9107F-D3BF-4900-99FA-6E1594571BA9-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2011-09-08 17:41   ` Simon Glass
2011-09-08 18:27   ` Grant Likely
     [not found]     ` <20110908182753.GK2967-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-09-09  0:38       ` David Gibson [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=20110909003816.GX30278@yookeroo.fritz.box \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@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 NNTP newsgroup(s).