DPDK patches and discussions
 help / color / mirror / Atom feed
From: Doug Foster <doug.foster@arm.com>
To: dev@dpdk.org
Cc: nd@arm.com, Doug Foster <doug.foster@arm.com>,
	Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: [PATCH] config/arm: update mcpu for Cobalt-100 SoC
Date: Tue, 11 Nov 2025 19:06:38 +0000	[thread overview]
Message-ID: <20251111190639.3470596-1-doug.foster@arm.com> (raw)

Update the build configuration for Microsoft Azure Cobalt 100 SoC to
use a CPU-specific mcpu value supported by GCC 14+.

Signed-off-by: Doug Foster <doug.foster@arm.com>
Reviewed-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
---
 config/arm/meson.build | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/config/arm/meson.build b/config/arm/meson.build
index c0aa21b57d..523b0fc0ed 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -300,7 +300,7 @@ implementer_microsoft = {
     'flags': [],
     'part_number_config': {
         '0xd49': {
-            'mcpu': 'mcpu_cobalt100',
+            'mcpu': 'cobalt-100',
             'flags': [
                 ['RTE_MACHINE', '"neoverse-n2"'],
                 ['RTE_ARM_FEATURE_ATOMICS', true],
@@ -492,6 +492,7 @@ soc_cobalt100 = {
     'description' : 'Microsoft Azure Cobalt 100',
     'implementer' : '0x6d',
     'part_number': '0xd49',
+    'extra_march_features': ['crypto'],
     'numa': true
 }
 
@@ -703,10 +704,6 @@ mcpu_defs = {
         'march': 'armv8-a',
         'march_extensions': ['crc']
     },
-    'mcpu_cobalt100': {
-        'march': 'armv9-a',
-        'march_extensions': ['crypto', 'sve', 'sve2']
-    },
     'mcpu_cortex-a78ae': {
         'march': 'armv8.4-a',
         'march_extensions': ['crypto']
-- 
2.34.1


                 reply	other threads:[~2025-11-11 19:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20251111190639.3470596-1-doug.foster@arm.com \
    --to=doug.foster@arm.com \
    --cc=dev@dpdk.org \
    --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 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).