linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] sbc8548: Add device tree source for Wind River SBC8548 board
Date: Sat, 22 Dec 2007 13:05:31 +1100	[thread overview]
Message-ID: <20071222020531.GA7891@localhost.localdomain> (raw)
In-Reply-To: <20071221172023.GA23220@windriver.com>

On Fri, Dec 21, 2007 at 12:20:24PM -0500, Paul Gortmaker wrote:
> In message: Re: [PATCH 2/3] sbc8548: Add device tree source for Wind River SBC8548 board
> on 21/12/2007 Kumar Gala wrote:
> 
> >
> > On Dec 21, 2007, at 12:43 AM, Paul Gortmaker wrote:
> >
> >> This adds the device tree source for the Wind River SBC8548 board. 
> 
> [...]
> 
> > mind looking at converting this to a dts-v1 format?
> >
> > - k
> 
> I figured there might be value in having it as a separate commit, seeing
> as there aren't that many other dts-v1 as a reference (yet).  Not sure
> if I've got all the v1 type changes in that you had in mind, but I fed
> it through the latest dtc from git and fed it to the board and it still
> seems happy with it.

There are really only two changes with dts-v1.
	1) All integers become C-style, so, decimal by default with
leading 0, 0x or 0b for octal/hex/binary.  d# h# o# are no longer
supported.
	2) References to pths must be writte as &{/some/node/or/other}
instead of &/some/node/or/other.  References to labels remain fine as
just &label.

The explicit new source version isn't because the format changes are
large, just because there was no way to make them in a
backwards-compatible way.

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

  reply	other threads:[~2007-12-22  2:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21  6:43 [PATCH 0/3] Powerpc support for SBC8548 board Paul Gortmaker
     [not found] ` <567bfb934387ec732a4c52c26efd17856f5144fd.1198217984.git.paul.gortmaker@windriver.com>
2007-12-21  6:43   ` [PATCH 1/3] sbc8548: Add basic support for Wind River SBC8548 as powerpc Paul Gortmaker
2007-12-21 15:32     ` Kumar Gala
2008-01-07 22:27       ` Paul Gortmaker
2008-01-07 22:40       ` [PATCH] sbc85xx: remove PCI exclude device for sbc8548/sbc8560 Paul Gortmaker
2008-01-08  6:15         ` Kumar Gala
     [not found]   ` <a9ccacef3dee433c1bc90cd73ef84ba26a2870bb.1198217984.git.paul.gortmaker@windriver.com>
2007-12-21  6:43     ` [PATCH 2/3] sbc8548: Add device tree source for Wind River SBC8548 board Paul Gortmaker
2007-12-21 15:33       ` Kumar Gala
2007-12-21 17:20         ` Paul Gortmaker
2007-12-22  2:05           ` David Gibson [this message]
     [not found]   ` <e954b4255110df8c9ac5c636af4ea4394ea1e953.1198217984.git.paul.gortmaker@windriver.com>
2007-12-21  6:43     ` [PATCH 3/3] sbc8548: Add default .config file for Wind River SBC8548 Paul Gortmaker

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=20071222020531.GA7891@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paul.gortmaker@windriver.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 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).