All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: dev@dpdk.org, david.marchand@redhat.com,
	wathsala.vithanage@arm.com, dhruv.tripathi@arm.com, nd@arm.com
Subject: Re: [PATCH v2 2/4] config/arm: add generic V2 SoC
Date: Thu, 22 Feb 2024 08:08:28 +0100	[thread overview]
Message-ID: <2923985.e9J7NaK4W3@thomas> (raw)
In-Reply-To: <20240220014533.1483934-2-honnappa.nagarahalli@arm.com>

20/02/2024 02:45, Honnappa Nagarahalli:
> Add generic V2 CPU SoC. This will allow for compiling a binary
> that will run on any SoC that uses V2 CPU.
[...]
> +soc_v2 = {
> +    'description': 'Arm Neoverse V2',
> +    'implementer': '0x41',
> +    'part_number': '0xd4f',
> +    'numa': true
> +}
[...]
>  thunderxt88:     Marvell ThunderX T88
>  thunderxt83:     Marvell ThunderX T83
> +v2:              Arm Neoverse V2

Why just "v2" and not "neoversev2"?

Is it a new Arm naming?
If yes, why not just "2" ;)
Last question: what is best between Arm V2 and Armv7? answer is aarchv2 :D
Sorry I like having fun with Arm naming.



  reply	other threads:[~2024-02-22  7:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  2:32 [RFC 1/2] config/arm: add Neoverse V2 part number Honnappa Nagarahalli
2024-01-18  2:32 ` [RFC 2/2] config/arm: add NVIDIA Grace CPU Honnappa Nagarahalli
2024-01-18  3:10   ` Ruifeng Wang
2024-01-18  3:10 ` [RFC 1/2] config/arm: add Neoverse V2 part number Ruifeng Wang
2024-02-20  1:45 ` [PATCH v2 1/4] " Honnappa Nagarahalli
2024-02-20  1:45   ` [PATCH v2 2/4] config/arm: add generic V2 SoC Honnappa Nagarahalli
2024-02-22  7:08     ` Thomas Monjalon [this message]
2024-02-22 22:05       ` Honnappa Nagarahalli
2024-02-20  1:45   ` [PATCH v2 3/4] config/arm: add NVIDIA Grace CPU Honnappa Nagarahalli
2024-02-20  1:45   ` [PATCH v2 4/4] config/arm: add AWS Graviton4 CPU Honnappa Nagarahalli
2024-03-06 15:31   ` [PATCH v2 1/4] config/arm: add Neoverse V2 part number Thomas Monjalon

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=2923985.e9J7NaK4W3@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dhruv.tripathi@arm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=nd@arm.com \
    --cc=wathsala.vithanage@arm.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 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.