All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/3] toolchain: add bfin support
Date: Mon, 4 Jul 2016 17:48:53 +0200	[thread overview]
Message-ID: <20160704174853.59af47cd@free-electrons.com> (raw)
In-Reply-To: <20160704110849.28f815fc@free-electrons.com>

Hello,

On Mon, 4 Jul 2016 11:08:49 +0200, Thomas Petazzoni wrote:

> BTW, uClibc-ng has linuxthreads support for Blackfin, but this patch
> series does not enable it. I tried to enable it, but it fails to build.
> 
> Do you plan on enabling thread support on Blackfin at some point ?
> 
> If we have good enough Blackfin support in the internal toolchain
> backend, this would ultimately allow us to get rid of the old Analog
> Devices external toolchains for Blackfin (they use gcc 4.3, a
> prehistoric version of uClibc, etc.), so getting rid of them would
> really be nice.

Also, the default Blackfin core in Buildroot is bf609, and there's no
support for it in the upstream gcc, which causes a build failure when
building uClibc-ng because -mcpu=bf609 is not valid.

It looks like we will need to:

 1/ Change the default Blackfin core to something that the internal
    toolchain backend support

 2/ Make the internal toolchain backend only available if the selected
    Blackfin core is supported

Could you work on this?

Thanks,

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

  reply	other threads:[~2016-07-04 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03  4:05 [Buildroot] [PATCH v3 2/3] toolchain: add bfin support Waldemar Brodkorb
2016-07-04  9:02 ` Thomas Petazzoni
2016-07-04  9:08 ` Thomas Petazzoni
2016-07-04 15:48   ` Thomas Petazzoni [this message]
2016-07-05 17:27     ` 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=20160704174853.59af47cd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.