public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH next 1/4] arch/arm: add the Neoverse-V1 core
Date: Fri, 13 Mar 2026 21:57:18 +0100	[thread overview]
Message-ID: <d90763e9dec2c5032dc847cf586ca4f4@free.fr> (raw)
In-Reply-To: <20260303202708.2065406-1-ju.o@free.fr>

On 03/03/2026 21:27, Julien Olivain via buildroot wrote:
> This commit adds the Neoverse-V1 core, which is an armv8.4a ISA.
> See: [1] [2].
> 
> This CPU support was added in GCC 11. See [3] [4] [5].
> 
> This CPU supports Aarch64 at all exception levels (EL0 to EL3).
> It also supports Aarch32 only in EL0 (user-space). This means it's
> technically possible to compile Aarch32 code. GCC has the support
> to do so. Since Buildroot recompiles a full system (ATF, Kernel,
> user-space) this support has limited value. This is why this
> CPU is limited to 64bit builds only.
> 
> Qemu added neoverse-v1 support in upstream commit [6], first included
> in v8.1.0.
> 
> [1] https://developer.arm.com/Processors/Neoverse%20V1
> [2] 
> https://developer.arm.com/documentation/101427/0102/Functional-description/Introduction/About-the-core
> [3] https://gcc.gnu.org/gcc-11/changes.html#arm-targets
> [4] 
> https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/aarch64/aarch64-cores.def;hb=releases/gcc-11.1.0#l141
> [5] 
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c9d56eb777552ac5ee0c281e1f6e34b6fe929b77
> [6] 
> https://gitlab.com/qemu-project/qemu/-/commit/c74138c6c040b62e941326a4fbb25a93fdd35b72
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>

Series applied to master.
For the record, I added a note in the commit log about the binutils
support for Neoverse V2/V3.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-03-13 20:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03 20:27 [Buildroot] [PATCH next 1/4] arch/arm: add the Neoverse-V1 core Julien Olivain via buildroot
2026-03-03 20:27 ` [Buildroot] [PATCH next 2/4] arch/arm: add the Neoverse-V2 core Julien Olivain via buildroot
2026-03-03 20:27 ` [Buildroot] [PATCH next 3/4] arch/arm: add the Neoverse-V3 core Julien Olivain via buildroot
2026-03-03 20:27 ` [Buildroot] [PATCH next 4/4] arch/arm: add the Neoverse-V3AE core Julien Olivain via buildroot
2026-03-13 20:57 ` Julien Olivain via buildroot [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=d90763e9dec2c5032dc847cf586ca4f4@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.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