From: Adrian Bunk <bunk@stusta.de>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: "wangnan0@huawei.com" <wangnan0@huawei.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] arch-arm64.inc: Do not append aarch64 in MACHINEOVERRIDES
Date: Tue, 3 Mar 2020 15:39:31 +0200 [thread overview]
Message-ID: <20200303133931.GB13148@localhost> (raw)
In-Reply-To: <41b7391039564f10a0c8b4f63eeb4274@XBOX03.axis.com>
On Tue, Mar 03, 2020 at 11:59:58AM +0000, Peter Kjellerstedt wrote:
>...
> Which corresponds to how it is done for armv7*.
>
> At least we currently rely on being able to do, e.g.:
>
> COMPATIBLE_MACHINE = "aarch64|armv7a|armv7ve"
>
> and if you remove "aarch64" from MACHINEOVERRIDES, we need a suitable
> substitute.
What does "aarch64" actually mean here?
Does it also cover 32bit-only aarch64 CPUs?
Similar to x86 there are 3 ABIs, and aarch64ilp32 is different from aarch32.
Different from x86, there is no ABI that is available in all aarch64 CPUs.
They can be 32bit-only or 64bit-only, and aarch32 support is optional.
> //Peter
cu
Adrian
next prev parent reply other threads:[~2020-03-03 13:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 17:11 [PATCH] arch-arm64.inc: Do not append aarch64 in MACHINEOVERRIDES Junling Zheng
2020-03-02 18:29 ` Khem Raj
2020-03-02 21:34 ` Adrian Bunk
2020-03-03 19:27 ` Khem Raj
2020-03-03 3:10 ` Junling Zheng
2020-03-03 11:59 ` Peter Kjellerstedt
2020-03-03 13:05 ` Herve Jourdain
2020-03-03 13:33 ` Peter Kjellerstedt
2020-03-03 13:39 ` Adrian Bunk [this message]
2020-03-03 14:19 ` Peter Kjellerstedt
2020-03-03 19:21 ` Jeremy Puhlman
2020-03-03 14:13 ` Junling Zheng
2020-03-03 14:20 ` Peter Kjellerstedt
2020-03-03 14:39 ` Junling Zheng
2020-03-03 19:31 ` Khem Raj
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=20200303133931.GB13148@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=wangnan0@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox