<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openembedded-core.git/meta/conf/machine/include/arm, branch 2011-1</title>
<subtitle>Mirror of openembedded-core</subtitle>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/'/>
<entry>
<title>tune: add missing closing quote to arch-armv7a.inc for AVAILTUNES</title>
<updated>2011-08-22T20:01:31+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2011-08-18T16:19:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=7d46901840795638ff184a43e65299446fbd0b4e'/>
<id>7d46901840795638ff184a43e65299446fbd0b4e</id>
<content type='text'>
A closing quote was missing for an AVAILTUNES append operation, add it.

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
CC: Jason Kridner &lt;jkridner@beagleboard.org&gt;
CC: Koen Kooi &lt;koen@dominion.thruhere.net&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A closing quote was missing for an AVAILTUNES append operation, add it.

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
CC: Jason Kridner &lt;jkridner@beagleboard.org&gt;
CC: Koen Kooi &lt;koen@dominion.thruhere.net&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>machine/include/arm/feature-arm-thumb: Allow thumb to be disabled</title>
<updated>2011-08-05T16:22:19+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-08-05T16:22:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=4b5e8074f8aca59b09421db464ce652e84f898f2'/>
<id>4b5e8074f8aca59b09421db464ce652e84f898f2</id>
<content type='text'>
The previous commit to this file meant thumb was always being turned on
even when TUNE_FEATURES did not contain "thumb". This is clearly wrong
and this patch corrects this so thumb options are no longer specified
in that case.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The previous commit to this file meant thumb was always being turned on
even when TUNE_FEATURES did not contain "thumb". This is clearly wrong
and this patch corrects this so thumb options are no longer specified
in that case.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>arch-armv7a.inc: fix armv7a-vfp-neon -&gt; armv7a compat case</title>
<updated>2011-08-01T15:49:03+00:00</updated>
<author>
<name>Koen Kooi</name>
<email>koen@dominion.thruhere.net</email>
</author>
<published>2011-08-01T13:41:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=2a41a311ddda11713296391050f3c2c1b2c1d3d3'/>
<id>2a41a311ddda11713296391050f3c2c1b2c1d3d3</id>
<content type='text'>
Without this 'armv7a' is used as TUNE_ARCH but does *not* end up in PACKAGE_EXTRA_ARCHS:

arch all 1
arch any 6
arch noarch 11
arch arm 16
arch armv4 21
arch armv4t 26
arch armv5 31
arch armv5t 36
arch armv5-vfp 41
arch armv5t-vfp 46
arch armv5e 51
arch armv5te 56
arch armv5e-vfp 61
arch armv5te-vfp 66
arch armv6-vfp 71
arch armv6t-vfp 76
arch armv7-vfp 81
arch armv7t2-vfp 86
arch armv7a-vfp 91
arch armv7at2-vfp 96
arch armv7a-vfp-neon 101
arch armv7at2-vfp-neon 106
arch beagleboard 111

Which leads to a failing do_rootfs

Signed-off-by: Koen Kooi &lt;koen@dominion.thruhere.net&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Without this 'armv7a' is used as TUNE_ARCH but does *not* end up in PACKAGE_EXTRA_ARCHS:

arch all 1
arch any 6
arch noarch 11
arch arm 16
arch armv4 21
arch armv4t 26
arch armv5 31
arch armv5t 36
arch armv5-vfp 41
arch armv5t-vfp 46
arch armv5e 51
arch armv5te 56
arch armv5e-vfp 61
arch armv5te-vfp 66
arch armv6-vfp 71
arch armv6t-vfp 76
arch armv7-vfp 81
arch armv7t2-vfp 86
arch armv7a-vfp 91
arch armv7at2-vfp 96
arch armv7a-vfp-neon 101
arch armv7at2-vfp-neon 106
arch beagleboard 111

Which leads to a failing do_rootfs

Signed-off-by: Koen Kooi &lt;koen@dominion.thruhere.net&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>feature-arm-thumb: respect ARM_INSTRUCTION_SET</title>
<updated>2011-07-29T17:18:15+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>martin.jansa@gmail.com</email>
</author>
<published>2011-07-30T01:04:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=e23f9ce928353c9da2b9c4bfa9a1a125a7d160f2'/>
<id>e23f9ce928353c9da2b9c4bfa9a1a125a7d160f2</id>
<content type='text'>
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>arch-armv6, arch-armv5-dsp: correct endianness confusion</title>
<updated>2011-07-29T16:47:56+00:00</updated>
<author>
<name>Phil Blundell</name>
<email>philb@gnu.org</email>
</author>
<published>2011-07-29T00:31:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=391c0102a81455c76244d13b6878e3a76cca65dc'/>
<id>391c0102a81455c76244d13b6878e3a76cca65dc</id>
<content type='text'>
PACKAGE_EXTRA_ARCHS_tune-armv5eb needs to be defined in terms of
the non-e with the same endianness, i.e. PACKAGE_EXTRA_ARCHS_tune-armv5b
not PACKAGE_EXTRA_ARCHS_tune-armv5, otherwise PACKAGE_EXTRA_ARCHS will
end up containing a semi-random mixture of endiannesses and disaster
will ensue.  Likewise for the vfp and armv6 variants.

This is all a bit confusing because TUNE_FEATURES is done the opposite
way around, i.e. TUNE_FEATURES_tune-armv5eb is derived by taking the
armv5e version and adding bigendian.  But fixing that is probably
a subject for a separate patch.

Signed-off-by: Phil Blundell &lt;philb@gnu.org&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
PACKAGE_EXTRA_ARCHS_tune-armv5eb needs to be defined in terms of
the non-e with the same endianness, i.e. PACKAGE_EXTRA_ARCHS_tune-armv5b
not PACKAGE_EXTRA_ARCHS_tune-armv5, otherwise PACKAGE_EXTRA_ARCHS will
end up containing a semi-random mixture of endiannesses and disaster
will ensue.  Likewise for the vfp and armv6 variants.

This is all a bit confusing because TUNE_FEATURES is done the opposite
way around, i.e. TUNE_FEATURES_tune-armv5eb is derived by taking the
armv5e version and adding bigendian.  But fixing that is probably
a subject for a separate patch.

Signed-off-by: Phil Blundell &lt;philb@gnu.org&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Add ARM tune file overhaul based largely on work from Mark Hatle</title>
<updated>2011-07-27T14:43:38+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-07-25T18:03:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=789dcb8e68a2ab9784ac10ab36815010c61af2fc'/>
<id>789dcb8e68a2ab9784ac10ab36815010c61af2fc</id>
<content type='text'>
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Move architecture specific TARGET_OS mangling into tune files</title>
<updated>2011-07-25T13:19:54+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-07-22T16:54:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=f10a3457cdfbb4a94978da998d178d4254632fa7'/>
<id>f10a3457cdfbb4a94978da998d178d4254632fa7</id>
<content type='text'>
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>conf/machine/include: Start to fill out architecture specific tune include files and tune features</title>
<updated>2011-07-25T13:19:54+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-07-22T16:32:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=5f9d56bd64997b93ed7e46c117851002a0556654'/>
<id>5f9d56bd64997b93ed7e46c117851002a0556654</id>
<content type='text'>
These changes revolve around the idea of tune features. These are represented by
'flag' strings that are included in the TUNE_FEATURES variable.

Any string included in TUNE_FEATURES should also add a TUNEVALID[&lt;name&gt;] entry so
we can know which flags are available in TUNE_FEATURES and have documentation about
what the flags do. We will add sanity code to error if flags are listed in
TUNE_FEATURES but are not documented in TUNEVALID.

A given tune configuration will want to define one or more predetermined sets of
_FEATURE flag lists. These are defined in the form TUNE_FEATURES_tune-&lt;name&gt;.
For defined tune configuation, &lt;name&gt; should be added to the AVAILTUNE list so that
we can determine what tune configurations are available. Flags cannot be used in this
case as with TUNEVALID since its useful to be able to build up tune lists from other
TUNE_FEATURES_tune-yyy options.

A given tune configuration may also define PACKAGE_EXTRA_ARCHS_tune-&lt;name&gt; and
BASE_LIB_tune-&lt;name&gt; to control the multilib location. All options can be overridden
by the distro or local user configuration.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
These changes revolve around the idea of tune features. These are represented by
'flag' strings that are included in the TUNE_FEATURES variable.

Any string included in TUNE_FEATURES should also add a TUNEVALID[&lt;name&gt;] entry so
we can know which flags are available in TUNE_FEATURES and have documentation about
what the flags do. We will add sanity code to error if flags are listed in
TUNE_FEATURES but are not documented in TUNEVALID.

A given tune configuration will want to define one or more predetermined sets of
_FEATURE flag lists. These are defined in the form TUNE_FEATURES_tune-&lt;name&gt;.
For defined tune configuation, &lt;name&gt; should be added to the AVAILTUNE list so that
we can determine what tune configurations are available. Flags cannot be used in this
case as with TUNEVALID since its useful to be able to build up tune lists from other
TUNE_FEATURES_tune-yyy options.

A given tune configuration may also define PACKAGE_EXTRA_ARCHS_tune-&lt;name&gt; and
BASE_LIB_tune-&lt;name&gt; to control the multilib location. All options can be overridden
by the distro or local user configuration.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</pre>
</div>
</content>
</entry>
</feed>
