Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] powerpc64 support
@ 2014-01-30 18:11 Danny Gale
  2014-01-30 18:50 ` Gustavo Zacarias
  0 siblings, 1 reply; 4+ messages in thread
From: Danny Gale @ 2014-01-30 18:11 UTC (permalink / raw)
  To: buildroot

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.

Thanks for your help,
Danny

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] powerpc64 support
  2014-01-30 18:11 [Buildroot] powerpc64 support Danny Gale
@ 2014-01-30 18:50 ` Gustavo Zacarias
  2014-01-30 19:24   ` Danny Gale
  0 siblings, 1 reply; 4+ messages in thread
From: Gustavo Zacarias @ 2014-01-30 18:50 UTC (permalink / raw)
  To: buildroot

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] powerpc64 support
  2014-01-30 18:50 ` Gustavo Zacarias
@ 2014-01-30 19:24   ` Danny Gale
  2014-01-30 19:25     ` Gustavo Zacarias
  0 siblings, 1 reply; 4+ messages in thread
From: Danny Gale @ 2014-01-30 19:24 UTC (permalink / raw)
  To: buildroot

Gustavo,

Thanks for getting back to me so quickly. Would it be preferred to add 
to Config.in.powerpc, or create Config.in.powerpc64?

Thanks,
Danny

On 01/30/2014 11:50 AM, Gustavo Zacarias wrote:
> 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.
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] powerpc64 support
  2014-01-30 19:24   ` Danny Gale
@ 2014-01-30 19:25     ` Gustavo Zacarias
  0 siblings, 0 replies; 4+ messages in thread
From: Gustavo Zacarias @ 2014-01-30 19:25 UTC (permalink / raw)
  To: buildroot

On 01/30/2014 04:24 PM, Danny Gale wrote:

> Gustavo,
> 
> Thanks for getting back to me so quickly. Would it be preferred to add
> to Config.in.powerpc, or create Config.in.powerpc64?

We prefer it in the same file like it's done for mips, x86 and other
architectures that have 32/64 bit variants.
Regards.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-01-30 19:25 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-30 18:11 [Buildroot] powerpc64 support Danny Gale
2014-01-30 18:50 ` Gustavo Zacarias
2014-01-30 19:24   ` Danny Gale
2014-01-30 19:25     ` Gustavo Zacarias

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox