linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: FDT for MPC5200, CPU revision, MSCAN
Date: Fri, 20 Apr 2007 09:21:51 +0200	[thread overview]
Message-ID: <46286A0F.9080608@grandegger.com> (raw)
In-Reply-To: <462864CA.7050601@grandegger.com>

Wolfgang Grandegger wrote:
> Hello,
> 
> is there a way to distinguish the CPU revision (Rev.A vs. Rev.B) of the 
> MPC5200, preferably at run time? Or should this be defined in the FDT?
> I ask, because some settings depend on the CPU revision due to hardware 
> bugs, like the clock source used for MSCAN.

I found the information here:

$ cat Documentation/powerpc/mpc52xx-device-tree-bindings.txt
...
The 5200B is almost the same as the 5200, but not quite.  It fixes
silicon bugs and it adds a small number of enhancements.  Most of the
devices either provide exactly the same interface as on the 5200.  A few
devices have extra functions but still have a backwards compatible mode.
To express this infomation as completely as possible, 5200B device trees
should have two items in the compatible list;
"mpc5200b-<device>\0mpc5200-<device>".  It is *strongly* recommended
that 5200B device trees follow this convention (instead of only listing
the base mpc5200 item).
...

Sorry for the noise.

Wolfgang.

  reply	other threads:[~2007-04-20  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20  6:59 FDT for MPC5200, CPU revision, MSCAN Wolfgang Grandegger
2007-04-20  7:21 ` Wolfgang Grandegger [this message]
2007-04-20 14:02   ` Grant Likely
2007-04-20 16:11     ` Wolfgang Grandegger

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=46286A0F.9080608@grandegger.com \
    --to=wg@grandegger.com \
    --cc=linuxppc-embedded@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).