From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] arch/arm: add an armv8.3a core
Date: Sun, 30 Dec 2018 16:11:24 +0100 [thread overview]
Message-ID: <20181230161124.622b233a@windsurf> (raw)
In-Reply-To: <c6db960a999901cb0beaac68b264e7c9b82e8891.1546179362.git.yann.morin.1998@free.fr>
Hello,
On Sun, 30 Dec 2018 15:16:13 +0100, Yann E. MORIN wrote:
> The armv8.3a generation is a cumulative extension to armv8.2a.
>
> Since gcc correctly enables the appropriate extensions based on the core
> name, we don't really need to introduce a separate config for armv8.3a,
> and we can piggyback on armv8a.
>
> This new core is AArch64 only.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> arch/Config.in.arm | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-12-30 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 14:16 [Buildroot] [PATCH 0/4] arch/arm: add more cores (branch yem/aarch64-new-cores) Yann E. MORIN
2018-12-30 14:16 ` [Buildroot] [PATCH 1/4] arch/arm: drop useless conditional dependencies for 64-bit-only cores Yann E. MORIN
2018-12-30 14:29 ` Thomas Petazzoni
2018-12-30 14:16 ` [Buildroot] [PATCH 2/4] arch/arm: restrict more armv8a cores to aarch64 Yann E. MORIN
2018-12-30 15:11 ` Thomas Petazzoni
2019-01-18 14:55 ` Peter Korsgaard
2018-12-30 14:16 ` [Buildroot] [PATCH 3/4] arch/arm: add armv8.2a cortex-based cores Yann E. MORIN
2018-12-30 15:11 ` Thomas Petazzoni
2018-12-30 14:16 ` [Buildroot] [PATCH 4/4] arch/arm: add an armv8.3a core Yann E. MORIN
2018-12-30 15:11 ` Thomas Petazzoni [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=20181230161124.622b233a@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.