linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Ted Peters <ted.peters@freescale.com>
Subject: Re: [PATCH] powerpc/85xx: Add P2020DS board support
Date: Wed, 15 Apr 2009 20:50:09 +0400	[thread overview]
Message-ID: <20090415165009.GA10214@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1239810564-8403-1-git-send-email-galak@kernel.crashing.org>

On Wed, Apr 15, 2009 at 10:49:24AM -0500, Kumar Gala wrote:
> From: Ted Peters <ted.peters@freescale.com>
> 
> The P2020 is a dual e500v2 core based SOC with:
> * 3 PCIe controllers
> * 2 General purpose DMA controllers
> * 2 sRIO controllers
> * 3 eTSECS
> * USB 2.0
> * SDHC
> * SPI, I2C, DUART
> * enhanced localbus
> * and optional Security (P2020E) security w/XOR acceleration
> 
> The p2020 DS reference board is pretty similar to the existing MPC85xx
> DS boards and has a ULI 1575 connected on one of the PCIe controllers.
> 
> Signed-off-by: Ted Peters <Ted.Peters@freescale.com>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
[...]
> +	soc@ffe00000 {
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +		device_type = "soc";
> +		compatible = "simple-bus";

Sorry for bringing this up again... But can we decide on soc's
compatible scheme and finally remove the device_type = "soc"
for new boards? "fsl,p2020-soc", "fsl,soc", "simple-bus" maybe?

Thanks,

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

  parent reply	other threads:[~2009-04-15 16:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 15:49 [PATCH] powerpc/85xx: Add P2020DS board support Kumar Gala
2009-04-15 15:59 ` Timur Tabi
2009-04-15 16:17   ` Kumar Gala
2009-04-15 16:50 ` Anton Vorontsov [this message]
2009-04-15 17:22   ` Kumar Gala
2009-04-15 17:54     ` Anton Vorontsov

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=20090415165009.GA10214@oksana.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ted.peters@freescale.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).