From: Kumar Gala <kumar.gala@freescale.com>
To: "annamaya" <annamaya@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8xx binaries running on a MPC82xx board
Date: Tue, 9 Nov 2004 10:50:24 -0600 [thread overview]
Message-ID: <73CDD492-326F-11D9-9710-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <20041109163726.30776.qmail@web53808.mail.yahoo.com>
One of the main issues that occurs when trying to run applications from=20=
8xx to 82xx is dealing with the difference in cache line size. If code=20=
is written properly this difference will be invisible to the user. It=20=
might be that 8xx code is not as optimal on 82xx because of it.
Also since you are going from 8xx -> 82xx your applications most likely=20=
are all integer code. Going from 82xx -> 8xx may not be as successful.
- kumar
On Nov 9, 2004, at 10:37 AM, annamaya wrote:
> I was under the assumption that the MPC8xx core was
> different from the MPC82xx core (the 603e?). But I was
> surprised to find that the MPC8xx binaries were
> running fine on a MPC82xx binaries, even if they were
> dynamically linked and were linking to the MPC82xx
> libraries. What's going on here? Can I just use the
> 8xx toolkit to work with the 82xx? There must be SOME
> differences between these two architectures. Can
> someone here explain this to me?
>
>
>
> =A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0
> __________________________________
> Do you Yahoo!?
> Check out the new Yahoo! Front Page.
> www.yahoo.com
> =A0
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2004-11-09 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 16:37 MPC8xx binaries running on a MPC82xx board annamaya
2004-11-09 16:50 ` Kumar Gala [this message]
2004-11-09 17:16 ` Dan Malek
2004-11-09 17:30 ` annamaya
2004-11-09 18:36 ` Dan Malek
2004-11-09 19:01 ` annamaya
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=73CDD492-326F-11D9-9710-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=annamaya@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.