All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: New meta-cubox layer
Date: Wed, 03 Apr 2013 18:52:19 -0400	[thread overview]
Message-ID: <515CB2A3.3080100@balister.org> (raw)
In-Reply-To: <CAP9ODKpRFNN6EP74C+YN2=uN_hRa1BTwz4CHUcUazCQQWKV9dg@mail.gmail.com>

On 04/03/2013 05:43 PM, Otavio Salvador wrote:
> On Wed, Apr 3, 2013 at 4:34 PM, Philip Balister <philip@balister.org> wrote:
>> On 04/03/2013 02:38 PM, Koen Kooi wrote:
>>> Op 03-04-13 18:50, Carlos Rafael Giani schreef:
>>>
>>> Just like https://github.com/naguirre/meta-cubox you're mixing
>>> DISTRO policy in the machine files by setting the tuning to
>>> hardfloat. Don't do that. If you want hardfloat, set that in your
>>> distro config, not in your machine config.
>>>
>>
>> This keeps coming up, but I do not see an answer that works for people
>> creating BSP's that work with just oe-core and a BSP layer.
>>
>> How are we supposed to set TUNE parameters for this case? And yes,
>> this case *must* produce useful output.
> 
> I don't think TUNE is a distro thing. It is indeed a board setting and
> I expect every board to have a good know TUNE setting.

The problem is if you are building for several machines, you may want to
force the same tune settings for several machines that are different
from what the BSP owner "declared" the default to be. Otherwise all
packages become per machine.

Philip

> 
> --
> Otavio Salvador                             O.S. Systems
> E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
> Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 
> 



  reply	other threads:[~2013-04-03 23:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 16:50 New meta-cubox layer Carlos Rafael Giani
2013-04-03 17:52 ` Khem Raj
2013-04-03 18:12   ` Carlos Rafael Giani
2013-04-03 18:05 ` Burton, Ross
2013-04-03 18:11   ` Carlos Rafael Giani
2013-04-03 18:37     ` Burton, Ross
2013-04-03 18:38 ` Koen Kooi
2013-04-03 19:04   ` Carlos Rafael Giani
2013-04-04  9:45     ` Koen Kooi
2013-04-03 19:34   ` Philip Balister
2013-04-03 19:57     ` Koen Kooi
2013-04-03 20:07       ` Philip Balister
2013-04-03 20:19         ` Koen Kooi
2013-04-03 20:49           ` Carlos Rafael Giani
2013-04-03 21:45             ` Otavio Salvador
2013-04-03 22:21               ` Khem Raj
2013-04-03 22:29                 ` Carlos Rafael Giani
2013-04-03 22:40                   ` Martin Jansa
2013-04-03 22:49                     ` Carlos Rafael Giani
2013-04-03 21:43     ` Otavio Salvador
2013-04-03 22:52       ` Philip Balister [this message]
2013-04-04  6:01         ` Koen Kooi
2013-04-04  5:53       ` Koen Kooi
2013-04-04  7:32 ` Henning Heinold
2013-04-04 16:08   ` Carlos Rafael Giani

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=515CB2A3.3080100@balister.org \
    --to=philip@balister.org \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.