All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: "OE Core \(openembedded-core@lists.openembedded.org\)"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] feature-arm-thumb: Fix missing t2 suffix for armv7a MACHINEs
Date: Wed, 22 Jan 2014 10:57:45 +0100	[thread overview]
Message-ID: <20140122095745.GQ4100@jama> (raw)
In-Reply-To: <D8C17D3D-12B9-41E5-AB9D-A2E916ACAB23@dominion.thruhere.net>

[-- Attachment #1: Type: text/plain, Size: 3520 bytes --]

On Wed, Jan 22, 2014 at 07:43:19AM +0100, Koen Kooi wrote:
> 
> Op 22 jan. 2014, om 01:49 heeft Martin Jansa <martin.jansa@gmail.com> het volgende geschreven:
> 
> > On Wed, Jan 22, 2014 at 12:43:12AM +0100, Martin Jansa wrote:
> >> * unfortunatelly that note about armv7 matching also armv7a is no
> >>  longer valid since armv7 include in armv7 was replaced with
> >>  armv6+neon in this commit:
> >> 
> >>  commit 75b8adbc042e0f65fb1286bc550d02becd3b6aea
> >>  Author: Khem Raj <raj.khem@gmail.com>
> >>  Date:   Tue Mar 27 18:37:45 2012 -0700
> >> 
> >>    tune/armv7: Delete
> >> 
> >>  since then thumb and arm feeds had the same architecture
> >> * be aware that this will rename lots of feeds
> > 
> > Can someone confirm that t2 should be included for armv7m or armv7r?
> 
> cortex-M is thumb2 only, no idea about cortex-r.

Thanks.

From
http://www.arm.com/products/processors/cortex-r/cortex-r4.php

it looks like r4 should support both, I've addressed that in following
RFC/WIP.

> > It looks like armv7m definitely should include it, but it doesn't even have
> > thumb in TUNE_FEATURES for the only armv7m user we have in oe-core cortexm3:
> > 
> > tune-cortexm3.inc:TUNE_FEATURES_tune-cortexm3 = "armv7m vfp cortexm3"
> > tune-cortexm3.inc:PACKAGE_EXTRA_ARCHS_tune-cortexm3 = "${PACKAGE_EXTRA_ARCHS_tune-armv7at} armv7m-vfp"
> > 
> > tune-cortexr4.inc:TUNE_FEATURES_tune-cortexr4 = "armv7r vfp cortexr4"
> > tune-cortexr4.inc:PACKAGE_EXTRA_ARCHS_tune-cortexr4 = "${PACKAGE_EXTRA_ARCHS_tune-armv7at} armv7r-vfp"
> > 
> > Anyway I'm sending a bit bigger RFC/WIP patchset to address this.
> > 
> >> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> >> ---
> >> meta/conf/machine/include/arm/feature-arm-thumb.inc | 3 +--
> >> 1 file changed, 1 insertion(+), 2 deletions(-)
> >> 
> >> diff --git a/meta/conf/machine/include/arm/feature-arm-thumb.inc b/meta/conf/machine/include/arm/feature-arm-thumb.inc
> >> index bd754be..fa3a4e5 100644
> >> --- a/meta/conf/machine/include/arm/feature-arm-thumb.inc
> >> +++ b/meta/conf/machine/include/arm/feature-arm-thumb.inc
> >> @@ -9,11 +9,10 @@ ARM_THUMB_M_OPT = "${@['-marm', '-mthumb'][d.getVar('ARM_INSTRUCTION_SET', True)
> >> TUNE_CCARGS .= "${@bb.utils.contains("TUNE_FEATURES", "thumb", " ${ARM_THUMB_M_OPT}", "", d)}"
> >> OVERRIDES .= "${@bb.utils.contains("TUNE_FEATURES", "thumb", ":thumb", "", d)}"
> >> 
> >> -# Note armv7 will hit on armv7a as well
> >> ARMPKGSFX_THUMB .= "${@bb.utils.contains("TUNE_FEATURES", [ "armv4", "thumb" ], "t", "", d)}"
> >> ARMPKGSFX_THUMB .= "${@bb.utils.contains("TUNE_FEATURES", [ "armv5", "thumb" ], "t", "", d)}"
> >> ARMPKGSFX_THUMB .= "${@bb.utils.contains("TUNE_FEATURES", [ "armv6", "thumb" ], "t", "", d)}"
> >> -ARMPKGSFX_THUMB .= "${@bb.utils.contains("TUNE_FEATURES", [ "armv7", "thumb" ], "t2", "", d)}"
> >> +ARMPKGSFX_THUMB .= "${@bb.utils.contains("TUNE_FEATURES", [ "armv7a", "thumb" ], "t2", "", d)}"
> >> 
> >> # Whether to compile with code to allow interworking between the two
> >> # instruction sets. This allows thumb code to be executed on a primarily
> >> -- 
> >> 1.8.5.3
> >> 
> > 
> > -- 
> > Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2014-01-22  9:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 23:43 [PATCH 1/2] opkg-utils: Add RPROVIDES/RREPLACES/RCONFLICTS to fix upgrade-path Martin Jansa
2014-01-21 23:43 ` [PATCH 2/2] feature-arm-thumb: Fix missing t2 suffix for armv7a MACHINEs Martin Jansa
2014-01-22  0:49   ` Martin Jansa
2014-01-22  6:43     ` Koen Kooi
2014-01-22  9:57       ` Martin Jansa [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=20140122095745.GQ4100@jama \
    --to=martin.jansa@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.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.