linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Wolfgang Grandegger" <wg@grandegger.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: FDT for MPC5200, CPU revision, MSCAN
Date: Fri, 20 Apr 2007 08:02:51 -0600	[thread overview]
Message-ID: <528646bc0704200702i328ba9dbvc62473e5a634d5ac@mail.gmail.com> (raw)
In-Reply-To: <46286A0F.9080608@grandegger.com>

On 4/20/07, Wolfgang Grandegger <wg@grandegger.com> wrote:
> 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.

This stuff is defined in the device tree.  If you need to detect the
version at runtime, then ideally your bootloader will read the PVR/SVR
to determine the chip version and then pass the correct FDT to the
kernel.

> I found the information here:
>
> $ cat Documentation/powerpc/mpc52xx-device-tree-bindings.txt
<snip>
> Sorry for the noise.

Not noise; good question.

g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  reply	other threads:[~2007-04-20 14:02 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
2007-04-20 14:02   ` Grant Likely [this message]
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=528646bc0704200702i328ba9dbvc62473e5a634d5ac@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=wg@grandegger.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).