LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: le tang <le_tang1@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux on MPC8541 and MPC8560
Date: Wed, 23 Nov 2005 00:09:47 -0600	[thread overview]
Message-ID: <CE4C7593-EEC8-4817-8ED8-219FAD1FE2A1@kernel.crashing.org> (raw)
In-Reply-To: <20051123053711.1110.qmail@web50607.mail.yahoo.com>


On Nov 22, 2005, at 11:37 PM, le tang wrote:

> Hi,
>
> I got questions on developing the linux on MPC8560 and
> MPC8541.
>
> 1) Which version of linux would be best suited for
> these two processors?

2.6.14 is a good starting point.  Older 2.6 kernels have support for  
MPC8540/MPC8560, I forget when we introduced it.

> 2) Can I make model these two processor accurately
> with device trees on the PSIM?

Extremely unlikely. While I think PSIM has some support for e500 I  
dont think it handles anything close enough to boot linux.

> 3) I have cross compiled gcc with target as
> powerpc-eabi option, and I am using
> powerpc-eabi-objdump to disassemble a pre-compiled
> code, I have tried use -M e500 options, but not sure
> if that would give a very accurate assemly listing.

It should be. The kernel is build with -me500 being passed to the  
assembler. for the majority of code it doesn't matter.  it will  
mainly get proper decode of m{t,f}spr instructions and a few other  
things.

- kumar

      reply	other threads:[~2005-11-23  6:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 18:18 linux 2.6.9 on 8xx platform Laurent Lagrange
2005-11-22 19:41 ` Pantelis Antoniou
2005-11-23  5:37   ` Linux on MPC8541 and MPC8560 le tang
2005-11-23  6:09     ` Kumar Gala [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=CE4C7593-EEC8-4817-8ED8-219FAD1FE2A1@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=le_tang1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox