All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <dwg@au1.ibm.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC][PATCH 6/8] Walnut DTS
Date: Wed, 18 Jul 2007 11:02:21 +1000	[thread overview]
Message-ID: <20070718010221.GA21877@localhost.localdomain> (raw)
In-Reply-To: <1184176531.32199.81.camel@weaponx.rchland.ibm.com>

On Wed, Jul 11, 2007 at 12:55:31PM -0500, Josh Boyer wrote:
> On Wed, 2007-07-11 at 19:49 +0200, Segher Boessenkool wrote:
> > > +	UIC0: interrupt-controller0 {
> > 
> > Why not just "interrupt-controller"?
> 
> Copy/paste error from Ebony DTS, which has multiple UICs.  Will fix.
> 
> > 
> > > +		#address-cells = <0>;
> > > +		#size-cells = <0>;
> > 
> > No need for these.
> 
> Ok.
> 
> > >
> > > +	plb {
> > > +		ranges;
> > 
> > Please make the valid address ranges explicit here.
> 
> Meaning what exactly?  I thought just specifying "ranges;" simply said
> "the addresses from this node don't have any translation from the parent
> node" (or something like that).
> 
> > 
> > > +		SDRAM0: memory-controller {
> > > +			compatible = "ibm,sdram-405gp", "ibm,sdram-440gp";
> > 
> > It's a bit weird to mention 440 here, since 405 is older.
> > Not a real problem, but if you still can change all relevant
> > OS code and device trees, I'd swap it around (make 440 trees
> > include the 405 "compatible" value).  Can you still do that
> > or is there a too big installed base already?
> 
> The installed base for 440 exists of exactly 1 completely non-functional
> board ;).  I can change it.

And I don't think we even actually look at this compatible property in
practice.

-- 
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:[~2007-07-23  0:47 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 13:52 [RFC][PATCH 0/8] arch/powerpc support for Walnut Board Josh Boyer
2007-07-11 13:53 ` [RFC][PATCH 1/8] 4xx Kconfig cleanup Josh Boyer
2007-07-11 13:55 ` [RFC][PATCH 2/8] 4xx boot wrapper reworks Josh Boyer
2007-07-11 13:56 ` [RFC][PATCH 3/8] 4xx MMU Josh Boyer
2007-07-11 20:56   ` Arnd Bergmann
2007-07-11 21:15     ` Josh Boyer
2007-07-12  7:09     ` Kumar Gala
2007-07-12 12:40       ` Josh Boyer
2007-07-11 13:57 ` [RFC][PATCH 4/8] 4xx decrementer fixes Josh Boyer
2007-07-11 13:58 ` [RFC][PATCH 5/8] Fix 4xx build Josh Boyer
2007-07-11 21:00   ` Arnd Bergmann
2007-07-11 13:59 ` [RFC][PATCH 6/8] Walnut DTS Josh Boyer
2007-07-11 14:26   ` Stefan Roese
2007-07-11 14:37     ` Josh Boyer
2007-07-11 17:49   ` Segher Boessenkool
2007-07-11 17:55     ` Josh Boyer
2007-07-11 18:07       ` Segher Boessenkool
2007-07-18  1:02       ` David Gibson [this message]
2007-07-12 15:13     ` Yoder Stuart-B08248
2007-07-16 14:34       ` Segher Boessenkool
2007-07-16 21:47         ` Benjamin Herrenschmidt
2007-07-16 21:55           ` Scott Wood
2007-07-16 22:11             ` Benjamin Herrenschmidt
2007-07-16 22:18               ` Scott Wood
2007-07-16 22:34                 ` Benjamin Herrenschmidt
2007-07-16 21:55           ` Yoder Stuart-B08248
2007-07-16 22:12             ` Benjamin Herrenschmidt
2007-07-17  2:39           ` Josh Boyer
2007-07-17 14:26             ` Segher Boessenkool
2007-07-17 14:15           ` Segher Boessenkool
2007-07-17 21:25             ` Benjamin Herrenschmidt
2007-07-17 22:25               ` Scott Wood
2007-07-17 22:58                 ` Benjamin Herrenschmidt
2007-07-18 13:53                 ` Segher Boessenkool
2007-07-18 16:47                   ` Scott Wood
2007-07-19 16:54                     ` Segher Boessenkool
2007-07-18 13:48               ` Segher Boessenkool
2007-07-11 14:02 ` [RFC][PATCH 7/8] Walnut defconfig Josh Boyer
2007-07-11 14:03 ` [RFC][PATCH 8/8] Walnut board support Josh Boyer
2007-07-11 14:04 ` [RFC][PATCH 9/8] Walnut zImage wrapper Josh Boyer

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=20070718010221.GA21877@localhost.localdomain \
    --to=dwg@au1.ibm.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.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 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.