linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Add AMCC Glacier 460GT eval board dts
Date: Fri, 21 Mar 2008 20:00:31 +1100	[thread overview]
Message-ID: <1206090031.8420.67.camel@pasglop> (raw)
In-Reply-To: <1205943310-26323-1-git-send-email-sr@denx.de>


On Wed, 2008-03-19 at 17:15 +0100, Stefan Roese wrote:
> +               cpu@0 {
> +                       device_type = "cpu";
> +                       model = "PowerPC,460GT";
> +                       reg = <0>;
> 

I wonder if we should do something here to differenciate the SoC chip
from the core. After all, all those 4xx mostly have the same core (there
are 2 or 3 revisions of the core maybe ...) but they tend to have all
different PVR which is a pain and won't scale...

Maybe AMCC could do something in HW (splitting the PVR from whatever
indicates what "chip" it is, and keeping the PVR purely for the core
rev) but I'm wondering if we should also do something in the DTS..
Stefan can you talk to your AMCC contacts about this ?

As for the DTS, maybe a "compatible" property in the CPU might make some
sense with a content along the lines of "ppc440x6" or whatever rev of
the 440 core it is.

What do you think ?

Cheers,
Ben.

  reply	other threads:[~2008-03-21  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 16:15 [PATCH] [POWERPC] Add AMCC Glacier 460GT eval board dts Stefan Roese
2008-03-21  9:00 ` Benjamin Herrenschmidt [this message]
2008-03-21 10:54   ` Stefan Roese
2008-03-21 12:24     ` Josh Boyer
2008-03-21 17:28       ` Segher Boessenkool
2008-03-22  1:14         ` Josh Boyer
2008-03-21 11:46   ` Segher Boessenkool
2008-03-21 11:51     ` Benjamin Herrenschmidt
2008-03-21 11:58       ` Segher Boessenkool

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=1206090031.8420.67.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sr@denx.de \
    /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).