> On Feb 22, 2024, at 1:08 AM, Thomas Monjalon <tho...@monjalon.net> wrote:
>
> 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”?
This is what was done for N2, so just keeping it consistent
>
> Is it a new Arm naming?
No. ’Neoverse’ is the brand name that encompasses all the products for
infrastructure market. CPUs are one of the products under Neoverse brand name.
There are 2 series of CPUs (targeting 2 different PPAs) - N series and V
series. N2 and V2 are the second generation of CPUs in those series.
> If yes, why not just "2" ;)
> Last question: what is best between Arm V2 and Armv7? answer is aarchv2 :D
ArmV7/ArmV8/ArmV9 are architecture revisions. There is no ArmV2 architecture.
Aarch32/Aarch64 are architecture states. For ex: N1 supported Aarch32 to run
32b applications as well as Aarch64 to run 64b applications. The later cores
just support Aarch64 state and one can run only 64b applications.
> Sorry I like having fun with Arm naming.
No worries, it can be confusing. I hope the above explanation helps.
You have to pin this email for several months to be able to remember this :)
>
>
