Devicetree
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Jon Loeliger <jdl-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: [Fwd: Re: [U-Boot-Users] using a flat device tree to drive u-boot config]
Date: Thu, 31 Jul 2008 11:15:46 +1000	[thread overview]
Message-ID: <20080731011546.GC11727@yookeroo.seuss> (raw)
In-Reply-To: <4890D9DA.1010603-KZfg59tc24xl57MIdRCFDg@public.gmane.org>

On Wed, Jul 30, 2008 at 04:15:06PM -0500, Jon Loeliger wrote:
> David Gibson wrote:
>
>> Heh, I guess with the new dtc release out, I should have a serious
>> look at getting the long-mooted expression support ready to merge.
>
>
> Well, I'm likely to work in this direction too.
>
> I think one of the first things that we might do
> is to convert the DTC to a two pass tool where the
> first pass just parses and creates an internal node
> structure, and the second pass traverses it writing
> it out.

Um.. I'm not really sure what you mean by this.  The most obvious
meaning to me, we already do...

-- 
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:[~2008-07-31  1:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 14:27 [Fwd: Re: [U-Boot-Users] using a flat device tree to drive u-boot config] Jon Loeliger
     [not found] ` <488F28BF.6030902-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2008-07-30  1:19   ` David Gibson
     [not found]     ` <20080730011908.GB19216-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-07-30 21:15       ` Jon Loeliger
     [not found]         ` <4890D9DA.1010603-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2008-07-31  1:15           ` 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=20080731011546.GC11727@yookeroo.seuss \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
    --cc=jdl-KZfg59tc24xl57MIdRCFDg@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