From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] powerpc64 support
Date: Thu, 30 Jan 2014 15:50:10 -0300 [thread overview]
Message-ID: <52EA9EE2.80807@zacarias.com.ar> (raw)
In-Reply-To: <52EA95DB.70504@coloradoengineeringinc.com>
On 01/30/2014 03:11 PM, Danny Gale wrote:
> Hi all,
>
> We have used buildroot in the past to build filesystems for 32-bit
> powerpc's with great success. Our newest boards are using 64-bit
> powerpc's, however. Using menuconfig with buildroot 2013-11, I don't see
> a target architecture for powerpc64. Is there support for 64-bit powerpc's?
>
> We're using an externally-generated toolchain, which is compiled for
> 64-bit powerpc's, specifically the e6500 core
> (powerpc64-e6500-linux-gnu-). Will selecting powerpc but using this
> 64-bit toolchain generate 64-bit filesystems? I don't see the e6500
> listed as a supported Target Architecture Variant either, but I believe
> it can run 32-bit code generated for the e500 cores.
Hi Danny.
That's because nobody did the necessary modifications yet.
You'd need to add 64 bit cores/defines into arch/Config.in.ppc and
arch/Config.in, and adjust all the available toolchain options for them.
IIRC the e6500 can execute e500mc code, but not e500v* since the later
use SPE instead of a normal FPU (which i think the e6500 doesn't carry
over, using the classic & altivec IIRC).
It may be possible to build internal toolchains too given the appropiate
component (binutils/gcc) versions.
uClibc definitely doesn't handle ppc64, so that would just leave
glibc/eglibc in the libc department.
Regards.
next prev parent reply other threads:[~2014-01-30 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 18:11 [Buildroot] powerpc64 support Danny Gale
2014-01-30 18:50 ` Gustavo Zacarias [this message]
2014-01-30 19:24 ` Danny Gale
2014-01-30 19:25 ` Gustavo Zacarias
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=52EA9EE2.80807@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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