All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH] arago.conf: Correct TOOLCHAIN_BRAND for ARM9 SOCs
Date: Mon, 6 May 2013 23:08:03 -0400	[thread overview]
Message-ID: <20130507030803.GA32479@edge> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C44B03D@DFLE08.ent.ti.com>

On Mon, May 06, 2013 at 08:07:19PM -0400, Cooper Jr., Franklin wrote:
> > > > > > > diff --git a/meta-arago-distro/conf/distro/arago.conf
> > > > > > > b/meta-arago-distro/conf/distro/arago.conf
> > > > > > > index 3954360..048c480 100644
> > > > > > > --- a/meta-arago-distro/conf/distro/arago.conf
> > > > > > > +++ b/meta-arago-distro/conf/distro/arago.conf
> > > > > > > @@ -21,7 +21,9 @@ DISTRO_FEATURES = "alsa argp bluetooth ext2
> > > > > > > irda largefile pcmcia usbgadget usbh
> > > > > > >
> > > > > > >  # Toolchain should be selected by setting TOOLCHAIN_BRAND in
> > > > > > > local.conf  # Set some sane defaults, in case someone forgets
> > > > > > > to set them in local.conf -TOOLCHAIN_BRAND ?= "linaro"
> > > > > > > +# ARM9 is not supported by the Linaro toolchain so default
> > > > > > > +back to the Arago # toolchain for ARM9 based SOCs.
> > > > > > > +TOOLCHAIN_BRAND ?=
> > > > > > "${@bb.utils.contains('SOC_FAMILY','omapl138','arago','linaro',d)}"
> > > > > >
> > > > > > I don't feel this belongs in the arago.conf - as the comment
> > > > > > above says, this is supposed to be set in the local.conf
> > > > > > anyways, here it just offers a default fall back...
> > > > >
> > > > > I don't see what harm is done by tweaking the variable to insure
> > > > > an optimal and safe default fall back is provided for all
> > > > > platforms we support. This patch changes nothing except fixes a broken
> > use case.
> > > >
> > > > Overhead - it calls that Python function every time you evaluate
> > > > TOOLCHAIN_BRAND variable...
> > > >
> > > > I might be more lenient with something like this though:
> > > >
> > > > TC_SANEDEFAULT := "${@...}"
> > > > TOOLCHAIN_BRAND ?= "${TC_SANEDEFAULT}"
> > > >
> > > > Although, that would no longer work in local.conf, only arago.conf...
> > >
> > > If you have no objection with me putting my suggested change to
> > > TOOLCHAIN_BRAND in oe-layersetup local.conf.sample then I am fine with
> > > dropping this patch.
> > 
> > Either way is fine. You didn't like to split it in 2 lines like above?
> 
> I did like your suggestion but I was confused by the statement "Although, 
> that would no longer work in local.conf, only arago.conf...". 
> TOOLCHAIN_BRAND could still be overridden in local.conf but TC_SANEDEFAULT 
> couldn't. Is that really a problem since originally the expectation was that 
> someone should be overriding TOOLCHAIN_BRAND anyway?

Correct - I meant setting TC_SANEDEFAULT like that (immediate assignment with 
Python code) won't work in local.conf. Which is fine, as TOOLCHAIN_BRAND can 
be overriden from local.conf anyway.


> If your fine with the below then I'll send a v2
> TC_SANEDEFAULT := "${@bb.utils.contains('SOC_FAMILY','omapl138','arago','linaro',d)}"
> TOOLCHAIN_BRAND ?= "${TC_SANEDEFAULT}"

Yes, please.

-- 
Denys


      reply	other threads:[~2013-05-07  3:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 21:30 [PATCH] arago.conf: Correct TOOLCHAIN_BRAND for ARM9 SOCs Franklin S. Cooper Jr
2013-05-06 21:31 ` Denys Dmytriyenko
2013-05-06 21:56   ` Cooper Jr., Franklin
2013-05-06 22:30     ` Denys Dmytriyenko
2013-05-06 23:03       ` Cooper Jr., Franklin
2013-05-06 23:05         ` Denys Dmytriyenko
2013-05-07  0:07           ` Cooper Jr., Franklin
2013-05-07  3:08             ` Denys Dmytriyenko [this message]

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=20130507030803.GA32479@edge \
    --to=denys@ti.com \
    --cc=fcooper@ti.com \
    --cc=meta-arago@arago-project.org \
    /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.