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] sbc834x: Add device tree source for Wind River SBC834x board.
Date: Thu, 10 Jan 2008 13:06:44 +1100	[thread overview]
Message-ID: <20080110020644.GA17816@localhost.localdomain> (raw)
In-Reply-To: <b9cda8aa586eba852f0763db2347d545a5b31be6.1199850992.git.paul.gortmaker@windriver.com>

On Wed, Jan 09, 2008 at 12:49:31AM -0500, Paul Gortmaker wrote:
> This adds the device tree source for the Wind River SBC834x board.
> It is based on the MPC834x_MDS DTS, with the biggest difference being
> the lack of BCSR and the PCI2 that the MDS gets via the PIB. That,
> and this file is also dts-v1 format.
> 
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
>  arch/powerpc/boot/dts/sbc8349.dts |  247 +++++++++++++++++++++++++++++++++++++
>  1 files changed, 247 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/powerpc/boot/dts/sbc8349.dts b/arch/powerpc/boot/dts/sbc8349.dts

[snip]
> +		wdt@200 {
> +			device_type = "watchdog";
> +			compatible = "mpc83xx_wdt";

Grah!  Hasn't someone fixed this so that the driver doesn't need the
crap device_type?

[snip]
> +		spi@7000 {
> +			device_type = "spi";
> +			compatible = "fsl_spi";

And again here.

[snip]
> +		usb@22000 {
> +			device_type = "usb";
> +			compatible = "fsl-usb2-mph";

And here.

[snip
> +		/* May need to remove if on a part without crypto engine */
> +		crypto@30000 {
> +			device_type = "crypto";
> +			model = "SEC2";
> +			compatible = "talitos";

I'm almost certain this one was fixed, hasn't it been merged yet?

[snip]
> +		ipic: pic@700 {

By generic names best practice this should be
"interrupt-controller@700", although that's probably not your error.

-- 
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-01-10  2:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09  5:49 [PATCH 0/3] Powerpc support for SBC834x board Paul Gortmaker
     [not found] ` <ac667c5b2e8acb0f92d31b8e3b590432bb939df9.1199850992.git.paul.gortmaker@windriver.com>
2008-01-09  5:49   ` [PATCH 1/3] sbc834x: Add support for Wind River SBC834x boards Paul Gortmaker
2008-01-09  7:01     ` Stephen Rothwell
2008-01-15 14:13       ` Kumar Gala
     [not found]   ` <b9cda8aa586eba852f0763db2347d545a5b31be6.1199850992.git.paul.gortmaker@windriver.com>
2008-01-09  5:49     ` [PATCH 2/3] sbc834x: Add device tree source for Wind River SBC834x board Paul Gortmaker
2008-01-10  2:06     ` David Gibson [this message]
     [not found]   ` <01993202680f1b46bad03b1836e730e297d353fb.1199850992.git.paul.gortmaker@windriver.com>
2008-01-09  5:49     ` [PATCH 3/3] sbc834x: Add default config file for Wind River SBC8349 board 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=20080110020644.GA17816@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).