On Wed, 2013-10-23 at 18:30 +0200, Björn Krombholz wrote:
> On 10/20/2013 09:04 PM, Koen Kooi wrote:
> > Then I noticed that the 'genericarmv7a' machine in meta-linaro set
> > the DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set
> > that variable, but that's a different bug. It turns out that using
> > that tune we can have a single feed again for all armv7a machines.
>
> Hi,
>
> just for clarification, I'm not sure where to set it if not in the
> MACHINE config without modifying meta-angstrom.
>
> I've seen you added MACHINE specific DEFAULTTUNEs based on the currently
> supported boards.
> Basically the result should be (IMHO):
> if MACHINE is a armv7a based and DISTRO is angstrom, then
> DEFAULTTUNE = "armv7athf-neon"
>
> Would it be possible to add those definitions based on SOC_FAMILY:
> DEFAULTTUNE_ti33x and DEFAULTTUNE_omap3?
I hope so, see below.
> As of now, when I add a new MACHINE=machfoo based on ti33x.inc from
> meta-ti, I end up with a DEFAULTTUNE=armv7a-neon instead of the new one,
> as the board is not known in meta-angstrom.
>
> I added
> DEFAULTTUNE_machfoo = "${DEFAULTTUNE_genericarmv7a}"
> to the machfoo.conf which is discouraged, if I understand you correctly.
>
> Maybe I'm just missing the obvious safe way?
There is no obvious safe way :( You are running into the same problems
Khem and I ran into with the oe-core way of doing tune files.
This is a big problem and needs to get fixed somehow.
regards,
Koen
_______________________________________________
Angstrom-distro-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
