From: Jerin Jacob <jerinjacobk@gmail.com>
To: Gavin Hu <gavin.hu@arm.com>
Cc: dpdk-dev <dev@dpdk.org>, nd <nd@arm.com>,
Thomas Monjalon <thomas@monjalon.net>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Subject: Re: [dpdk-dev] [PATCH v3 3/3] config: add cortex-a76 configuration
Date: Tue, 12 Nov 2019 09:54:39 +0530 [thread overview]
Message-ID: <CALBAE1OYOwL9J7bhq9XQQsGzQzcO245=ZmRt-6XZVXc6hBzqdg@mail.gmail.com> (raw)
In-Reply-To: <1573450911-24317-4-git-send-email-gavin.hu@arm.com>
On Mon, Nov 11, 2019 at 11:12 AM Gavin Hu <gavin.hu@arm.com> wrote:
>
> To make the list complete and consistent, add cortex-a76 configuration.
>
> Signed-off-by: Gavin Hu <gavin.hu@arm.com>
> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
> ---
> config/arm/meson.build | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/config/arm/meson.build b/config/arm/meson.build
> index b56e442..b23dac1 100644
> --- a/config/arm/meson.build
> +++ b/config/arm/meson.build
> @@ -90,6 +90,7 @@ machine_args_generic = [
> ['0xd08', ['-mcpu=cortex-a72']],
> ['0xd09', ['-mcpu=cortex-a73']],
> ['0xd0a', ['-mcpu=cortex-a75']],
> + ['0xd0b', ['-mcpu=cortex-a76']],
> ['0xd0c', ['-march=armv8.2-a+crc+crypto', '-mcpu=neoverse-n1'], flags_n1sdp_extra]]
>
> machine_args_cavium = [
> --
> 2.7.4
>
prev parent reply other threads:[~2019-11-12 4:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 23:32 [dpdk-dev] [PATCH 1/2] test/rcu: fix the compiling error for armv8.2 Gavin Hu
2019-07-31 23:32 ` [dpdk-dev] [PATCH 2/2] config: add N1SDP configuration Gavin Hu
2019-07-31 23:48 ` [dpdk-dev] [PATCH v2 0/3] add arm neoverse N1 SDP configuration Gavin Hu
2019-07-31 23:48 ` [dpdk-dev] [PATCH v2 1/3] test/rcu: fix the compiling error for armv8.2 Gavin Hu
2019-07-31 23:48 ` [dpdk-dev] [PATCH v2 2/3] config: add arm neoverse N1 SDP configuration Gavin Hu
2019-10-17 22:18 ` Ola Liljedahl
2019-10-18 5:12 ` Honnappa Nagarahalli
2019-10-18 7:23 ` Jerin Jacob
2019-10-22 21:07 ` Honnappa Nagarahalli
2019-10-23 5:03 ` Jerin Jacob
2019-10-27 21:22 ` Thomas Monjalon
2019-10-28 3:24 ` Honnappa Nagarahalli
2019-10-28 8:36 ` Thomas Monjalon
2019-10-29 5:47 ` Honnappa Nagarahalli
2019-11-11 5:06 ` Gavin Hu (Arm Technology China)
2019-07-31 23:48 ` [dpdk-dev] [PATCH v2 3/3] config: add cortex-a76 configuration Gavin Hu
2019-11-11 5:41 ` [dpdk-dev] [PATCH v3 0/3] add arm N1SDP and A76 configurations Gavin Hu
2019-11-20 22:41 ` Thomas Monjalon
2019-11-11 5:41 ` [dpdk-dev] [PATCH v3 1/3] test/rcu: fix the compiling error for armv8.2 Gavin Hu
2019-11-20 22:18 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-11-21 11:23 ` Gavin Hu (Arm Technology China)
2019-11-25 3:36 ` [dpdk-dev] [PATCH v4] test/rcu: fix build for small number of cores Gavin Hu
2019-11-25 22:40 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-11-11 5:41 ` [dpdk-dev] [PATCH v3 2/3] config: add arm neoverse N1 SDP configuration Gavin Hu
2019-11-12 4:23 ` Jerin Jacob
2019-11-14 7:55 ` Gavin Hu (Arm Technology China)
2019-11-14 8:17 ` Jerin Jacob
2019-11-11 5:41 ` [dpdk-dev] [PATCH v3 3/3] config: add cortex-a76 configuration Gavin Hu
2019-11-12 4:24 ` Jerin Jacob [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='CALBAE1OYOwL9J7bhq9XQQsGzQzcO245=ZmRt-6XZVXc6hBzqdg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=nd@arm.com \
--cc=thomas@monjalon.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 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 NNTP newsgroup(s).