All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Markus Volk <f_l_k@t-online.de>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org,
	Pablo Saavedra <psaavedra@igalia.com>,
	Khem Raj <raj.khem@gmail.com>
Subject: Re: [oe-core][PATCH] graphene: disable neon support on arm 32bits
Date: Mon, 13 Feb 2023 22:06:57 +0100	[thread overview]
Message-ID: <Y+qmcQVCcJ4F5LOA@mail.local> (raw)
In-Reply-To: <V6J0QR.2R35TSZ0OM8J3@t-online.de>

On 13/02/2023 10:47:19+0100, Markus Volk wrote:
> Am Sa, 11. Feb 2023 um 09:05:05 +0000 schrieb Richard Purdie
> <richard.purdie@linuxfoundation.org>:
> > Can we tweak the comment to say why? Saying what it does isn't that
> > useful, saying why it does it helps to understand when it may be
> > removed in future. An example of how to crash it would be even better.
> > Was this just some some subset of 32 bit arm or all 32 bit arm?
> > 
> > Cheers,
> > 
> > Richard
> 
> Hello Richard,
> 
> I'm not affected by this bug, none of my machines has it but probably  the
> underlying problem is, that there are still issues with neon runtime
> detection and not all arm platforms are guaranteed to have NEON available.
> That said, maybe it would be better to add this as a PACKAGECONFIG, so
> people could at least manually enable neon support if they know it would be
> working for them?
> 

Can't we get that out of the tune?


> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#177087): https://lists.openembedded.org/g/openembedded-core/message/177087
> Mute This Topic: https://lists.openembedded.org/mt/96893757/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-02-13 21:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11  8:26 [oe-core][PATCH] graphene: disable neon support on arm 32bits Markus Volk
2023-02-11  9:05 ` Richard Purdie
2023-02-13  9:47   ` Markus Volk
2023-02-13 21:06     ` Alexandre Belloni [this message]
2023-02-14  5:45       ` Markus Volk
     [not found]   ` <1743594D8095F1A6.21535@lists.openembedded.org>
2023-02-13 10:15     ` Markus Volk
     [not found] <1742B7B2647E3F63.29566@lists.openembedded.org>
2023-02-11  8:30 ` Markus Volk

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=Y+qmcQVCcJ4F5LOA@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=f_l_k@t-online.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=psaavedra@igalia.com \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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.