LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Per-Erik Johansson <perka@dtek.chalmers.se>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Toolchain for Freescale e200
Date: Thu, 10 Jan 2008 09:46:01 -0600	[thread overview]
Message-ID: <4DA554B1-FBDD-4E5C-AEC3-97EB84020117@kernel.crashing.org> (raw)
In-Reply-To: <1526.213.15.68.47.1199872028.squirrel@webmail.chalmers.se>


On Jan 9, 2008, at 3:47 AM, Per-Erik Johansson wrote:

> Hi
>
> I need a new toolchain since my old one hasn't got support for the  
> (as)
> -me200 and book-e stuff I need to compile a kernel for the e200 core.
> What flags do I specify to get what I need?
> --target=powerpc-e200-linux-gnu --with-cpu=?? --enable-threads=posix
> --enable-languages=c,c++ --with-gnu-as --with-gnu-ld
> And should I use a particular version of gcc, binutils..?
>
> I'm not that familiar with building cross-toolchains, have tried with
> tools like crosstool and buildroot but cant seem to get it to build  
> what I
> need.
>> From what I understand the e200 and e500 are code compatible so  
>> maybe I
> could a toolchain for e500 instead, --with-cpu=8540?
> Any help is much appreciated!

if you aren't using VLE than an e500 toolchain should be sufficient.

- k

      reply	other threads:[~2008-01-10 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 13:56 Linux on Freescale e200 Per-Erik Johansson
2007-12-19 17:36 ` Kumar Gala
2007-12-19 22:15   ` Per-Erik Johansson
2008-01-09  9:47   ` Toolchain for " Per-Erik Johansson
2008-01-10 15:46     ` 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=4DA554B1-FBDD-4E5C-AEC3-97EB84020117@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=perka@dtek.chalmers.se \
    /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