linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Can software discover MPC8xx variant?
Date: Thu, 30 Jan 2003 15:52:04 -0500	[thread overview]
Message-ID: <3E399074.3040203@embeddededge.com> (raw)
In-Reply-To: 1043848594.10504.41.camel@zambia


Alex Zeffertt wrote:

> Can anybody tell me if there is a way to identify which processor from
> the MPC8xx family software is running on.

I haven't checked recently, but I believe the PVR still has the same
core type for all 8xx processors.  This is arguably a valid thing to
do since all of the PPC cores are the same in these processors.  There
are some mmu and cache differences, but they all behave in the same
generic manner.

> ....  I hoped I could use the IMMR
> special purpose register.  However, this only tells you the silicon
> revision, which can have the same value even if the processors are
> different!

Right.  The processors also have a CPM microcode revision number stored
in the DPRAM.  Since the real difference among the processors is the CPM,
you can read this number and likely detect the CPM configuration.  Perhaps
from all three values you can detect the processor variant.  From a software
perspective, it really doesn't matter if you can determine the actual
part number printed on the package (that's only for human consumption), but
you can detect the silicon configurations if you wish to dynamically adapt
to the different CPM configurations.

 From the first day of Linux on 8xx, we decided it wasn't worth the baggage
to try and dynamically detect all of these details (and we weren't sure we
could).  In the interest of small, efficient, embedded kernels we adpoted
the direction of configuring specifically for a known part.

Thanks.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-01-30 20:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 13:56 Can software discover MPC8xx variant? Alex Zeffertt
2003-01-29 14:13 ` Marius Groeger
2003-01-30 20:52 ` Dan Malek [this message]
2003-02-03  9:58   ` Alex Zeffertt
  -- strict thread matches above, loose matches on Subject: below --
2003-01-29 16:29 Leonardo Pereira Santos
2003-01-29 17:02 Steven Blakeslee
2003-01-29 17:15 ` Leonardo Pereira Santos
2003-01-29 17:31 Steven Blakeslee

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=3E399074.3040203@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=ajz@cambridgebroadband.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).