One image for two different core

2 messages, 2 authors, 2008-09-05 · open the first message on its own page

One image for two different core

From: Bizhan Gholikhamseh (bgholikh) <hidden>
Date: 2008-09-05 00:29:11

Hi All,

I am doing a feasibility study whether I can have one image for two
different  platform with e300 ad e500 core. The idea is uboot will
detect which type of the processor is running and pass the information
to the early Linux startup, then the code will configure itself based on
what type of core it is.

One of the issue I see is the tool chain,.

I would like to get your opinion on this please.

Many thanks in advance,

Bizhan

Re: One image for two different core

From: Josh Boyer <hidden>
Date: 2008-09-05 01:44:19

On Thu, Sep 04, 2008 at 05:18:45PM -0700, Bizhan Gholikhamseh (bgholikh) wrote:
Hi All,

I am doing a feasibility study whether I can have one image for two
different  platform with e300 ad e500 core. The idea is uboot will
detect which type of the processor is running and pass the information
to the early Linux startup, then the code will configure itself based on
what type of core it is.
That doesn't really sound possible to me with a single kernel binary.  If
I remember correctly, e300 is a 603e style CPU, and e500 is a BookE CPU.
They have totally different MMUs (among other things), which means you
would really need to separate kernel binaries to support that.

I'm not an Freescale core expert though, so I might be confused or don't
know of some way that would work.

josh
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help