From: Raslan Darawsheh <rasland@nvidia.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <ruifeng.wang@arm.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH v3 2/4] config/arm: add NVIDIA BlueField-3 platform
Date: Mon, 20 Feb 2023 10:48:25 +0200 [thread overview]
Message-ID: <20230220084827.3317796-3-rasland@nvidia.com> (raw)
In-Reply-To: <20230220084827.3317796-1-rasland@nvidia.com>
Add meson build configuration for NVIDIA BlueField-3 platform
with Cortex-A78AE cores.
Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
---
config/arm/arm64_bluefield3_linux_gcc | 16 ++++++++++++++++
config/arm/meson.build | 16 ++++++++++++++++
2 files changed, 32 insertions(+)
create mode 100644 config/arm/arm64_bluefield3_linux_gcc
diff --git a/config/arm/arm64_bluefield3_linux_gcc b/config/arm/arm64_bluefield3_linux_gcc
new file mode 100644
index 0000000000..775cf5883d
--- /dev/null
+++ b/config/arm/arm64_bluefield3_linux_gcc
@@ -0,0 +1,16 @@
+[binaries]
+c = ['ccache', 'aarch64-linux-gnu-gcc']
+cpp = ['ccache', 'aarch64-linux-gnu-g++']
+ar = 'aarch64-linux-gnu-gcc-ar'
+strip = 'aarch64-linux-gnu-strip'
+pkgconfig = 'aarch64-linux-gnu-pkg-config'
+pcap-config = ''
+
+[host_machine]
+system = 'linux'
+cpu_family = 'aarch64'
+cpu = 'armv8.4-a'
+endian = 'little'
+
+[properties]
+platform = 'bluefield3'
diff --git a/config/arm/meson.build b/config/arm/meson.build
index 6442ec9596..89d8f327f1 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -85,6 +85,9 @@ part_number_config_arm = {
['RTE_MAX_NUMA_NODES', 1]
]
},
+ '0xd42': {
+ 'march': 'armv8.4-a',
+ },
'0xd49': {
'march': 'armv8.5-a',
'march_features': ['sve2'],
@@ -442,12 +445,24 @@ soc_thunderxt83 = {
'part_number': '0xa3'
}
+soc_bluefield3 = {
+ 'description': 'NVIDIA BlueField-3',
+ 'implementer': '0x41',
+ 'flags': [
+ ['RTE_MAX_LCORE', 32],
+ ['RTE_MAX_NUMA_NODES', 1]
+ ],
+ 'part_number': '0xd42',
+ 'numa': false
+}
+
'''
Start of SoCs list
generic: Generic un-optimized build for armv8 aarch64 execution mode.
generic_aarch32: Generic un-optimized build for armv8 aarch32 execution mode.
armada: Marvell ARMADA
bluefield: NVIDIA BlueField
+bluefield3: NVIDIA BlueField 3
centriq2400: Qualcomm Centriq 2400
cn9k: Marvell OCTEON 9
cn10k: Marvell OCTEON 10
@@ -474,6 +489,7 @@ socs = {
'generic_aarch32': soc_generic_aarch32,
'armada': soc_armada,
'bluefield': soc_bluefield,
+ 'bluefield3': soc_bluefield3,
'centriq2400': soc_centriq2400,
'cn9k': soc_cn9k,
'cn10k' : soc_cn10k,
--
2.25.1
next prev parent reply other threads:[~2023-02-20 8:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 13:59 [PATCH 1/4] " Raslan Darawsheh
2023-02-16 13:59 ` [PATCH 2/4] crypto/mlx5: add Bluefield-3 and ConnectX-7 device IDs Raslan Darawsheh
2023-02-16 13:59 ` [PATCH 3/4] doc: update supported devices for NVIDIA NICs Raslan Darawsheh
2023-02-16 13:59 ` [PATCH 4/4] mlx: update PCI device IDs names for NVIDIA BlueField NICs Raslan Darawsheh
2023-02-16 14:04 ` [PATCH v2 0/4] support NVIDIA Bluefield-3 device Raslan Darawsheh
2023-02-16 14:04 ` [PATCH v2 1/4] mlx: update PCI device IDs names for NVIDIA BlueField NICs Raslan Darawsheh
2023-02-16 14:04 ` [PATCH v2 2/4] config/arm: add NVIDIA BlueField-3 platform Raslan Darawsheh
2023-02-20 2:50 ` Ruifeng Wang
2023-02-20 8:42 ` Raslan Darawsheh
2023-02-16 14:04 ` [PATCH v2 3/4] crypto/mlx5: add Bluefield-3 and ConnectX-7 device IDs Raslan Darawsheh
2023-02-16 14:04 ` [PATCH v2 4/4] doc: update supported devices for NVIDIA NICs Raslan Darawsheh
2023-02-20 8:48 ` [PATCH v3 0/4] support NVIDIA Bluefield-3 device Raslan Darawsheh
2023-02-20 8:48 ` [PATCH v3 1/4] mlx: update PCI device IDs names for NVIDIA BlueField NICs Raslan Darawsheh
2023-02-20 8:48 ` Raslan Darawsheh [this message]
2023-02-20 8:48 ` [PATCH v3 3/4] crypto/mlx5: add Bluefield-3 and ConnectX-7 device IDs Raslan Darawsheh
2023-02-20 8:48 ` [PATCH v3 4/4] doc: update supported devices for NVIDIA NICs Raslan Darawsheh
2023-02-20 10:40 ` [PATCH v3 0/4] support NVIDIA Bluefield-3 device 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=20230220084827.3317796-3-rasland@nvidia.com \
--to=rasland@nvidia.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ruifeng.wang@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).