All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] ne10: set NE10_TARGET_ARCH with an override instead of anonymous python
Date: Fri, 26 Apr 2019 10:35:18 -0700	[thread overview]
Message-ID: <CAMKF1sq3J1pjWp-sBijwi4VzGVAZWQCk8uznx0VbtODixTFY4A@mail.gmail.com> (raw)
In-Reply-To: <20190426052056.GB26023@localhost>

On Thu, Apr 25, 2019 at 10:21 PM Adrian Bunk <bunk@stusta.de> wrote:
>
> On Wed, Apr 24, 2019 at 07:00:38PM +0000, Martin Jansa wrote:
> > * set COMPATIBLE_MACHINE to (^$) to prevent building it for any other
> >   architectures than armv7a and aarch64
> > * with new arm tune files it's easy to have armv7a in OVERRIDES even
> >   when there isn't armv7a in TUNE_FEATURES:
> >   meta/conf/machine/include/tune-cortexa9.inc:7
> >      "${@bb.utils.contains('TUNE_FEATURES', 'cortexa9', 'armv7a:', '',d)}"
> >   in cases like this COMPATIBLE_MACHINE was satisfied thanks to the
> >   armv7a OVERRIDE, but then the anonymous python was failing with:
> >   ne10 was skipped: Incompatible with archs other than armv7 and aarch64
> >...
>
> How does this handle Cortex A9 SoCs without NEON support?

this is a valid concern although rare but this combination is out
there ( tegra2 )
and ne10 needs neon, so probably its better to check for neon in tune features
 than anything else first.


  reply	other threads:[~2019-04-26 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 19:00 [meta-oe][PATCH] ne10: set NE10_TARGET_ARCH with an override instead of anonymous python Martin Jansa
2019-04-25 21:14 ` Andreas Müller
2019-04-26  5:20 ` Adrian Bunk
2019-04-26 17:35   ` Khem Raj [this message]
2019-04-26 19:27     ` Martin Jansa
2019-04-26 20:34       ` Andreas Müller
2019-05-22 22:16         ` Andre McCurdy
2019-05-22 23:28           ` [meta-oe][PATCH] ne10, libopus: add armv7ve override as well Martin Jansa

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=CAMKF1sq3J1pjWp-sBijwi4VzGVAZWQCk8uznx0VbtODixTFY4A@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=bunk@stusta.de \
    --cc=openembedded-devel@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.