From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: Alex Coplan <Alex.Coplan@arm.com>,
"newlib@sourceware.org" <newlib@sourceware.org>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: RE: [PATCH] libgloss/aarch64: Add support for Armv8-R AArch64
Date: Tue, 22 Sep 2020 12:42:02 +0000 [thread overview]
Message-ID: <DB7PR08MB30020E0394CED58943A3553C933B0@DB7PR08MB3002.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200918144327.7qgh64f57myg6njs@arm.com>
> -----Original Message-----
> From: Newlib <newlib-bounces@sourceware.org> On Behalf Of Alex Coplan
> Sent: 18 September 2020 15:43
> To: newlib@sourceware.org
> Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>
> Subject: [PATCH] libgloss/aarch64: Add support for Armv8-R AArch64
>
> Hello,
>
> This patch adds support for Armv8-R AArch64. We update the AArch64 CPU
> boot code to work on Armv8-R if __ARM_ARCH_PROFILE is set to 'R'.
> Armv8-R AArch64 has no EL3, so we don't set vbar_el3, and adjust the
> code to set up the MPU for Armv8-R.
>
> We also add a specs file for use with Armv8-R AArch64 models.
>
> Testing:
> * Ran AArch64 GCC testsuite using --with-arch=armv8-r together with the
> new specs file and boot code in an Armv8-R AArch64 model.
> * Ran newlib testsuite, no regressions.
>
> OK for master?
>
FWIW this looks good to me but I'm not a maintainer.
Thanks,
Kyrill
> Thanks,
> Alex
>
> ---
>
> 2020-09-18 Alex Coplan <alex.coplan@arm.com>
>
> libgloss/ChangeLog:
>
> * aarch64/Makefile.in: Install new specs file.
> * aarch64/cpu-init/Makefile.in: Also build boot code for Armv8-R.
> * aarch64/cpu-init/rdimon-aem-el3.S: Add support for Armv8-R.
> * aarch64/elf-aem-v8-r.specs: New.
next prev parent reply other threads:[~2020-09-22 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 14:43 Alex Coplan
2020-09-22 12:42 ` Kyrylo Tkachov [this message]
2020-09-29 14:06 ` Richard Earnshaw (lists)
2020-09-29 16:27 ` Alex Coplan
2020-09-30 10:25 ` Richard Earnshaw (lists)
2020-09-30 13:25 ` UNSUBSCRIBE Brian Hawley
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=DB7PR08MB30020E0394CED58943A3553C933B0@DB7PR08MB3002.eurprd08.prod.outlook.com \
--to=kyrylo.tkachov@arm.com \
--cc=Alex.Coplan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=newlib@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).