linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Zhang Wei-r63237 <Wei.Zhang@freescale.com>
Subject: Re: Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D
Date: Thu, 24 May 2007 10:52:15 +1000	[thread overview]
Message-ID: <20070524005215.GA14320@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0705230916170.535@localhost.localdomain>

On Wed, May 23, 2007 at 09:21:48AM -0500, Kumar Gala wrote:
> On Wed, 23 May 2007, Zhang Wei-r63237 wrote:
> 
> > > So I'm taking the boot/dts/mpc8641_hpcn.dts and producing a new
> > > mpc8641D_umem.dts with the following addition to the soc.
> > >
> > > srio@c0000 {
> > >                 device_type = "srio";
> > >                 compatible = "86xx,85xx";

This is quite tangential to the rest of this discussion, but "xx"s in
compatible properties always alarm me if they're the only thing
listed.  It's generally best to give a precise model, then a more
general one: the trade-off is that if you're too precise, it's fairly
easy for the driver to workaround by recognizing and binding to
multiple compatible strings, whereas if you're too general you risk
the driver not being able to determine whether it needs a
model-specific workaround or not.

-- 
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-05-24  0:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 19:38 Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D Phil Terry
2007-05-22 20:08 ` Segher Boessenkool
2007-05-22 20:09 ` Timur Tabi
2007-05-22 23:05 ` Arnd Bergmann
2007-05-24  6:48   ` Porting RapidIO from ppc arch to powerpc arch in support ofMPC8641D Zhang Wei-r63237
2007-05-24  9:19     ` Arnd Bergmann
2007-05-24  9:44       ` Zhang Wei-r63237
2007-05-24 11:27         ` Arnd Bergmann
2007-05-23 13:26 ` Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D Zhang Wei-r63237
2007-05-23 13:32   ` Mark A. Greer
2007-05-23 14:03     ` Zhang Wei-r63237
2007-05-23 15:42       ` Phil Terry
2007-05-23 15:53       ` Mark A. Greer
2007-05-23 15:54       ` Phil Terry
2007-05-23 14:21   ` Kumar Gala
2007-05-23 15:37     ` Phil Terry
2007-05-23 16:05       ` Segher Boessenkool
2007-05-23 16:20         ` Phil Terry
2007-05-23 16:20           ` Kumar Gala
2007-05-23 16:43             ` Phil Terry
2007-05-23 23:17               ` Segher Boessenkool
2007-05-23 23:05           ` Segher Boessenkool
2007-05-24  7:31       ` Porting RapidIO from ppc arch to powerpc arch in support ofMPC8641D Zhang Wei-r63237
2007-05-23 16:00     ` Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D Segher Boessenkool
2007-05-23 16:13       ` Phil Terry
2007-05-24  0:52     ` 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=20070524005215.GA14320@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=Wei.Zhang@freescale.com \
    --cc=galak@kernel.crashing.org \
    --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 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).