All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2 6/7] Holly DTS
Date: Sat, 05 May 2007 13:12:26 -0500	[thread overview]
Message-ID: <1178388746.3393.47.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <e1d22829fe3f12509018791541073706@kernel.crashing.org>

On Sat, 2007-05-05 at 19:21 +0200, Segher Boessenkool wrote:
> > +/ {
> > +	model = "ppc750-tsi109";
> 
> "model" should be something really specific; typically
> a (unique!) model number.  This means you can't use the
> same device tree for Holly and Hickory (but there are
> more reasons for that; see below).
> 
> > +	compatible = "ppc750-tsi";
> 
> The needs to be more specific as well; "ibm,holly"
> or something.

Why?  Holly and Hickory share the same memory map and devices.  The only
thing that differs from what I can tell is the actual CPU itself.

> 
> > +		PowerPC,750@0 {
> 
> Needs to be PowerPC,750CL etc.
> 
> > +			name = "PowerPC,750";
> 
> You don't need to specify "name" in modern DTS.

Ok.

> > +  	tsi109@c0000000 {
> > +		device_type = "tsi-bridge";
> 
> Don't put a "device_type" here, it is useless
> (and undefined).  There are more like this, but
> perhaps Linux (wrongly) probes on "device_type"
> for those, so the kernel would need updating
> first.

It's not useless.  The TSI code probes by device_type all over the
place.  Do you have an example of how to probe for something like this
without using device_type?

> > +		bus-frequency = <0>;
> 
> 0?

Can likely go.

> 
> > +		ethernet@6200 {
> > +			model = "TSI-ETH";
> 
> "model" should be an exact model name.  If you don't
> have one, just leave out the "model" property.

OK.

> 
> > +			address = [ 00 0d 60 f4 3f 04 ];
> 
> "local-mac-address" instead.  And you don't want to
> hardcode one specific address like this; just keep
> it open so if the bootloader fails to fill it in you
> notice.  If the bootloader cannot do that, just leave
> out this property completely (not compliant, but neither
> is filling in the wrong value).

Ok.

> 
> > +		serial@7808 {
> > +			reg-shift = <0>;
> 
> This is the default value so you can leave it out.

Ok.

> 
> > +	  	MPIC: pic@7400 {
> > +			built-in;
> 
> Why say this for MPIC only, not for most other nodes?
> What binding defines "built-in", anyway?

http://playground.sun.com/1275/bindings/chrp/chrp1_8a.ps

Page 34.

> 
> > +				/*--------------------------------------------+
> > +				| AD19.
> > +				+--------------------------------------------*/
> > +				1800 0 0 1 &RT0 26 0
> > +				1800 0 0 2 &RT0 27 0
> > +				1800 0 0 3 &RT0 24 0
> > +				1800 0 0 4 &RT0 25 0
> > +
> > +				2000 0 0 1 &RT0 27 0
> > +				2000 0 0 2 &RT0 24 0
> > +				2000 0 0 3 &RT0 25 0
> > +				2000 0 0 4 &RT0 26 0
> > +				>;
> 
> You forgot to say "AD20" ;-)

Heh, ok.

> 
> > +	chosen {
> > +		linux,platform = <0>;
> > +		linux,initrd-start = <0>;
> > +		linux,initrd-end = <0>;
> 
> Do you need to set those zero properties?

Perhaps not.  I'll look at that.

josh

  reply	other threads:[~2007-05-05 18:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05 16:13 [PATCH v2 0/7] Add support for 750CL Holly board Josh Boyer
2007-05-05 16:14 ` [PATCH v2 0/1] Add tsi108_pci.h for common PCI functions Josh Boyer
2007-05-05 16:15 ` [PATCH v2 2/7] Generalize tsi108 PHY types Josh Boyer
2007-05-05 16:16 ` [PATCH v2 3/7] Generalize TSI 108 PCI setup Josh Boyer
2007-05-05 16:17 ` [PATCH v2 4/7] Add support for 750CL Holly board Josh Boyer
2007-05-07  4:22   ` Paul Mackerras
2007-05-07 10:32     ` Josh Boyer
2007-05-05 16:19 ` [PATCH v2 5/7] Holly defconfig Josh Boyer
2007-05-05 16:20 ` [PATCH v2 6/7] Holly DTS Josh Boyer
2007-05-05 17:21   ` Segher Boessenkool
2007-05-05 18:12     ` Josh Boyer [this message]
2007-05-05 20:44       ` Segher Boessenkool
2007-05-05 21:36         ` Josh Boyer
2007-05-06  0:47           ` Segher Boessenkool
2007-05-05 19:13     ` Olof Johansson
2007-05-05 19:46       ` Josh Boyer
2007-05-05 20:51         ` Segher Boessenkool
2007-05-05 20:49       ` Segher Boessenkool
2007-05-07 17:50         ` Loeliger Jon-LOELIGER
2007-05-09  0:49           ` David Gibson
2007-05-09  7:40             ` Stephen Rothwell
2007-05-09 10:29             ` Josh Boyer
2007-05-09 15:28               ` Segher Boessenkool
2007-05-10 23:54                 ` David Gibson
2007-05-12 12:02                   ` Segher Boessenkool
2007-05-14  0:24                     ` David Gibson
2007-05-14 12:33                       ` Segher Boessenkool
2007-05-14 16:16                         ` Scott Wood
2007-05-06  0:40     ` David Gibson
2007-05-07 13:11       ` Josh Boyer
2007-05-08  0:06         ` David Gibson
2007-05-05 16:20 ` [PATCH v2 7/7] Holly bootwrapper 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=1178388746.3393.47.camel@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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.