linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Andrei Konovalov <akonovalov@ru.mvista.com>
Cc: PPC_LINUX <linuxppc-embedded@ozlabs.org>
Subject: Re: MPC8xx Platformization
Date: Fri, 20 May 2005 13:51:06 -0400	[thread overview]
Message-ID: <4ab1a586a6835c2436e992f6e2bf7e5a@embeddededge.com> (raw)
In-Reply-To: <428E2049.4010907@ru.mvista.com>


On May 20, 2005, at 1:37 PM, Andrei Konovalov wrote:

> But it still doesn't distinguish between e.g. MPC885, MPC880, MPC875, 
> and MPC870
> - though the set of on-chip devices is different for the four.

I don't believe you can reliably distinguish among many of these parts.
I've had parts stamped with a number on them, but it looks like it had
remnants of other, probably non-working, peripherals from another.
Just poking at some peripheral locations to determine processor
type isn't likely to always be accurate.

I don't think we should be writing any code that relies on the proper
identification of the parts.  When building the code for a real product,
you always configure specifically for it to reduce code size and run 
time
start up.  As a development engineer, you should know the configuration
you are using as well.  The only difference is in the peripherals 
supported,
so just configure what you want to use.

Thanks.

	-- Dan

      reply	other threads:[~2005-05-20 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 13:47 MPC8xx Platformization Jason McMullan
2005-04-27 14:42 ` Kumar Gala
2005-04-27 16:38   ` Jason McMullan
2005-05-20 17:37 ` Andrei Konovalov
2005-05-20 17:51   ` Dan Malek [this message]

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=4ab1a586a6835c2436e992f6e2bf7e5a@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=akonovalov@ru.mvista.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).