Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/4] toolchain: add bfin support
Date: Sat, 28 May 2016 17:42:29 +0200	[thread overview]
Message-ID: <20160528154229.GI22609@waldemar-brodkorb.de> (raw)
In-Reply-To: <20160528153349.7a4e1cee@free-electrons.com>

Hi Thomas,
Thomas Petazzoni wrote,

> Hello,
> 
> On Fri, 13 May 2016 14:15:57 +0200, Waldemar Brodkorb wrote:
> 
> > -config BR2_GCC_TARGET_CPU
> > +config BR2_TARGET_CPU
> 
> This seems wrong. Why are you doing this?

In the first patch I disabled --with-cpu for gcc and bfin, as gcc
does not support --with-cpu on bfin. You could use
-mcpu=$(BR2_TARGET_CPU) to optimize code for a specific Bfin CPU,
that is the reason the second version of the patch renamed
the config symbols for a later use.
 
> > +	string "Target CPU"
> 
> And this?
> 
> >  	default bf606		if BR2_bf606
> >  	default bf607		if BR2_bf607
> >  	default bf608		if BR2_bf608
> > @@ -98,7 +99,7 @@ config BR2_GCC_TARGET_CPU
> >  	default bf549		if BR2_bf549
> >  	default bf561		if BR2_bf561
> >  
> > -config BR2_GCC_TARGET_CPU_REVISION
> > +config BR2_TARGET_CPU_REVISION
> 
> Ditto here.
> 
> At the very least, it needs to be explained in the commit log,
> including the impact on the Blackfin external toolchain support.

I thought it has no impact on the external toolchain.
Is BR2_GCC_TARGET_CPU used in any way for external toolchains?

> So you essentially broke this code by renaming the options.

Not broke, disabled it here my intention :=)
 
So how we go further with the internal Bfin toolchain stuff?

best regards
 Waldemar

  reply	other threads:[~2016-05-28 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 12:15 [Buildroot] [PATCH v2 2/4] toolchain: add bfin support Waldemar Brodkorb
2016-05-28 13:33 ` Thomas Petazzoni
2016-05-28 15:42   ` Waldemar Brodkorb [this message]
2016-05-28 17:10     ` 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=20160528154229.GI22609@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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