Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openpgm: Blacklist Blackfin ADI 2014R1 toolchain
Date: Thu, 12 Mar 2015 22:47:54 +0100	[thread overview]
Message-ID: <5502098A.6030909@openwide.fr> (raw)
In-Reply-To: <20150308183023.06960971@free-electrons.com>

Hello Thomas,

Le 08/03/2015 18:30, Thomas Petazzoni a ?crit :
> Dear Romain Naour,
> 
> On Sun, 08 Mar 2015 17:43:48 +0100, Romain Naour wrote:
> 
>>> Also, at some point, we will need to really on the ARCH_HAS_ATOMICS
>>> stuff for this.
>> really -> rely
> 
> Right. But it's not a commit log, so do we care about typos ? :-)

:)

> 
>> You mean BR2_ARCH_HAS_ATOMICS ?
>> But it's set by default for bfin configs.
> 
> Yes. Back when we introduced BR2_ARCH_HAS_ATOMICS, but wondered whether
> it should be BR2_ARCH_HAS_ATOMICS or BR2_TOOLCHAIN_HAS_ATOMICS, i.e
> whether we would have the case of an architecture that does support
> atomic intrinsics, but has certain toolchain versions for this
> architecture that do not.

I remember to have read something about that on the ml.

Yann said in the commit log:
"The fact that atomic operations are available is not really a
specificity of the toolchain, but rather of the architecture."

> 
> I don't remember if we carefully check whether Blackfin has atomic
> intrinsics or not.

I don't know, the commit enabling BR2_ARCH_HAS_ATOMICS on bfin said nothing
about that. Yann do you remember ?

> 
>> config BR2_ARCH_HAS_ATOMICS
>>   	# The following toolchains lack required compiler intrinsics
>> 	depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2014R1
>>   	depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2013R1
>>   	depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2
>> 	default y
> 
> Nope. We first need to find out whether the Blackfin architecture has
> what's needed to provide atomic intrinsics. Depending on that, we'll
> now if it's a toolchain limitation or not.

I'm not sure but blackfin seems to have some (one?) atomic instruction(s):

http://www.analog.com/media/en/dsp-documentation/processor-manuals/ADSP-BF539_HRM_rev03.pdf
"The processor provides a single atomic operation: TESTSET"

http://blackfin.uclinux.org/doku.php?id=toolchain:application_binary_interface
"The Blackfin does not have an atomic 64 bit load/store instruction"

Best regards,
Romain
> 
> Best regards,
> 
> Thomas
> 

  reply	other threads:[~2015-03-12 21:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07 18:51 [Buildroot] [PATCH] openpgm: Blacklist Blackfin ADI 2014R1 toolchain Romain Naour
2015-03-08  7:53 ` Thomas Petazzoni
2015-03-08 16:43   ` Romain Naour
2015-03-08 17:30     ` Thomas Petazzoni
2015-03-12 21:47       ` Romain Naour [this message]
2015-03-13  6:25         ` 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=5502098A.6030909@openwide.fr \
    --to=romain.naour@openwide.fr \
    --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