Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] arch/powerpc: add fsl e5500 and e6500 support
Date: Tue, 18 Nov 2014 16:20:20 +0100	[thread overview]
Message-ID: <20141118162020.02921a54@free-electrons.com> (raw)
In-Reply-To: <546B5779.9010708@zacarias.com.ar>

Dear Gustavo Zacarias,

On Tue, 18 Nov 2014 11:28:09 -0300, Gustavo Zacarias wrote:

> > I'll try to give this a test when I get a chance, we currently have a
> > e5500 target that we're building binaries for but with a e500mc
> > toolchain (using arch compatibility mode on the processor).  Will the
> > buildroot toolchain do multilib so that it's possible to build uboot
> > 32/36bit and a kernel 64bit?  So far that's why we stuck with the
> > e500mc (just 32/36bit) keeping us using a single toolchain.
> 
> We don't do proper multilib yet, so unfortunately you'll have to go with
> separate BR projects for say kernel/bootloader (64 bit) and userland (32
> bit).

That's kind of annoying, and we have a similar problem on x86-64 when
we need to build a 32 bits bootloader (though this might become less of
an issue with UEFI being capable of using 64 bits bootloaders).

Should we do something about this, and support multilib? Note that SH4
is also broken since quite a while in the internal toolchain backend
because it needs multilib support. The issue is how do we decide which
multilib variants to build? Do we simply "force" a certain set of
multilib variants for a given architecture?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-11-18 15:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 23:14 [Buildroot] [RFC PATCH 0/2] Add Freescale e5500 & e6500 support Gustavo Zacarias
2014-11-17 23:14 ` [Buildroot] [PATCH 1/2] arch/powerpc: add fsl e5500 and " Gustavo Zacarias
2014-11-18 13:56   ` Matthew Weber
2014-11-18 14:28     ` Gustavo Zacarias
2014-11-18 15:20       ` Thomas Petazzoni [this message]
2014-11-18 16:28         ` Gustavo Zacarias
2014-11-18 16:56           ` Thomas Petazzoni
2014-11-18 17:00             ` Gustavo Zacarias
2014-11-18 17:04               ` Thomas Petazzoni
2014-11-18 18:31             ` Baruch Siach
2014-11-18 20:59               ` Thomas Petazzoni
2014-11-17 23:14 ` [Buildroot] [PATCH 2/2] package/gcc: set e5500 and e6500 version mask Gustavo Zacarias
2014-12-07 22:48 ` [Buildroot] [RFC PATCH 0/2] Add Freescale e5500 & e6500 support Thomas Petazzoni
2014-12-07 23:17   ` Gustavo Zacarias
2014-12-07 23:21     ` Thomas Petazzoni

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=20141118162020.02921a54@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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