From: Scott Wood <scottwood@freescale.com>
To: Johns Daniel <johns.daniel@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Common kernel image for e300 and e500v2
Date: Fri, 23 Jan 2009 12:42:00 -0600 [thread overview]
Message-ID: <497A0F78.8000600@freescale.com> (raw)
In-Reply-To: <ba5d9360901230931o20611d59hafdfb555209e255c@mail.gmail.com>
Johns Daniel wrote:
> Thank you for that piece of info, Scott!
>
> May I expand the question one bit, and ask whether the user-mode
> binaries compiled for the e300 will generally work for the e500 -- or,
> vice versa? Is one choice safer than the other?
>
> I know for sure that we take a big hit on floating-point ops, but are
> there other things I am not considering?
It should work, though as you note floating point will have to be
emulated (make sure your kernel supports it); better would be to compile
as soft-float. Also avoid string instructions.
-Scott
prev parent reply other threads:[~2009-01-23 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 15:05 Common kernel image for e300 and e500v2 Johns Daniel
2009-01-23 16:21 ` Scott Wood
2009-01-23 17:31 ` Johns Daniel
2009-01-23 18:42 ` Scott Wood [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=497A0F78.8000600@freescale.com \
--to=scottwood@freescale.com \
--cc=johns.daniel@gmail.com \
--cc=linuxppc-dev@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).