linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Johns Daniel <johns.daniel@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: Common kernel image for e300 and e500v2
Date: Fri, 23 Jan 2009 11:31:05 -0600	[thread overview]
Message-ID: <ba5d9360901230931o20611d59hafdfb555209e255c@mail.gmail.com> (raw)
In-Reply-To: <4979EE74.6040306@freescale.com>

[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

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?

-- Johns

On Fri, Jan 23, 2009 at 10:21 AM, Scott Wood <scottwood@freescale.com>wrote:

> Johns Daniel wrote:
>
>> Is it possible -- and prudent -- to use a single kernel binary image
>> for two similar boards, one based on an e300 core and the other on an
>> e500v2 core?
>>
>
> No, it is not possible.  They use different MMUs, and the kernel does not
> support choosing between them at runtime.
>
>  I was surprised to see that the e500v2-targeted toolchain did build
>> the kernel for the e300 board just fine. Don't know whether this will
>> always be true?
>>
>
> "always" is a strong word, but it should generally work.
>
> -Scott
>
>

[-- Attachment #2: Type: text/html, Size: 1679 bytes --]

  reply	other threads:[~2009-01-23 17:38 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 [this message]
2009-01-23 18:42     ` Scott Wood

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=ba5d9360901230931o20611d59hafdfb555209e255c@mail.gmail.com \
    --to=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).