linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alex Zeffertt <ajz@cambridgebroadband.com>
To: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Can software discover MPC8xx variant?
Date: 03 Feb 2003 09:58:08 +0000	[thread overview]
Message-ID: <1044266288.10504.152.camel@zambia> (raw)
In-Reply-To: <3E399074.3040203@embeddededge.com>


Thank you everyone for your suggestions.  It looks like I can't
determine the 8xx variant from software in a reliable way.  The idea
about using pull up/pull down resistors is a good one - but the boards
have already been manufactured, so I am not in the position to be able
to hard-wire the information in this way.

The reason I want to know the 8xx variant, however, is to optimise s/w
for the performance of the chip.  So, I guess I can get away with just
knowing the clock speeds, and the cache sizes.

I know how to determine the clock speeds (they're in /proc/cpuinfo), but
can anybody tell me how to determine the cache sizes (in a
non-destructive manner such as is used by ppcboot).

Thanks,

Alex


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

  reply	other threads:[~2003-02-03  9:58 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
2003-02-03  9:58   ` Alex Zeffertt [this message]
  -- 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=1044266288.10504.152.camel@zambia \
    --to=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).